iOS 9.1 NSMutableArray Crash - ios

We have a company salesapp that runs on a lot iPads. One device keeps crashing every now and then. The crashlog shows:
Model: iPad5,4
iOS: 9.1
Exeption:
[__NSArrayM removeObjectsInArray:]: unrecognized selector sent to
instance 0x157d022a0
First of we don't use this method in our code. Testing with the 9.1 iOS Simulator shows that the method gets called by the os during touch events. It is also not an immutable object btw.
This didn't happen in previous versions and the codebase didn't change since the last update was content only.
However the only new component is XCode 8. The previous version was made with XCode 7.
Granted the user needs to update his iPad.(If IT will allow)
But that doesn't explain what is happening here.
No crashes before XCode 8 - wich sound troubling if XCode is the culprit.
Our logs shows that all other iPads run 8.3, 9.3.5 or 10.x.
Are there any issues known with iOS 9.1 that could explain this?

Related

iOS 14.0.1 crash issue

Since last release on the AppStore, that was a major update, with many new sections and two new targets added to project, my app started crashing on iOS 14.0.1 only on various devices.
No issues with all other OS.
Many users report the app is crashing at launch, showing a black screen and then crashing.
In Xcode organizer I can see all empty crash logs, with no stack trace.
I have no chance to replicate the issue since I have no device with iOS 14.0.1 and have no idea what could have introduced the issue and, most of all, what kind of issue can affect iOS 14.0.1 only.
Any idea or suggestion will be appreciated.

App crashing immediately on start up after upgrading to iOS12

My application is working fine on iOS 11.0. But when I am run on iOS 12.0 they crashing immediately on startup. My application is on Objective-C and MRC.
Running fine in simulator but crashes in the device.
No main or didFinishLaunchingWithOptions is called yet.
Tried re-installing the application. Tried "Eare All Content and Settings" but it does not work.
Enabled zombie objects but even that did not help(no logs recorded).
I also try to symbolicated the crash report but not find any solution from crash report.
I have attached my crash report here.
Crash Report
I found the solution. The app is crashing just because of using an Old version of the Crittercism SDK. Upgrade to the latest version to support iOS 12.0.

avoiding selector not found in iOS

I downloaded a calendar tutorial and ran it with deployment target as iOS 6.1 and ran it in the simulator, everything went fine. I loaded it onto a iOS 6.1 device and it crashed with "selector not found"
It uses 'startOfDayForDate'
return [[NSCalendar currentCalendar] startOfDayForDate:self.start];
This crashes on the iOS 6.1 test device yet it works in the simulator even though I have a deployment target of iOS 6.1.
I used instancesRespondToSelector and found it doesn't respond.
I listed out the methods and found about 30 methods fewer when I run the same program on the device when compared to the simulator.
Note that the other settings are the same.
Q. How do you set the simulator to simulate a certain OS?
Is there some hidden setting I don't see that would cause the simulator to load methods from a different version of iOS?
Looking at the documentation here it looks like this method is only supported in iOS 8.0 and later which is why this crashes on your iOS 6.1 device.
You are probably running a simulator for a version of iOS later than 8.0.
If you're running xCode 6.0 or later the earliest simulator you can download is iOS 7. This is better described here

How can I use and debug an iOS version a simulator doesn't exist for?

I'm in the midst of squashing bugs for my App in development, and I've stumbled across a problem when it comes to addressing a crash occurring on iOS 8.0.2
The problem is that I can't actually test (On the simulator) for iOS 8.0.2 as the earliest version of iOS 8 I can use is 8.1
I am not supporting iOS 7, but did go back and try to see if I could catch the bug there as described by the tester who reported the crash. It did not occur no matter what I did, so I assume it must occur when running iOS 8 only.
I'm not sure how to address this problem. I would like to submit my App for review, but if I cannot eliminate this crash I will be rejected. Yet I can't test for it either. I've been waiting a day+ now for any crash report to come back from Test-Flight, but none have shown yet. It could take around three days for that to happen.
Can anyone assist me in finding another way or workaround to be able to test for this crash?
You could download and install Xcode 6 (Xcode 6.1 might also have the iOS 8.0 simulator) as that'll have the iOS 8 SDK and simulators (you'll have to be signed in to your Apple developer account to access those links otherwise pick from the list here).
The problem you'll then have with that though, is that you'll be compiling your code against a different SDK. But its worth a try!
Its also difficult to get specific 8.0.X versions of the simulators as they only really have the minor version release (8.X) available as opposed to the bug fix releases.
Obviously the only guaranteed way to reproduce the issue is on a 8.0.2 device.

App crashes in iOS 5 in iPad and works fine in iOS 6 and iOS 7

I have Crittercism in my app. I created a copy of this app to ugrade to next version. But it crashes before it enters applicationDidFinishLaunching. But the previous version of app is working fine. In case I remove the Crittercism in the current then it works fine. Crittercism version is libCrittercism_v4_1_2.a. I have no clue about the error. Please help.
Screenshot of error:
It works fine in iOS 6 and 7. I have enabled zombie and added All Exceptions breakpoint but still no log at all. It just shows the splash screen and crashes.
I'd recommend upgrading the Crittercism library if you can to a newer version.
If you look at the release notes here:
https://gitlab.recatch.tv/modules-ios/crittercism-ios-sdk/blame/1a167a6c9bd72fe002175680fbeb88d0b1cdafda/release_notes.txt
You can see that there were some changes regarding deployment target in the version you are using. Try to upgrade to a newer version (latest if you can) and see if this corrects your issue.
Good Luck!

Resources