-
Notifications
You must be signed in to change notification settings - Fork 212
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]: v3.5.3 crashes when trying to initialize #934
Comments
Hi @TheMeanCanEHdian thanks for reaching out! I see you are on an older version of our SDK; we'll look into reproducing this on v3, but I wanted to flag that we currently have an updated major release with many improvements and enhancements. I'd suggest checking out our Migration Guide and upgrading as this should resolve this error. Please let us know if you have any additional questions or concerns! |
Hi @jennantilla, Thank you for the reply. I have tried migrating to v5, but I have also run into issues there with the Notification Service Extension. I opened a bug report here: |
@jennantilla I have isolated the issue to an interaction between OneSignal and PurchasesFlutter. I have tested OneSignal v3.5.3 against PurchasesFlutter v6.29.2 (recommended on issue #694), v6.30.2 (the latest on their old SDK), and v8.1.1 (the latest on the newest SDK). Here is an example app for Android that adds minimal code to get OneSignal to initialize and simply has the PurchasesFlutter dependency included in the pubspec. Removing PurchasesFlutter from the pubspec or disabling the OneSignal initialization prevents this issue. Added OneSignal Code:
Added PurchasesFlutter Code:
Debug Output
|
What happened?
I am in the progress of updating my app. However, when OneSignal v3 tries to initialize it is crashing.
I am using Flutter v3.24.0.
Steps to reproduce?
What did you expect to happen?
I expect OneSignal to initialize successfully
OneSignal Flutter SDK version
3.4.3
Which platform(s) are affected?
Relevant log output
Code of Conduct
The text was updated successfully, but these errors were encountered: