We have an existing app that has Crashlytics implemented. As I understand, App Not Responding report in Crashlytics is only for Android 11 and above, which most of our traffic meets as a condition.
In Crashlytics, I can see % for crash free users, total users and total crashed but - for ANR metric. How can I implement this?
Thanks.
Related
Crashlytics report is showing much less crashes than the actual amount. My App has over 20k active users and crashlytics reports only 18 crashes but 97.55% crash-free users.
Crashlytics Screenshot
I also implemented Flurry and it shows much more reasonable numbers, but the stack-trace is not as good as crashlytics.
Is there any way to get the correct number of crashes in crashlytics?
I started using Firestore recently (Free plan) in my iOS app, the app is in Production now, and I see huge discrepancy in the number of Reads. App Engine Quota shows 1M reads of 0.05M (free quota) (Cloud Firestore Read Operations), while Firebase Console (Database tab) shows just a one hundred reads for today - 10,000 times difference!
The app can still read the data from the servers (it's not from cache as I tried to delete the app and reinstall), so the Firestore functionality is not limited by exceeding the free quota.
Each app user can read only one document (via listener) with applied security rules, and it reads own document only 3-5 times per session. There are about 50 users so far, so the expected number of reads matches Firebase console.
Is there a known bug in App Engine console?
Is there a way or free tool to understand the source of all those reads?
Which reporting tool is more reliable in general - Firebase Console or App Engine Console?
I appreciate your help guys!
The Crashlytics dashboard is showing Crash-free statistics but there is no crash in the ISSUES table.
Knowns:
Latest Fabric and Crashlytics following the Firebase tutorial
Forced a crash using Crashlytics.sharedInstance().crash()
In appdelegate I set FirebaseApp.configure()
App is not on Appstore, but I uploaded the dsyms from the xarchive package
That can happen from time and here's why - when a session ends in a crash, the small amount of data that needs to be sent to know that the crash occurred can safely be sent. However, the crash report is larger, so it can't be sent safely until your users relaunch the app. Once your users do that, the crash report will be sent and you'll be able to dive into the details. Let me know if that clears it up or if you have any other questions!
I've been using FCM console(web) to test push notification for Android smartphone.
I use push token from Android device, but FCM console says "Completed" and it's not delivered.
It worked fine before, but recent few days, it's not working.
Is there anyone facing same problem?
I got an answer from FCM support team.
Thank you for that information.
It would seem that you are affected by the changes made between July
31 and August 1st. We rolled out a change to Firebase Notifications to
filter apps by GMP App Id rather than by package name. This change was
purely internal and should have had no effect on visible behavior as
all apps using Firebase should have had both package name and app id
set to match. However, we are now seeing some apps that have the wrong
app id set and this is causing messages to not be delivered (or in
some cases to be delivered to the wrong app if an app has the app id
of another app). These apps have a bug that was previously masked but
is now exposed.
We are investigating ways in which apps have sent these incorrect app
ids and ways in which we can catch them and warn app developers.
For now, the Firebase Notifications console will only work with apps
that use the FCM SDK. We recommend updating to the latest version of
the FCM SDK in order to mitigate the issue, but in case you don't want
to migrate to FCM SDK, you can still use your own server to send push
notifications.
Apologies for the inconvenience this may have caused. Please let me
know if there's anything else I could help with.
Regards,
I've been using Crashlytics in application, our client using HockeyApp, and I came to know by the recent updates to Google Firebase.
Has anyone had a chance to use above tools, what are your overview and suggestion? Did you like one over the other... and why?
Have a great day.
I'm afraid I can't speak for HockeyApp at all, but I have some experience in using Firebase and Crashlytics using iOS and Android clients. The below paragraphs don't factor in HockeyApp, and only compare Firebase Crash Reporting to Crashlytics.
Of the two, I would depend on Crashlytics for crash reporting until Firebase can further revise features. I've implemented both in some apps, and there are some advantages to Crashlytics. They send email notifications when crashes occur, including for priority changes, and crashes appear very quickly in the interface, within 5 minutes typically.
As it currently stands, Firebase doesn't have crash notifications, and it can take 20-40 minutes for a crash report to appear in the dashboard. A benefit of using Firebase's reporting is that their analytics will create an audience group of crash experiencing users, allowing you to identify and provide a different experience for those users (push notification, welcome screen, coupon code, etc)
Both:
Ability to report logs for crashes to investigate interaction and
function
Crashlytics:
~5 minute reporting time
Email notifications
Firebase:
20-40 minute reporting time
Richer user data
Can redact some logged info: "Logged in Chris" could become "Logged in [REDACTED_US_MALE_NAME]"