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.
Related
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.
I am trying to migrate Crashlytics from Fabric to Firebase and in the documentation Upgrade to the Firebase Crashlytics SDK there is only a description for Cocoapods. I am not using Cocoapods in my project and don't want to, but I haven't found any alternative for installing the Firebase Crashlytics SDK. Does anyone has the same issue and found already a solution?
I have found this post from Saravana How to add Firebase Crashlytics to iOS app, but it is over one year old, so the SDK offered there is probably not the latest one.
This is my first question, please be kind :) And thanks a lot in advance!
Firebase is also distributed as a downloadable zip and via an experimental Carthage distribution.
So, after further research, there is a documentation for the installation without Cocoapods: Add Firebase to your iOS project.
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.
Is it possible to integrate Crashlytics with Xcode 6.2 ?
If no, is there any free crash reporting tool that can be integrated with an iOS that runs only on Xcode 6.2 ?
This is for an enterprise app which will not be submitted to the Apple appstore.
So, even if Crashlytics (now part of Fabric, by Twitter) is great, if it doesn't fit your needs then you can browse through the alternatives until you find one compatible:
Firebase by Google
SplunkMint (was Bugsense)
Crittercism (now Apteligent)
Instabug
HockeyApp by Microsoft
PLCrashReporter
AppDynamics
Also, migrating your project to be compatible with a newer version of Xcode shouldn't be that hard...
Recently I try to add Fabric & Crashlytics to my projects, but I got one link issue.
My base SDK is iOS7.0 and deployment target is 7.0 too, try to use the Fabric app for mac or cocoapods to add these frameworks, but always got error msg like this:
Anyone can assist?
Thanks a lot.
Add the run script provided by fabric to you. The follwing screenshot demonstrates where to add the runscript.
Reply from Mattie, Twitter Staff
Yes. It turns out that Crashlytics does not support building with a base SDK older than "latest" for any given Xcode release. It's extremely hard for us to maintain build compatibility with older SDKs, even if we can maintain runtime compatibility.
So I need change the base SDK to latest one and revamp my codes..