search

firebase / quickstart-unity

Firebase Quickstart Samples for Unity
https://firebase.google.com/games
Apache License 2.0
819 stars 424 forks source link

java.lang.UnsatisfiedLinkError on CppStorageListener #1322

Closed gclaret closed 1 year ago

gclaret commented 1 year ago

We started seeing this error on our Unity game. We tried updating firebase libraries to the latest (10.4.0), and it's still happening. We cannot reproduce it locally, but see it when we do a live push of our app.

[REQUIRED] Please fill in the following fields:

Unity editor version: 2021.3.13f1 Firebase Unity SDK version: 10.4.0 (but was also happening in 9.x) Source you installed the SDK: .unitypackage Problematic Firebase Component: storage Other Firebase Components in use: auth, messaging, firestore Additional SDKs you are using: Applovin, singular Platform you are using the Unity editor on: Mac Platform you are targeting: Android Scripting Runtime: IL2CPP

image
google-oss-bot commented 1 year ago

This issue does not seem to follow the issue template. Make sure you provide all the required information.

chkuang-g commented 1 year ago

Could you provide snippet of code about how you use Storage APIs?

The implementation of nativeCallback should be here and is pretty fundamental to Storage API. The implementation should be this https://github.com/firebase/firebase-cpp-sdk/blob/8f3e19226639a3b91e5d879cdf5f3d867dbf8db4/storage/src/android/controller_android.cc#L227

We did not see this issue from our daily testapp. Therefore we would like to learn more about your situation.

Ex.

Thank you!

google-oss-bot commented 1 year ago

Hey @gclaret. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.

If you have more information that will help us get to the bottom of this, just add a comment!

google-oss-bot commented 1 year ago

Since there haven't been any recent updates here, I am going to close this issue.

@gclaret if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.