From b2d41e91cfa29e401829ea812d468bfbfa0576c9 Mon Sep 17 00:00:00 2001 From: Prithvi Rajakumar Date: Fri, 19 Jun 2026 16:28:25 -0400 Subject: [PATCH] Use package-qualified SENTRY_RELEASE (unify with Build Distribution) 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) --- .env.example | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/.env.example b/.env.example index 9751f28..f684bd4 100644 --- a/.env.example +++ b/.env.example @@ -6,7 +6,7 @@ # ======================================== SENTRY_AUTH_TOKEN=your_auth_token SENTRY_DSN=your_dsn -SENTRY_RELEASE=empower_flutter@9.14.0+1 # Format: appname@version+build +SENTRY_RELEASE=com.example.empower_flutter@9.22.0+1 # Format: @version+build (matches the build identifier used by Build Distribution) SENTRY_ENVIRONMENT=your_environment # ========================================