chore: unify Sentry release to package-qualified name (com.example.empower_flutter@…)#24
Merged
Merged
Conversation
Build Distribution keys builds by the APK's applicationId+version (com.example.empower_flutter@version), so set SENTRY_RELEASE to the same package-qualified form. Now events, debug symbols, source maps, ProGuard mapping, and builds all share one release instead of splitting between empower_flutter@... and com.example.empower_flutter@... Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Follow-up to #23. Sets
SENTRY_RELEASEin.env.exampleto the package-qualified formcom.example.empower_flutter@<version>+<build>so the app's release matches the identifier Build Distribution derives from the APK.Why
sentry-cli build upload(Build Distribution / size analysis) keys builds by the APK'sapplicationId+version (com.example.empower_flutter@9.22.0+1), not by the free-formSENTRY_RELEASE. With the bareempower_flutter@…release, events/symbols landed on one release while builds landed on another. Using the package-qualified name makes events, debug symbols, web source maps, ProGuard mapping, and builds all share one release.This works because
sentry_dart_pluginreadsSENTRY_RELEASEfrom the env,demo.sh'sget_release_namealready emitscom.example.…, and Build Distribution reads the same identity from the APK — so all sources now agree.Change
.env.example:SENTRY_RELEASE=com.example.empower_flutter@9.22.0+1(+ clarifying comment). (.envis gitignored; updated locally.)Verified by rebuilding/uploading: the release build now creates only
com.example.empower_flutter@9.22.0+1, with Dart symbols, ProGuard, web source maps, and the Build Distribution APK all under it.🤖 Generated with Claude Code