Firebase iOS Crashlytics stuck at Add SDK - ios

My iOS app is live with Appstore.In my app ,I was using Fabric Crashlytics SDK.I missed too upgrade to updated Firebase Crashlytics SDK before 15 November 2020.Yesterday,I updated it to updated Firebase Crashlytics.But on Console it is still showing Add SDK page.
On Home Screen it shows crash details but not crash report & crash count.
Please help.
Thanks in advance.

Related

Downgrading Facebook SDK for iOS 9 application

Referring to the question here
ios facebook login sdk 4.28.0 error code 3
I am facing the same issue. Trying to run the app on iOS 9 device, I receive the same error. The problem now is that the required versions are not available as Cocoapods. Tried to update using GitHub link I got the attached error.
Thanks

After migration my iOS app from Fabric to Firebase crashes still appearing in Fabric

I did the migration asked from Google because Fabric will die next year.
But the crashes reports still are available in Fabric. They are available in both tools: Firebase and Fabric.
Looking the Docs, they still asks you to include Fabric library in your app (https://firebase.google.com/docs/crashlytics/get-started?platform=ios)
So, it's something wrong in my migration?
Firebase uses the same Fabric Crashlytics SDK to calculate the crashes on both Fabric and Firebase dashboards. After March 31st 2020 Fabric Crashlytics dashboard will deprecate and developer use only Firebase Crashlytics for their crash information.
Fabric won't show your crash after 31st march so better migrate your project from fabric to firebase.
Firebase still uses fabric Crashlytics SDK to calculate errors but the dashboard of firebase won't show anything.

Crash Report for Flutter

I am new to flutter. I developed one Wallpaper App using flutter and upload in playstore. Now i need to track crash report for that app. In Android have crashlytics to all report crash and more fearure's. Is crashlytics support in flutter ?. I looked sentry plugin but it's not free. Any help Appreciable.
Sentry is currently the only solution provided by the Flutter team.
Crashlytics support is planned https://github.com/flutter/flutter/issues/14765
update
There is now a community package with crashlytics support as well https://pub.dartlang.org/packages/flutter_crashlytics
note this:
since April 2020 fabric crashlytics panel will no longer be supported so you have to use firebase crashlytics panel instead
solution:
for that flutter team now has created firebase_crashlytics.
so you can use this library instead of the flutter_crashlytics which is the community version.

iOS Hockey SDK not reporting crashes

I have installed hockey sdk on my native iOS application via cocoapods.
I've installed the default sdk using:
pod 'HockeySDK'
In my appDelegete I added the following lines:
BITHockeyManager.shared().configure(withIdentifier: "myID")
BITHockeyManager.shared().start()
The app Identifier is correct with the one on the hockeyApp dashboard, I'm sure about it because the user is correctly traced.
The problem is that the sdk does not report crashes of the app.
I've installed the application and then disconnected the cable and reopend the app. When the app crashes and when then i reopen the application a prompt does not appear to me.
What could be the problem? Maybe I missing something on the the installation of the Hockey SDK?
Thanks all

add crittercism sdk to my ios app

I'm trying to use crittercism to know the crash in my app, the problem is that when crittercism have a crash report to send of web service, my app crash. so I can not open the app again.
The only possible to open the app is, run again the app with xcode, put a break point unit the line [Crittercism enableWithAppID:#"XXXXXXXXXXXXXXXXX"]; and run line per line.
In this moment crittercism send the report and I can run my app normally.
What can I do to resolve this ?
To additional information I am using, ios 8.3 in ipod 5g and xcode 6.3
Thanks.
One of the founders of Crittercism here. Which version of the Crittercism SDK are you using? There was a small bug in v5.1.5 of the iOS SDK that we're fixing now which may be causing that issue. If you downgrade to v5.1.3, it should work:
http://docs.crittercism.com/downloads/downloads.html
Take care
Rob

Resources