When adding a map anywhere in our project whether it be through a xib, storyboard or programmatically will crash the app. This crash occurs on a physical device but not in simulator. If the map's alpha is set to 0 the app doesn't crash. As soon as it is set to 1 it crashes with this cause:
Terminating app due to uncaught exception 'NSInvalidArgumentException',
reason: '-[VKMapView layer]: unrecognized selector sent to instance 0x109695d60'
Environment: xcode 14.1,
OS Ventura 13.0.1,
MacBook Pro 16in 2019
Project:
Min iOS 14.3
Device:
iPhone 13 Pro,
iOS v 16.1.2
The issue was caused by a third party integration. We downgraded the version of that package and now we no longer have a crash.
Related
I have a legacy app that uses Objective-C (with manual memory management). Using the new Xcode 11 (gold master) the app crashes after building and starting to run on the device/simulator. I noticed that this only happens to devices/simulators with iOS 12 or earlier. The crash happens after start up and I can get no exact pinpoint in the code when this happens.
There is no specific crash message only:
Message from debugger: Terminated due to signal 9
The problem was that the subprojects were getting build with different deployment targets. When the deployment target is the same on all subprojects as the main project this crash goes away.
The answer that got me on the right track is from this thread
Xcode 8, iOS 8 simulator with crash: "dyld: lazy symbol binding failed: Symbol not found: _objc_unsafeClaimAutoreleasedReturnValue"
Environment:
Xcode v9.1
Swift 4
I am trying to create an AVAssetDownloadURLSession to download the video asset from the background. However the app crash on iOS 9 due to the following reasons.
'NSGenericException', reason: 'Creating an AVAssetDownloadURLSession requires the com.apple.developer.media-asset-download entitlement'
Does anyone know how to fix the crash on iOS 9 (Simulator & Real device)? Many thanks.
You can't. The availability annotation is incorrect: that API requires a private entitlement on iOS 9 so you can't use it.
You can call it on iOS 10 or later.
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?
I have an app which I have been developing for ios 6.1 and I finally got it to work as I wanted to.
Then just to test how it works on the older iPhones, I set the deployment target to 5.1 and when I ran it, the ui started looking messed up.
Would anyone know why this happens? And should I keep the deployment target to 6.1? And if so, how do I make sure that the app looks ok on the older versions of the iPhones?
ps - here is the crash when I check the auto layout option
*** Terminating app due to uncaught exception 'NSInvalidUnarchiveOperationException', reason: 'Could not instantiate class named NSLayoutConstraint'
*** First throw call stack:
Autolayouts were introduced in iOS6.0
If you want your app to run on iOS5.x or 4.x you must disable or not use autolayouts, or version gate the use of autolayouts based on which iOS the device is running (which, is a pain).
The Deployment Target is the oldest iOS version you want your app to run on. if its iOS5.0, then it'll run on all devices having iOS5.0 or later
Here's a better answer
I m trying to compile an app developped with ios sdk 4.3 with new ios 5.0 sdk
however, I get a strange crash at app loading with SIGABRT signal
the call stack is pretty minimalistic :
13 UIApplicationMain
14 main
after checking console, I get the following error:
Could not load NIB in bundle: 'NSBundle (loaded)' with name 'MainWindow_iPad''
I checked my resource folder , and the file is there, and the problem only occurs with the new xcode/ios sdk 5.0 , on a different machine with xcode 4 / ios 4.3 / ipad 4.3 with the same project, the project is not present
Does moving to ios 5 requires somes tweaks in resources management?
the beta version of xcode/ios 5 was bugged , with final version of ios 5 all is ok.