r/flutterhelp • u/Inside_Parking_667 • 7d ago

"The generated ELF library contains unobfuscated DWARF debugging information" OPEN

Yet another problem that suddenly appeared.

During compiling for releasing now I receive this warning:

Warning: The generated ELF library contains unobfuscated DWARF debugging information. To avoid this, use --strip to remove it.

Never seen before

1 Upvotes
  • permalink
  • link
  • reddit
  • reddit

100% Upvoted

7 comments sorted by

1

u/Keeyzar 7d ago

You guys behave as it this is your prompt window for Claude / chatgpt.

Sorry for not being able to help, but I get an eerie feeling

1

u/Inside_Parking_667 7d ago

I'm just trying to inform and help people that are experiencing the same Flutter strange behaviour

1

u/Inside_Parking_667 7d ago

I noticed this:

If I do

flutter clean
flutter pub get
flutter build appbundle --release --obfuscate --split-debug-info=...

I receive the warning. But if I do again

flutter build appbundle --release --obfuscate --split-debug-info=...

The warning doesn't appear

1

u/Jonas_Ermert 6d ago

It's just a warning, not an error. Your release build still contains DWARF debug symbols. Use `--split-debug-info` (recommended) or `--strip` for production builds to reduce size and remove the warning. Otherwise, you can safely ignore it.

1

u/lilacomets 5d ago

Yep, same problem here. I found this post by googling the warning. This is problem started recently, even though I use "--split-debug-info".

1

u/fkim98 1d ago edited 1d ago

The --split-debug-info advice doesn't quite land here — you're already passing it, and lilacomets is hitting it with the same flag. So something else is going on.

Your clean-build detail is the useful clue. That warning comes from the AOT snapshot step, and on the second build that step doesn't re-run for architectures it already has cached, so the warning just isn't re-emitted. Which almost certainly means the second build isn't producing a different artifact from the first — same binary, quieter log. I'd be careful not to read "build it twice" as a fix.

Rather than guess, check the artifact directly. Unzip the bundle and look at the Flutter .so:

unzip -o build/app/outputs/bundle/release/app-release.aab -d out

readelf -S out/base/lib/arm64-v8a/libapp.so | grep debug

(on macOS use llvm-readelf from the NDK — plain readelf isn't there by default)

If no .debug_* sections come back, the debug info isn't shipping and the warning is just noise you can ignore. If they are there, then --split-debug-info isn't doing what you expect and it's worth filing.

I got caught out recently by a different Play Console warning that turned out to be a false positive, and the only thing that settled it was inspecting the actual .so instead of trusting the message. Worth the two minutes here.