Skip to content
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

corrupted com.google.firebase.firebase-messaging-unity-***.aar #1351

Open
shifugate opened this issue Aug 15, 2023 · 2 comments
Open

corrupted com.google.firebase.firebase-messaging-unity-***.aar #1351

shifugate opened this issue Aug 15, 2023 · 2 comments
Labels
new New issue.

Comments

@shifugate
Copy link

[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
    Screenshot 2023-08-16 001317
    Screenshot 2023-08-16 001255

  • 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.

@shifugate shifugate added the new New issue. label Aug 15, 2023
@GTPaulo
Copy link

GTPaulo commented Apr 4, 2024

This issue still exists in 11.8.1

@OlivierHokke
Copy link

Also having this issue on 11.8.1 and 11.8.0
Any indications on when this may be fixed?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new New issue.
Projects
None yet
Development

No branches or pull requests

3 participants