Closed pgawlowski closed 4 years ago
I found a few problems with this issue:
Thanks for reporting the issue, @pgawlowski . May I know if you have removed your Fabric API key or made any changes in the setup? You may check out the docs here for more details.
Also, could you try to undo removing of info.plist, and perform a test crash on debug mode to see if you'll receive a "Report submission successful" message?
Yes I removed Fabric API Key from info.plist.
When it is present this part
Crashlytics.sharedInstance.debugMode = true
seems to have no effect at all - crashlytics logs are empty. Not a single message about sending, success or failure is present. What is more Firebase Console is not reporting any kind of effect. Stats are unaffected, issues are still empty.
The test you mentioned is the one I am using for the whole time.
Hi @pgawlowski, as per docs(https://firebase.google.com/docs/crashlytics/migration-post-linking#what-happened), you shouldn’t remove the Fabric API key and not making changes on the setup. Please undo the changes you have made. If you’re still getting the same successful message but not receiving any reports, please file to Firebase Support (https://firebase.google.com/support) in order for them to help you fix the issue on receiving reports.
@rizafran - read my last post. As soon as I reverted changes to info.plist Crashlytics is not responding at all. No logs at all. Nothing is being reported. Not a single log about Crashlytics.
Like I mentioned
Crashlytics.sharedInstance.debugMode = true
this seems to have no effect as soon as I revert info.plist to original values.
After discarding all changes and starting from scratch it seems to work fine now. No idea what was the initial problem with issues + Crashlytics still has some some logging problems - nothing is happening when "Fabric" key is present in info.plist.
Glad to hear you are up and running! :)
Describe your environment
Describe the problem
After migration from Fabric to Firebase I encountered multiple problems with Crashlitics. I followed this guide. (https://firebase.google.com/docs/crashlytics/get-started?fbclid=IwAR0YuotcIwobzk_3BOfQIKxVh-2129nlt1Z26pi5muzjZ2YkJq7ObwSMd0w) and used test implementation part to verify if it works fine.
Effect is:
To sum up. I am using debug format DWARF + dSYM. I removed info.plist old "Fabric" section (not a single firebase + crashlitics tutorial mention this part). Only in that case Crashlitics.sharedInstance.debugMode = true seems to be working correctly.
Crashlitics logs are showing, inter alia:
So far it's been around 48h of struggling with that problem so, even assuming pretty long firebase delay, issues supposed to be there.