-
Notifications
You must be signed in to change notification settings - Fork 369
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]: Crash on 5.0.0 - "Unrecognized operation: login-user-from-subscription" #1814
Comments
Hi @tajchert thanks for reaching out! We'll investigate this. Just to confirm, this does not happen with every device you've tested, only some? Are you migrating from a previous version of our SDK or is this a fresh install of 5.0.0? |
Hi, I don't know if in case of those users it was upgrade or clean install sadly. |
I am having the same issue on my side after upgrading to version 5. I can see that it's happening on Android 12 and 13 too. |
I am having same issue as well. Checked on Android 13.
I would like to mention that I am not a native android developer, instead I write extensions for App Inventor with codes. I changed few things in Work Manager and wrote manifest manually. Seems to be similar to this: |
Not publishing the proguard rules of version 5.0 is a big novice. Not good for such a big company. Release proguard rules for 5.x versions urgently. |
I'm getting the same issue reported by Firebase Crashlytics. Here's a sample of one of the crashes copied from Firebase:
|
any news? |
I'm having the same issue. Help, please. |
I ended up removing OneSignal, but I might realize it might not be so easy for others to do it right away. |
the bug is missing operation "login-user-from-subscription" management |
What's the status on this? It is holding back a big release for us and going back to earlier OneSignal version is not really an option, as it is not compatible with other latest versions of firebase packages and gradle. |
This issue has caused serious drop of our users (our app is used by over 5M users), and it seems no one cares about it. |
Nothing yet? |
Please, I don't want to end up removing OneSignal. |
The proguard issues should be resolved in version 5.0.1. If anyone is still seeing crashes only for release (minify) builds please tag me and post the stack trace |
We don't have the minify enabled for release builds, but we are still seeing this crash. |
I apologize this seems like a separate issue, I have identified the issue and it will be resolved in the next release. Thank you for your patience. |
ETA @emawby ? |
Any possible workaround until we wait for the next release @emawby ? I'm using it on Unity. |
Same Issue Here |
What's the ETA on this release please? We're getting thousands of crashes because of this and we can't rollback the version number at this stage. |
I think they've fixed it and released a new version v5.0.1. |
I tried installing v5.0.1 but I'm still getting the same crashes... |
@chriscborg Yeah, kinda figured! I'm pretty much sure they're trying to fix this ASAP but to make sure everything is stable for you right now, try to rollback as much as you can until a stable version gets released! |
This specific Unrecognized operation: login-user-from-subscription issue has been resolved in OneSignal-Android-SDK 5.0.2 If you are still seeing this exact issue after updating let us know and we can reopen this issue. |
I confirm the issue is still there in V5.0.2 |
@Neferetheka Can you provide more details on the error. There have been multiple crashes on startup with different stack traces so if you could post it that would be very helpful. |
W/System.err: java.lang.reflect.InvocationTargetException Still hapening on v5.0.4 |
flutter: 3.19.6
|
What happened?
I see crash on few devices (Android 11 and 10 for sure).
This is on calling
OneSignal.initWithContext()
Steps to reproduce?
-
What did you expect to happen?
OneSignal Android SDK version
5.0.0
Android version
11, 10
Specific Android models
Relevant log output
The text was updated successfully, but these errors were encountered: