-
Notifications
You must be signed in to change notification settings - Fork 428
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
Android app crash caused by using Remote Config with other SDK and EDM4U resolution conflict #846
Comments
[REQUIRED] Please fill in the following fields: Unity editor version: 2019.4.13f1_____ [REQUIRED] Please describe the issue here: |
Same issue here. Unity editor version: 2019.4.12f1 Please describe the issue here: Unable to find Method com/google/firebase/remoteconfig/FirebaseRemoteConfig.activateFetched (signature '()Z', instance). Please verify the AAR which contains the com/google/firebase/remoteconfig/FirebaseRemoteConfig class is included in your app. Longer log snippit:
|
It looks like it should be calling 'activate' instead of 'activateFetched'. We keep running into these issues where the Unity package is calling old deprecated functions. Does anyone have a work around? |
As mentioned this seems to be the same issue as In this case. Unity RemoteConfig package is expecting 19.2.0. I assume that no longer exists. it resolves to 2.0.0 which removed the deprecated call 'activateFetched'. Going to try the same workaround as 758. I will again note these workarounds prevent us from using tools like Unity Cloud Build so we need to find a long-term solution to this kind of error. |
I meet the same question.It's too bad. |
@cszhongit @lfg-ryan
|
this is a great answer ,it's useful for me .Thank you! |
Y'all have done an excellent job identifying the symptom: For my first two questions:
I see that all reporters are using the Package Manager to manage Firebase. Are you also all resolving dependencies into If you look in
Finally, in the "Android Resolver Settings" window, if you're still running into issues, can you turn on "Verbose Logging". Then force resolve the dependencies and paste your Unity editor log? |
I'm afraid that this does seems to be similar to #758 where some other packages forced EDM4U to bump up the version. I installed all Firebase plugins you mentioned and was not able to reproduce the issue. Therefore, I suspect this is related to other packages, such as IronSource. Could you provide the text in the windows when you click on In general, when you are using Gradle 5, which is the one EDM4U is using now, Your script which change I would recommend you to downgrade other packages instead. |
|
This is the |
So interesting, it's just working now? Does anyone else with this issue find that it resolves itself like this? |
Still broken for me with a fresh force resolve. I did however forget to follow up that the technique from the other bug works. I downloaded the 19.2.0, renamed it to 20.0.0 and it works. As mentioned it would be great to get this working for Cloud Build purposes where that fix is not really an option in a Resolve on build world. Here are the details. Resolved to config-20.0.0
Debug on a force resolve attached. I am putting the files in Assets/Plugins/Android and not using a custom gradle. |
This also worked great for me. I added the file. I now can have resolve on build checked and Unity Cloud Build works just fine. Thank you very much. |
Analyzing all these recent posts, I think there are two key issues.
I think the first step would be changing how Firebase specify Android dependency ranges in Note that this will NOT prevent future dependency conflict. Also, this cannot resolve when any team makes breaking changes in patch release, which is unlikely to happen but you'll never know. |
Same issue for me. I ended up modifying the version of remote config inside the RemoteConfigDependencies.xml file directly for now. Is there a solution coming up? |
Same issue, I just started using the RemoteConfig 7.0.0 using Unity Package Manager (released 2nd Dec), built and stumbled upon same error as OP. For now I went into mainTemplate.gradle and changed to 19.2.0. |
I also started Firebase 7.0.0 and I'm getting similar issues on remote config on Android. IOS seems fine. |
Me too. Having exactly same issue if I am using firebase-config:20.0.0 |
Is there any complete solution for this problem ? firebase-config 20.0.0 [Edit] making mainTempleta.gradle and changed to 19.20.0 fixed problem for now |
[REQUIRED] Please fill in the following fields:
[REQUIRED] Please describe the issue here:
(Please list the full steps to reproduce the issue. Include device logs, Unity logs, and stack traces if available.)
I'm getting an exception:
E/firebase: Unable to find Method com/google/firebase/remoteconfig/FirebaseRemoteConfig.activateFetched (signature '()Z', instance). Please verify the AAR which contains the com/google/firebase/remoteconfig/FirebaseRemoteConfig class is included in your app.
things seemed to be working with firebase version 6.16.1 before today but today things stopped working and I think it's related to new firebase arr files that are being used:
new files:
old files:
```
Assets/Plugins/Android/com.google.firebase.firebase-abt-19.1.0.aar
Assets/Plugins/Android/com.google.firebase.firebase-analytics-17.6.0.aar
Assets/Plugins/Android/com.google.firebase.firebase-auth-19.4.0.aar
Assets/Plugins/Android/com.google.firebase.firebase-config-19.2.0.aar
Assets/Plugins/Android/com.google.firebase.firebase-iid-20.3.0.aar
Assets/Plugins/Android/com.google.firebase.firebase-messaging-20.3.0.aar
The text was updated successfully, but these errors were encountered: