You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Platform you are using the Unity editor on: _____ Windows
Platform you are targeting: _____ Android
Scripting Runtime: _____ IL2CPP
[REQUIRED] Please describe the issue here:
As of FirebaseFirestore_10.7.0, the lib com.google.firebase.firebase-messaging-unity-.aar has a corrupted .jar of 1kb.
This makes it impossible for me to use the file in my custom activity.
With FirebaseMessaging_9.6.0.unitypackage the com.google.firebase.firebase-messaging-unity-.aar it's ok.
Steps to reproduce:
Download sdk and install FirebaseMessaging.unitypackage
Resolve dependencies
Open aar in android studio or unzip it.
The jar file will be corrupted.
The text was updated successfully, but these errors were encountered:
[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: _____2022.3.7
Firebase Unity SDK version: _____11.3.0
Source you installed the SDK: _____ FirebaseMessaging.unitypackage
Problematic Firebase Component: _____ FirebaseMessaging
Platform you are using the Unity editor on: _____ Windows
Platform you are targeting: _____ Android
Scripting Runtime: _____ IL2CPP
[REQUIRED] Please describe the issue here:
As of FirebaseFirestore_10.7.0, the lib com.google.firebase.firebase-messaging-unity-.aar has a corrupted .jar of 1kb.
This makes it impossible for me to use the file in my custom activity.
With FirebaseMessaging_9.6.0.unitypackage the com.google.firebase.firebase-messaging-unity-.aar it's ok.
Steps to reproduce:
Download sdk and install FirebaseMessaging.unitypackage
Resolve dependencies
Open aar in android studio or unzip it.
The jar file will be corrupted.
The text was updated successfully, but these errors were encountered: