-
Notifications
You must be signed in to change notification settings - Fork 371
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: OneSignal.initWithContext() crashes on minified builds (5.0.0) #1811
Comments
@matejsemancik Thank you for reaching out! We're looking into this and will get back to you as soon as possible. |
I can verify this same behavior in our application after updating to 5.0.0. The library works fine in a development environment without minification but fails on release builds due to minification. |
If someone tries to fix this problem, here's more readable output of the same error. I got it by keeping all classes of
|
I tried here #1810 (comment) to convert the old rules |
Still broken on 5.0.1 |
Closing as a Duplicate of #1810 |
What happened?
The latest (5.0.0) version of SDK crashes during initialization using
OneSignal.initWithContext(Context, String)
methodwhen executed on application build minified by R8.
The attached crash log is extracted from my application's Crashlytics. (Android Gradle Plugin 8.1.0, Kotlin 1.8.22)
The same crash happens on OneSignalDemo example app. (Android Gradle Plugin 7.0.4, Kotlin 1.4.32)
This might be related to #1810
I temporarily worked around this issue by excluding entire OneSignal SDK from my proguard rules, but I see that as not very ideal solution.
Steps to reproduce?
What did you expect to happen?
I expected SDK to initialize without any issues and for the app to not crash during startup on obfuscated release build of application.
OneSignal Android SDK version
5.0.0
Android version
13
Specific Android models
No response
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: