I am getting a crash on firebase on SKStoreProductViewController, while during testing this crash is not being produced.
Is there anyway to resolve this issue? Thanks.
Fatal Exception: NSInvalidArgumentException
-[SKStoreProductViewController sceneDisconnected:]: unrecognized selector sent to instance
How to resolve the reported issue?
This crash happens in the public release of iOS/iPadOS 15.7, and seed releases of iOS/iPadOS 16 prior to seed 4 [1]. It does not occur in the public release of iOS 16.
The crash primarily happens when the app is in the background and is about to be terminated by the operating system. As a result, these crashes are not expected to be visible to the majority of end users. (One exception is on iPad with an app that supports multiple scenes, and a user manually terminates a scene.)
Your analytics will show an increased in crash rate, however your customers should not be affected by this issue.
You can refer to https://developer.apple.com/forums/thread/714464
Related
I've used Xcode's zombie debugger and managed to find this flag upon launch:
This crashed the app, and re-recording from Instruments caused the same result. Relaunching the app from the device made the app launch without a crash and subsequent launches from Instruments resulted in normal operation without flags or crashes.
Can anyone make sense of this or advise? I'm getting a number of "heap corruption" crashes in production. The reports are limited to a handful of users, but I'm afraid that number is growing.
It looks like the Parse SDK's latest release notes (1.15.1) addresses this:
-Adds polygonal queries
-Fixes memory leaks related with PFCommandCache
But my crash reports are coming from builds with this SDK version.
The Parse team has responded saying that a fix for this is coming to a new SDK release soon. :)
I just discovered it is possible to force quit a frozen application on iOS.
According to the Technical Note TN2151 I should get a crash log on my device with code 0xdeadfa11 but I have no such crashlog.
The exception code 0xdeadfa11 indicated that an application has been force quit by the user. Force quits occur when the user first holds down the On/Off button until "slide to power off" appears, then holds down the Home button. It's reasonable to assume that the user has done this because the application has become unresponsive, but it's not guaranteed - force quit will work on any application.
Note: Terminating a suspended app by removing it from the multitasking tray does not generate a crash report. Once an app has suspended, it is eligible for termination by iOS at any time, so no crash report will be generated.
Is it an apple bug or are there some additional steps I am missing ?
EDIT
If I check the device console after the force quit I see this log :
ReportCrash[2074] : Stackshot code 0xdeadfa11 not tasked,
ignoring
Seems that for whatever reason iOS decides not to generate deadfall crash report.
I tried to generate force quit on three devices:
1)iPad 3 (iOS 8)
2)iPad Air (iOS 9.2)
3)iPhone 5 (iOS 9.2.1)
When I tried to generate crash on all three devices via xcode while debugging, no crash log was generate instead I got the following error message:
Message from debugger: Terminated due to signal 9
which I think similar to your message:
Service exited due to signal: Killed: 9
and when I tried to generate crash without debugging and seeing log via device logs then I found:
1)For iPad 3 (iOS 8): Crash log was generated, screenshot attached.
2)For iPad Air (iOS 9.2): Crash log was not generated.
3)For iPhone 5 (iOS 9.2.1): Crash log was not generated.
As per my understanding, when you try to generate force quit via xcode while debugging, it does not get generated and for case try to generate crash while without debugging directly in your device then it might be os (iOS 9) specific reason.
P.S: And Service exited due to signal: Killed: 9 is generated due to memory issues, and high CPU consumption tasks.
Hope this might help you further.
The Apple note says that Terminating a suspended app by removing it from the multitasking tray does NOT generate a crash report. I don't think you will have a log.
I just have device UDID & client reported that the app is crashing
on his device & he is not able to start application.
The client device iOS version is 7.1.2
Also i am not having any crash report.(Asked for Crash Report)
Now referring
(iAd works on simulator but crash on device(ipad)):
I am assuming the reason behind this might be the library,
So will making iAD.framwork optional & handling codes related to this do the trick?
**Update:
Unfortunately the cause of the crash was -[__NSCFString containsString:]: unrecognized selector sent which was iOS version fault & not device fault. I got it resolved. sorry to iAd for blaming or trying to blame. Long live iAd. Thanks**
First of all - you need crash details. Without it, nobody help you.
Integrate any crash reporter SDK: Crashlytics or anything like this.
Our current beta version of the app crashes sometimes, this happens to myself and my colleagues. The beta's are send with Apple's TestFlight app and I build it to my own phone. Phones are iPhone6 running latest iOS8.
When I hook each of them on my mac and load the crashlogs I couldn't find any crashlogs on the time the crash has occurred (also none on other times). I see recent crashlogs of other apps but none of the crashes is our app. Also there isn't an unknown crash at that time indicating a memory issue.
The app crashes after using it a couple of minutes to a hour and seems not to crash each time. So not on startup but somewhere in the middle and not always in the middle. App is using the users-location actively.
Changes in this beta version:
- More MKOverlays on the map
- First time MKMapCamera to position the users location on the map
- Crashes occur while using the map
Any ideas?
Best,
Sjoerd
edit:
After running the app on my phone in xcode for some time I finally found some crashlogs. Perhaps it's the kind of crash?:
Exception Type: EXC_RESOURCE
Exception Subtype: WAKEUPS
Exception Message: (Limit 150/sec) Observed 300/sec over 300 secs
Triggered by Thread: 19
Seems that I had memory crashes at another time. Weird.
I ran the app on my own phone (not simulator) in debug and found out that is was a memory crash. Now the memory crashlog was there with the right time now
Not sure what happened before and why the time wasn't right.
Also memory crashlogs appear as unknown. See the first one:
We have application released on iOS app store. And as per the guidelines the crashlytics SDK is integrated and also calling [Crashlytics startWithAPIKey:#"API_KEY"] as well. What could be the different reasons that the crashes are not getting updated on the Crashlytics Dashboard.
How we can verify or debug, the app which having the Crashlytics sdk integrated and initialised appropriately or not?
Before you launched, did you verify that crashes were getting reported? If not, then you may have a conflicting Exception/Signal Handler preventing Crashlytics from doing it's job.
Here's how you can throw a signal:
-(void) throwSignal {
int i = 12345;
NSLog(#"%#", i);
}
To throw an uncaught exception simply do the following:
[NSException raise:#"test version 3.3.2 crashy" format:#"awesomeness"];
If you were able to get crash reports before launch, then there may be something happening with Crashlytics ingest of the reports and I would contact their support team.
We are getting now crash reports for app store build. We had a provided .dSym file to the crashlytics team, they have uploaded the same in their db.