-
-
Notifications
You must be signed in to change notification settings - Fork 32
coreLibraryDesugaring breaks Sentry #476
Comments
hey @PaulWoitaschek thanks for raising this, we'll have a look at it |
@marandaneto If I were you I'd either go with moshi with the code gen or use kotlin serialization. |
@PaulWoitaschek which device/API have you used? I can't reproduce it on 2 of my devices. We can't use Kotlin features, this SDK will be the base of the new sentry-java where Kotlin is not that popular yet. |
Are you sure you did ran it in release mode? This is the device:
|
thanks, yes, I'll try after lunch again, the only difference was |
ok I could reproduce it, it looks like a Gson bug:
|
some development in the investigation, but I still don't have a fix. I'm wondering if it's something related to this: https://developer.android.com/distribute/best-practices/develop/restrictions-non-sdk-interfaces
|
so I found out the issue, but I'm gonna raise an issue to the R8 team as well, I'll release a fix for now.
I'll |
@PaulWoitaschek I've got a fix for this, #478 and this would avoid reflection for this class and its children, I'll do a bit more of testing and if all good, you can expect a new version on Monday morning :) |
@marandaneto thanks for all the work, was just curious is there any ETA on when this pull request might appear in new release? thanks |
released: https://github.com/getsentry/sentry-android/releases/tag/2.2.1 let us know if you find any issues, thanks for reporting this. |
Thanks for tackling this so quickly! |
JFI: I've raised an issue on R8 team https://issuetracker.google.com/issues/160909126 |
Btw, checking back on this; our events are now arriving! |
Enabling coreLibraryDesugaring is incompatible with sentry 2.2.0
To reproduce this, add coreLibraryDesugaring to your application and now no events will be sent.
Here is an example project that demonstrates the issue: (it's the official sample)
PaulWoitaschek@167cd61
Just install it to your device in release mode:
./gradlew sentry-sample:installRelease
Click on
Capture exception
And you'll see the stacktrace in your log:
The text was updated successfully, but these errors were encountered: