Repository navigation
Replies: 5 comments
|
A few more details since opening this, to make it easier to assess. Where the UUID gets lost. The Dart SDK builds the event and runs its own processors, then Why So our two questions, more directly:
Where we think a fix could live
A looks simpler and keeps the logic next to the code that creates the Rest of our workaround (reading the UUID)The UUID is written to the asset by the Gradle plugin after the Dart code is compiled, so it can't be a private String readProguardUuids() {
try (InputStream input = context.getAssets().open("sentry-debug-meta.properties")) {
Properties properties = new Properties();
properties.load(input);
return properties.getProperty("io.sentry.ProguardUuids");
} catch (IOException e) {
return null;
}
}The processor is registered in the |
|
Thanks a lot @buenaflor for confirming and opening #4080! Option A works for us too. I'll take the issue and open a PR. |
|
Thanks @buenaflor! I opened a PR for #4080 with the Dart-side approach: #4081 A few points worth flagging for the review:
It's ready for review, happy to adjust anything. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello
We're using sentry_flutter 9.10.0 on Android (also checked 9.30.1) with the Sentry Android Gradle Plugin, which embeds the ProGuard UUID in the APK and uploads the R8 mapping under that UUID. Crashes captured by the Android SDK are deobfuscated correctly.
However, PlatformExceptions captured on the Dart side keep their Java frames obfuscated, and since the minified names change with every build, each release creates a new Sentry issue for the same defect.
What we found
This looks like what was observed in #2841 ("the mapping is uploaded correctly, but the issue itself has no debug_meta"), which was closed for an unrelated reason.
In our case the error comes from the Flutter engine itself (TextInputChannel rejecting setEditingState), so the workaround suggested in #2841 (capturing from Kotlin) isn't possible.
Our current workaround
We read io.sentry.ProguardUuids from the sentry-debug-meta.properties asset through a method channel, and attach it with an event processor registered in SentryFlutter.init:
It works, with events from two builds that have different R8 output landing in the same issue, but it feels like something the SDK could do itself, since the native side already knows the ProGuard UUID.
Questions
Thanks!
All reactions