I followed all the Fabric documentation concerning crash reports for iOS.
I can see my first crash test on the dashboard, but now the App is on the AppStore, and I see no crashes, no active users, no data at all on the Fabric App.
But I know there are a lot of users right now, we can see all the stats for Android.
How can we make this solution working for iOS ?
you might want to check 3 things:
missing dYSIM
runscript
plist
Related
I have an iOS app in the store written in Swift that seemed to be working fine for the last 2 years. However, in the recent past, users reported that the app was crashing after they updated to iOS 13.5.1.
During this time, several other notable apps like Spotify, Pinterest, Tiktok ad Instagram were crashing as well due to some Facebook SDK bug which they claimed to have fixed.
None the less, I removed the Facebook SDK from the app and resubmitted the app as an update hoping to fix this issue.
Users have installed the new updated and some users have even updated to iOS 13.6. A few users have reported crashes again on app launch.
The problem is I am unable to reproduce the crash on a device or a simulator.
I was wondering and hoping someone ran into this issue and has any ideas on how to resolve this ?
Edit
Here are the crash logs I see from the app store after the advice from Benjamin below: https://pastebin.com/BPbn77T8 - when I click open in project: http://prntscr.com/tpnxp1 - it leads me to this line of code in the project
let classification = aDecoder.decodeObject(forKey: "classification") as! String
I know it is not a lot of code to work with but this issue never occurred before the latest iOS 13.4 update that I know off.
Thanks
Issues like this - where a user reports a crash that you cannot replicate locally - are why remote logging is important.
The best way to solve an issue like this is to enable remote logging/crash reporting BEFORE the issue arises. That way you have logs and stack traces that can help you see what caused the crash.
For more info, take a look at services like Google Crashlytics, Datadog, or New Relic. I’m not advocating for any. There are many services out there. But those are some common examples.
I have to work with 2 different SDKs which should report the Crashs. Once is Firebase Crashlytics and the other is Sentry. The second one I need in the company for different tools. With Firebase I have a better overview in general.
My problem now is, I see only the crashs in Firebase, but not in Sentry. If I create by my own a crash, then it appears in both. I don't understand what is happen.
What I know is that when an app is crashing the OS creates the report and the SDK in the app is checking this with the next start of the app.
For me it looks like that Firebase catch the crash reports and Sentry didn't get it. But then why I can see my self created crashs in both?
Do you have some experience with both frameworks in one project?
This came up before, including in the Sentry forum.
It's not a supported use case. Each error tracking SDK will attach to the signal handler to stack unwind during a crash and only one of them will succeed.
EDIT: We did some tests and it seems to work. At least on the device we tested, connected to WiFi, etc. That said, we heard reports that it didn't work in other cases.
So as I wrote on the comment below, it's undefined behavior and not recommended to be relied upon.
I am an iOS developer, and recently I try to find a tool to track crashes in our project.
After I integrated Crashlytics in my demo, I forced the demo to
crash for some times and check if the data in Crashlytics is correct.
But then I am confused by the data on the dashboard because the
percentage of 'CRASH-FREE SESSIONS' is always '<1%', while the total
number of crashes is 65.
Even I launch my demo and then kill it without crash it for several
time, the '<1%' doesn't change.
Is it a bug of Crashlytics?
I have sent 3 email to support#fabric.io, but did not get any reply. I don't know what is going on here.
That depends on your users. I had the same problem because I was testing it within my simulator and my iOS device, fabric is a service made by google. It's impossible to find a bug like that-- rest assured. Submit your app. Let your users use it, the actual result will come in a week
Hope this helps
I have enabled Flurry crash analytics in my app. My app crashes but it is not reported under the Errors section of Flurry Dashboard , but can be seen as exception logs under the "errors" option of Technical section.
How long will it take to report ?
Regarding Flurry, I dont know if the behavior is sent straightaway. In the case of flurry analytics, is not straightaway and you have to wait sometime. My questions now are : have you configured correctly the application with your flurry key? does the application ask you to send the report once it has happened and you reopen the app? Sometimes, and it happens in all the frameworks like crashlytics, if the app doesnt ask you to send the report, it can mean a hardware problem has happened (external to the app) and it wont be sent to the backend. Take a look in all the steps.
I want to access the crash reports of my app inside my app and i need to send the crash reports to a server. I searched in google and I couldn't find any API that helps my purpose but I found there are open source projects like QuincyKit, plcrashreporter for getting the crash reports of the application. If I use these APIs will apple reject my app ?
Thanks in Advance
There is no API from Apple to do that. So the only chance is to use a 3rd party framework which catches the crash when it happens and provides options to further process it afterwords.
There are multiple solutions available, one is QuincyKit. The second part of the answer of Including custom data into iOS crash dumps shows all known solutions and services that you can use.
Note: I am the developer of QuincyKit and also part of the HockeyApp team.
About QuincyKit:
I've used only Flurry, which has crash collection, and there seems to be no problem in using these libraries in your project for the app store.