Visitar URL original
[Bug] Crashlytics not sending crashes to the console when using *.tgz and UPM · Issue #1116 · firebase/quickstart-unity · GitHub
Skip to content

[Bug] Crashlytics not sending crashes to the console when using *.tgz and UPM #1116

Description

@jamier-hh

[REQUIRED] Please fill in the following fields:

  • Unity editor version: 2019.4.26f1
  • Firebase Unity SDK version: 8.1.0
  • Source you installed the SDK: UPM
  • Problematic Firebase Component: Crashlytics
  • Other Firebase Components in use: Core, Analytics
  • Additional SDKs you are using: Facebook, AppLovin MaxSDK
  • Platform you are using the Unity editor on: Mac
  • Platform you are targeting: iOS
  • Scripting Runtime: IL2CPP

[REQUIRED] Crashlytics not sending crashes to the console:

I wasn't sure where to add this issue. It seems to be specific to Unity when using iOS. Whenever including Crashlyitcs via UPM using *.tgz, Crashlytics does not seem to initialize properly and crashes will not get sent to the console. I've tried installing them via our custom registry as well directly in the project and it does not seem to make a difference.

Using the same GoogleService-Info.plist file, I've been able to send reports when using the *.unitypackage version of Crashlytics. I've removed my test *.plist for privacy purposes.

Steps to reproduce:

  1. Open attached project.
  2. Add the following tarball to the Packages folder: com.google.firebase.crashlytics-8.1.0.tgz, com.google.external-dependency-manager-1.2.166.tgz, com.google.firebase.analytics-8.1.0.tgz, com.google.firebase.app-8.1.0.tgz
  3. Add the GoogleService-info.plist to the Assets/* folder.
  4. Build for iOS
  5. Deploy to device. Crashes should happen automatically.
  6. Check the console and see no crashes.
    Have you been able to reproduce this issue with just the Firebase Unity quickstarts (this GitHub project)?
    What's the issue repro rate? 100%

What happened? How can we make the problem occur?
No errors are reported to the Crashlytics dashboard.

If you have a downloadable sample project that reproduces the bug you're reporting, you will
likely receive a faster response on your issue.

TestingPackages.zip

Activity

  1. changed the title [-][Bug] [/-] [+][Bug] Crashlytics not sending crashes to the console[/+] on Aug 18, 2021
  2. changed the title [-][Bug] Crashlytics not sending crashes to the console[/-] [+][Bug] Crashlytics not sending crashes to the console when using *.tgz and UPM[/+] on Aug 18, 2021
  3. paulinon commented on Aug 19, 2021

    @paulinon
    Contributor

    Hi @jamier-hh,

    In order to identify what's causing this behvaior, could you provide the debug logs for your iOS build after enabling debug logging?

  4. jamier-hh commented on Aug 19, 2021

    @jamier-hh
    Author

    I've included both since for whatever reason, the repro-projects logs aren't as good. The game logs are edited to remove identifying information but nothing pertinent should have been removed.

  5. added and removed
    needs-infoNeed information for the developer
    on Aug 19, 2021
  6. paulinon commented on Aug 20, 2021

    @paulinon
    Contributor

    Thanks for the additional information, @jamier-hh. Could you also verify if you're getting a similar result when using our quickstart?

  7. added
    needs-infoNeed information for the developer
    and removed on Aug 20, 2021
  8. jamier-hh commented on Aug 20, 2021

    @jamier-hh
    Author

    Hmm very odd. It seems to be working with the quickstart.

  9. 25 remaining items

  10. jamier-hh commented on Sep 10, 2021

    @jamier-hh
    Author

    The original issue was iOS only, which was probably lost in my assertation of what the issue actually was - sorry about that. If you try the same steps for iOS, and open the project in Xcode. Specifically the Firebase.App.Crashlytics*.cpp files will be missing from the Classes/Native folder.

    I've attached a version of the test app that reproduces the issue. You just need to add the dependencies to the package folder:

    • com.google.external-dependency-manager-1.2.166.tgz
    • com.google.firebase.analytics-8.1.0.tgz
    • com.google.firebase.app-8.1.0.tgz
    • com.google.firebase.crashlytics-8.1.0.tgz
  11. added and removed
    needs-infoNeed information for the developer
    on Sep 10, 2021
  12. DellaBitta commented on Sep 10, 2021

    @DellaBitta
    Contributor

    Ok, thanks for the quickly follow up @jamier-hh. I was able to reproduce this behavior, and I'm sorry for the confusion about the Android target.

  13. chkuang-g commented on Sep 14, 2021

    @chkuang-g
    Contributor

    Interesting, looks like the prevention we put in Crashlytics no longer works.

    Ex. this attribute, or the link.xml (This file is not found on firebase-unity-sdk. But probably just an unrelated issue.)

    <linker>
    <assembly fullname="Firebase.Crashlytics" ignoreIfMissing="1">
        <namespace fullname="Firebase.Crashlytics" preserve="all"/>
    </assembly>
    </linker>
    

    It is pretty odd that this only affect .tgz but not .unitypackage.

  14. hegi25 commented on Oct 29, 2021

    @hegi25

    Note that link.xml files are not supported inside packages, but you can reference package assemblies from non-package link.xml files.

    You can put this link.xml file into your main Assets folder and the .tgz version will work.

  15. self-assigned this
    on Oct 24, 2022
  16. a-maurice commented on Oct 28, 2022

    @a-maurice
    Contributor

    This will be fixed with the upcoming 10.1.0 Firebase Unity SDK, so closing the issue.

  17. locked and limited conversation to collaborators on Nov 27, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions