fix: Source context for class libraries when running on Android in Release mode

[jamescrosswell]

Resolves: #4278

• Partial source context in Release with multi-project MAUI apps #4278

[bruno-garcia]

looks like we have one logger but shouldn't this be a level Error log?

[jamescrosswell]

We'd have to refactor the AssemblyReader classes that we vendored in fomr MS in order to be able to do that (they use a different pattern for logging).

Probably the easiest would be to replace DebugLogger with our own IDiagnosticLogger... would involve quite a few changes, but then we've made so many changes to these already that the only way to merge in changes from new code is by hand. So a few more changes wouldn't hurt.

[jamescrosswell]

Note

This behaviour only manifests in CI (with the headless runners). Device tests work fine when run locally on a simulator.

Something very unusual happening with the device tests. Running against API levels 27 and 33, 27 always fails. 33 fails frequently (but not always).

Since Google require folks target 34 and higher to be able to release anything on the play store now, I figured I'd bump the API levels we test against to 34 (oldest supported) and 36 (latest). The also both seem to fail.

Looking at the logs, there don't appear to be any failed tests.

In one run, I noticed the last line that gets logged from .NET SDK is:

07-14 05:34:09.084  4252  4294 I DOTNET  : 	[IGNORED] Sentry.Maui.Tests.SentryMauiScreenshotTests.CaptureException_BeforeCaptureScreenshot_DefaultAsync

Shortly after that I see some logs from sentry-native:

07-14 05:34:10.213  4252  5450 I sentry-native: entering signal handler
07-14 05:34:10.225  4252  4280 I sentry-native: entering signal handler
07-14 05:34:10.229  4252  5450 D sentry-native: captured backtrace from ucontext with 1 frames
07-14 05:34:10.232  4252  5450 D sentry-native: captured backtrace with 1 frames
07-14 05:34:10.232  4252  5450 D sentry-native: merging scope into event
07-14 05:34:10.232  4252  5450 D sentry-native: trying to read modules from /proc/self/maps
...
07-14 05:34:11.726  4252  5439 I sentry-native: entering signal handler
...
07-14 05:34:11.828  4252  5450 D sentry-native: read 475 modules from /proc/self/maps
07-14 05:34:11.828  4252  5450 D sentry-native: adding attachments to envelope
07-14 05:34:11.828  4252  5450 D sentry-native: sending envelope
07-14 05:34:11.829  4252  5450 I sentry-native: crash has been captured

So it looks like potentially there is a low level crash that sentry-native is picking up and sending as an envelope. To where though and from which test?

Even then, this was only on the Run against API level 34... level 36 doesn't show any native errors.