I'm using App center to show the crash reports occurring in testing / production crashes. I was able to view the crash report graph before, but from the past 20 days I am not able to view the crash reports graph. Below is the image which I have always seen. I'm not understanding what happened. Has any one faced this issue?
From this https://github.com/microsoft/appcenter/issues/541 got some information, that need to change filter option to 28days but i don't find where should change this filter option.
Related
I have a published app that has a need to keep the display on for an extended period of time. I use UIApplication.isIdleTimerDisabled to control it, setting it true when I need to keep the display on, and setting it false when it's no longer needed.
Since the app is distributed through the Apple App Store, I get reports when crashes occur. I sometimes get a report that points to a crash at a line where I call UIApplication.shared.isIdleTimerDisabled = false, i.e., where I'm restoring the normal state of affairs after the screen has been on for a while. Below is a screen shot of the stack trace.
I'm unable to reproduce the problem on my own. There are thousands of users who have downloaded and tried the program, and I only get one or two crash reports a week, so the problem must arise from some infrequently-occuring set of conditions. The crash reports come from a variety of iPhones and iPads running iOS 13 and 14.
Any ideas?
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 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
A user has reported that my app suddenly won't launch on their device. They sent me a video, and they launch the app, the launch image screen shows for a split second, but then crashes back to the iOS home screen.
The user tried deleting and reinstalling the app with no benefit.
I use Crashlytics, and am not getting any reports of crashes from them (or any other user- although I've seen them in prior versions so I know it's working correctly). I'm also not seeing any crashes in iTunes connect.
I asked the user to send me any crash reports in the Settings Diagnostics section and they said there are none listed for my app.
I have confirmed that their iOS version is supported by my app. (iOS 8.4).
I'm not sure where to go next, and would appreciate any pointers. Sorry for the vague question but I have posted everything that I know about the situation.
Just wanted to provide some closure on this. The user ended up wiping and restoring their device, and it solved the problem. It seems extreme to me but it was their own suggestion and didn't take them long to do. So I'm not sure what caused this but that's one (albeit brute force) way to fix it.
Currently, I am using Crittercism for crash reporting and making sure that I add dSYMs to get symbolicated crash reports.
But it is not helping with some of my crashes which are segmentation faults (SIGSEGV and SIGBUS). They occur randomly and I haven't been able to reproduce them on device and on simulator. I have tried to find a pattern by trying my app on different ios devices with different network connections (3G, Wifi, Edge) but with no success.
What can be my next step?
Not much to go on, but here are a few places to look:
If you have multiple threads, check to make sure they are behaving properly. Make sure you synchronize properly if multiple threads could be accessing the same objects.
Check your NSNotifications - could one be posted when you are not expecting it?
I have found that the hardest bugs to find are those that are caused by asynchronous events - either in other threads or due to external events that you might be monitoring.
Not being able to reproduce the bug in your development environment will make it very hard to find.