Android - DSN is required. crash on launch when a valid DSN is specified

[bricefriha]

Package

Sentry

.NET Flavor

.NET

.NET Version

8

OS

Android

SDK Version

4.13.0

Steps to Reproduce

1. Create an Android project (not MAUI)
2. Add the DSN in the options:
   options.Dsn = "..."; // Enter a valid DSN
   options.Debug = true;

Alternatively, from the sentry-dotnet just run the sample app Sentry.Samples.Android

Note

Make sure the SDK version is 4.13.0. versions below work just fine

Expected Result

The app should launch without a crash

Actual Result

Crashes on launch, telling us the DSN is missing

[bricefriha]

To confirm, This affects all versions of the dotnet SDK above 4.12.2

[jamescrosswell]

To confirm, This affects all versions of the dotnet SDK above 4.12.2

Yikes, it looks like samples/Sentry.Samples.Android/Sentry.Samples.Android.csproj is filtered out of the Sentry-CI-Build-macOS.slnf as well, so this isn't' being detected in CI (which it should be).

[bricefriha]

samples/Sentry.Samples.Android/Sentry.Samples.Android.csproj is filtered out of the Sentry-CI-Build-macOS.slnf as well, so this isn't' being detected in CI (which it should be).

Sheesh!...
Is it something we can fix separately?

[bricefriha]

It seems like the issue is specifically related to the Android replay package => sentry-android-replay-7.16.0.aar

I tested with all the versions of sentry-android-replay from 7.12.0 to 7.17.0. Same problem occur everytime

[bricefriha]

Update on this

It seems like the configuration callback is never invoked via void OptionsConfigurationCallback.Configure(JavaObject optionsObject).

I investigated, and here's what I observed:

• On MAUI Android: OptionsConfigurationCallback.Configure(JavaObject optionsObject) is invoked as soon as SentryAndroid.Init(); is called
• On vanilla Android with the 4.12.2 SDK, the configuration callback is called from the code Android bindings generate.

__this.Configure (p0!);

Line 93 of Sentry.Java.Sentry.cs

• On vanilla Android with 4.13 SDK: the app crashes before the configuration method is even called

For the later two, OptionsConfigurationCallback.Configure(JavaObject optionsObject) is basically never called

It seems like this has something has to be fixed on Sentry.Android.Bindings, but the thing is that the 3 cases I mentioned all share the same code...

[jamescrosswell]

@romtsn do you have any ideas?