I am getting stability alerts that my app is now going under 67% crash free users so of course I got scared:
I went to Fabric to check what was happening and I see absolutely no crashes:
I also checked Firebase since I migrated the project, and nothing shows up there either.
What might be going on here?
As a follow up,
The developer wrote in to support at fabric(at)support(dot)io and was able to have this issue resolved. The cause was an API key error, which caused reports to not be sent to the developers Fabric Dashboard.
Related
I am using firebase crashlytics. I am causing a crash by doing
firebase.crashlytics().crash()
and I am not seeing the crash report on the firebase dashboard. The crash is working because on android i get this screen
and on ios the app freezes and i get brought to this page on xcode
But on the crashlytics dashboard on firebase the crashes are not showing up.
Is there any reason why the crashes are not showing up on crashlytics dashboard? I am using react-native-firebase. I know i installed it correctly because I tried causing the crashes natively on android with java and I am able to see the crash on crashlytics.
TL;DR: run react-native run-android --variant=release for Crashlytics to begin working properly, assuming you've set everything up correctly (which it certainly appears you have since firebase.crashlytics().crash() is crashing your application.)
Please note - in order for react-native run-android --variant=release to function properly, you will have needed to configure your APK for release builds according to the directions here: https://facebook.github.io/react-native/docs/signed-apk-android
I've never been happier to see my crash free users rating decrease :)
Let me know if you have any questions! Setting up signing can be a little confusing, so let me know if you have any questions.
This is a very frustrating issue, but fortunately, I've found the solution and I'm in exactly the same boat you are.
See that big red screen? That's React Native's way of telling you, during development, that you've made some kind of mistake. What isn't immediately obvious is that this red screen prevents errors from making it through to our error reporting tools. Running your app in release mode will prevent React Native from showing that red screen, and your error reporting tools will be able to report crashes.
As Gian has pointed out in another answer to this question, it appears that firebase.crashlytics().crash() is not functioning properly. However, this isn't quite true. Whenever you are operating in debug mode (anytime you can see the red screen, you're in what I'm calling debug mode), Crashlytics and other crash reporting tools cannot catch Native Exceptions, but they can catch Javascript exceptions.
Once you run the application in release mode as I’ve described above, Crashlyitcs will be able to catch Native Exceptions. If you look into Crashlytics.crash(), it’s actually an crash intentionally written in Java. In order for Crashlytics to actually ‘hear’ that the application is crashed due to a Native Exception, you have to be running in release mode, not debug mode.
Sorry for beating the dead horse down here, but I’ve been looking into this issue all morning and felt it pertinent to share this information to others suffering the same fate as I was.
In iOS you need to unlink the app from Xcode so that it doesn't freeze when a crash occurs.
Build the App.
Stop the project in Xcode without terminating the simulator or
device.
Then you can crash without Xcode freezing.
Reopen the app so that Firebase can send the crash report.
For more details on this, see here in the Firebase documentation.
It will definitely help you
Go to Edit Scheme
Run -> Info
Change the Build Configuration to release.
Now run the App
And crash your app manually. Now you can check on your crashlytics dashboard
Try this as well
Launch your simulator/iPhone
Press stop
Launch your app and force a crash
Relaunch the app from simulator/iPhone
See the crash report in the crashlytics dashboard.
firebase.crashlytics().crash() its not working properly.
I purposely made a bug to simulate a crash when i tap a button and that crash was caught and shown in the Crashlytics Dashboard inmediately.
Ej: I work with React Native so i changed a this.props.etc... to this.state.etc...
to create an "undefined is not a function exception".
Hope it helps!
which version of #react-native-firebase/crashlytics do you have on your package.json?
you'll need to use one of the versions released after June 2020 because otherwise it doesn't have the Fabric removal change. For example, I have to update to
"#react-native-firebase/app": "11.2.0",
"#react-native-firebase/crashlytics": "11.2.0",
Here you can check versions available:
https://www.npmjs.com/package/#react-native-firebase/crashlytics
its stupid from Firebase Teams, but the solution is :
1- Force the crash
2- Launching the app with ide or cli
3- stop launching app from ide or cli
4- launch the app from smilator like user normal
And you will see the crashs in firebase console.
I have a android app in which Crittercism SDK is included and initialised as per standard documentation.
I intentionally put a loophole in the flow by which I can make app crash by manipulating data on my server and then pushing it to device.
Recently few users reported crash but I didnot see it on Crittercism website. So I simulated crashes. Out of 3 crashes I got report for 2 on Crittercism website and one was missed.
I waited for a day. And since 2 crashes made through, there is no issue with sdk integration in my app. (Its not NDK and crashes were of type malformed JSON during parsing) Not related to Java runtime crashes or other low level crashes.
Does any one face similar issue? How can we avoid this?
Thanks in advance.
I experienced a similar issue, but it concerned the automatic emails that you receive when a crash occurs. I found that identical crashes are usually only reported once.
The following Crittercism KB article explains why:
http://support.crittercism.com/articles/knowledge_base/Im-not-getting-an-email-every-time-the-app-crashes-whats-happening
I have been testing my application with my relatives through distribution via Google Play's alpha testing feature. Crashes have been showing under "Crashes & ANRS" for a while. However, there have been many crashes in the past few days but none have shown up on this page at all. I have spoken with them and they have assured me that there have been crashes and that they have been reporting them and sending them off to Google.
Does anyone know why the Crashes & ANRS page on the Google Play Developer Console doesn't pick up these crash reports anymore? I haven't contacted Google about this yet but I will do so now as well.
edit:
Okay so I just checked today and all of the crash reports have just shown up. I guess it can take up to a day or so for the reports to show up.
It was just a case of not being patient enough.
Okay so I just checked today and all of the crash reports have just shown up. I guess it can take up to a day or so for the reports to show up.
It was just a case of not being patient enough.
I can recommend you use Crittercism. Then you will have actionable crash reports immediately, both in release and during development if you so wish.
You can also know with some confidence whether your app is actually stable or not, and prioritise what you need to fix.
So, there are two points here:
1) It depends on the user's decision to 'Send Report' (or not) on any crash perceived during app usage. To check all of the stack traces generated by your application, you must implement third-party crash reporter or start testing Firebase Crash Reporting (https://firebase.google.com/docs/crash).
2) In my experience using the Google Play console, a reported crash/ANR may take some hours to reach your dashboard.
I am developing android application for client. Now client testing my application in various device. While testing, my application is crash at times. Now I need to know when and where the application crash.
How can I get the crash report from the device? Since my client does not have sdk and eclipse to view logcat error report.
There are mechanisms like ACRA that will let you obtain the crash reports from Android apps.
Instabug is a bug & crash reporting service and it’s just what you’re looking for.
It automatically sends a report containing all crash and device details once a crash occurs, plus it only takes a line of code to integrate in your app.
For full disclosure, I work at Instabug. Let me know if I can help.
By adding the Crash Report SDK in the project, You can view the released application crash log, which will help to locate problems.
Here is a demo page
I posted a free app and I've got a couple users who posted a comment saying that the app force closes in google's feedback. It's got a few hundred downloads in the day it's been up with an 84% retention rate. Google's error report in the developer's console says it has 0 errors. I've never had an app that reported any errors in the console. Does it actually work or am I getting fake reports of force closes? I'm a bit suspicious competitors might be posting the comments, but I don't have any way to confirm that the error reporting google provides does actually work.
As far as I know, the 'Report' button is only available on devices running FroYo (2.2) or later, which is very few.
At least I've never seen the ability to report an error upon force close.
I don't think there's any reason to assume your users are lying to you. But it's always a good idea to include something in your app that'll allow for the users to submit an error from within the application.
http://groups.google.com/group/android-developers/browse_thread/thread/ddf6863e9a31052f?pli=1
you could use this project http://code.google.com/p/android-remote-stacktrace/ to verify