test(backport): run mobile integration tests in Release and Debug modes#4855
test(backport): run mobile integration tests in Release and Debug modes#4855Flash0ver merged 1 commit intosupport/v5from
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## support/v5 #4855 +/- ##
==============================================
+ Coverage 73.50% 73.54% +0.03%
==============================================
Files 483 483
Lines 17692 17692
Branches 3492 3492
==============================================
+ Hits 13005 13011 +6
+ Misses 3796 3793 -3
+ Partials 891 888 -3 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
There was a problem hiding this comment.
Cursor Bugbot has reviewed your changes and found 1 potential issue.
Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.
| { | ||
| base.OnCreate(savedInstanceState); | ||
|
|
||
| System.Environment.SetEnvironmentVariable("SENTRY_DSN", Intent?.GetStringExtra("SENTRY_DSN")); |
There was a problem hiding this comment.
Unused runtime DSN on Android is dead code
Low Severity
The SENTRY_DSN environment variable is set in MainActivity.OnCreate() from intent extras, and RunAndroidApp passes the DSN via intent. However, this value is never used because the Sentry SDK is already configured with a hardcoded DSN in MauiProgram.cs (which runs before OnCreate()). For Android, options.Dsn is explicitly set at build time, so the environment variable fallback never triggers. This dead code creates confusion about how DSN configuration works on Android versus iOS.
Backports from
v6tov5