Repository navigation
[Bug] Crashlytics not sending crashes to the console when using *.tgz and UPM #1116
Description
Activity
- changed the title
[-][Bug] [/-][+][Bug] Crashlytics not sending crashes to the console[/+]on Aug 18, 2021 - 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 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?
- addedneeds-infoNeed information for the developerNeed information for the developer
on Aug 19, 2021 - Slightly edited game log: game-debug.log
- Repo-project log: repro-debug-logs.log
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.
- addedneeds-attentionNeed Googler's attentionNeed Googler's attentionand removedneeds-infoNeed information for the developerNeed information for the developer
on Aug 19, 2021 Thanks for the additional information, @jamier-hh. Could you also verify if you're getting a similar result when using our quickstart?
- addedneeds-infoNeed information for the developerNeed information for the developerand removedneeds-attentionNeed Googler's attentionNeed Googler's attention
on Aug 20, 2021 Hmm very odd. It seems to be working with the quickstart.
25 remaining items
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*.cppfiles will be missing from theClasses/Nativefolder.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
- addedneeds-attentionNeed Googler's attentionNeed Googler's attentionand removedneeds-infoNeed information for the developerNeed information for the developer
on Sep 10, 2021 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.
Reacted by jamier-hh- added and removedneeds-attentionNeed Googler's attentionNeed Googler's attention
on Sep 10, 2021 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
.tgzbut not.unitypackage.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.xmlfile into your main Assets folder and the.tgzversion will work.This will be fixed with the upcoming 10.1.0 Firebase Unity SDK, so closing the issue.
- locked and limited conversation to collaborators
on Nov 27, 2022
[REQUIRED] Please fill in the following fields:
[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:
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