quickstart-unity: JniResultCallback.onCompletion Deadlocked, ANR In Firebase Unity SDK 8.9.0
[READ] For Firebase Unity SDK issues, please report to Firebase Unity open-source
Once you’ve read this section and determined that your issue is appropriate for this repository, please delete this section.
[REQUIRED] Please fill in the following fields:
Unity editor version: 2020.3.22f1 Firebase Unity SDK version: 8.9.0 Source you installed the SDK: .unitypackage Problematic Firebase Component: Cloud Messaging Other Firebase Components in use: Auth, Database, Remote Config Additional SDKs you are using: Facebook, IronSource, Adjust Platform you are using the Unity editor on: Mac Platform you are targeting: Android and iOS Scripting Runtime: IL2CPP
[REQUIRED] Please describe the issue here:
Steps to reproduce:
Possible steps:
- run the app from background, maybe push
Relevant Code:
// TODO(you): code here to reproduce the problem
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 1
- Comments: 56 (8 by maintainers)
Hi all,
I believe we’ve identified the root cause of the problem, and it will be addressed with the next release.
We weren’t able to reproduce this, due to the nature of how inconsistent the issue seems to be, but thanks to the callstacks that you all provided, this issue will hopefully be fixed with this fix.
Were observing that the issue is resolved. Rolled out an update 2 days ago and have not seen any occurrences of it since.
@DFC005 I’m aiming for later this week, some of our dependencies had an update that delayed it a bit.
You might want to wait before updating if you’re using RemoteConfig, there’s a breaking issue on initialization in a build: https://github.com/firebase/firebase-unity-sdk/issues/751
Alright, the release is out now, 11.1.0, https://github.com/firebase/firebase-unity-sdk/releases/tag/v11.1.0
I’m going to close this issue, to indicate that this should hopefully be fixed, at least this specific Messaging one. If there are still problems, feel free to either respond in this issue, or file a new one.
Normally it does not work in that way. Firebase should mention this in their release notes If they fixed something related, It does not make sense to update the SDK based on just an assumption.