I've run into a problem with Xcode crashing when trying to run my SwiftUI app on my iPhone XS Max. The crash only occurred after upgrading to the latest Xcode 11 Beta 7. Also, the app still runs without an issue in the canvas and with the iPhone Simulator. Below is the error code that I get, the app doesn't go past the launch screen when running on my device. My device is running iOS 13.1
"Terminating app due to uncaught exception 'CALayerInvalidGeometry', reason: 'CALayer position contains NaN: [nan inf]. Layer: >; sublayers = (); opaque = YES; allowsGroupOpacity = YES; anchorPoint = CGPoint (0 0)>'"
Where should I look?
Sorry, noticed someone posted that it's not possible to run apps on devices with iOS 13.1 currently using the Beta 7 build.
Related
Screen shot above shows annotationView callouts in my app appearing transparent in iOS 13. The app is currently in the store, and has been for many years. The last code change was March of 2018, and testing in simulator and on device (using direct usb connection) do not show this problem as seen below:
I have added the proper device support files to version of Xcode used to submit the app in March 2018 so I could build/run the app on a device running ios13 - annotationView callouts work as expected! But using same device and the version of the app from the app store, annotationView callouts show transparent.
Also tested the latest app store version of the app on devices running iOS 9 though iOS 12 and as expected, annotationView callouts work as they should.
I have deleted and reinstalled app via the app store on an iOS 13 device - problem persists.
I'm looking for ideas on how to track down this phenomena. I'm a bit stumped.
Seems to be that in the current iPad OS (13.4) this error is fixed by apple.
I have an app that has been in the App Store for almost two years. Published originally for iOS 7, it was updated and runs perfectly under iOS 8, and I just downloaded XCode 7 to make sure I was ready when iOS 9 hits the streets.
I am getting a EXC_BAD_ACCESS error when I run the app in the simulator, but not when I run it on my test device running iOS 9.
I am using NSURLSessionDownloadTask to pull a file down from my server:
NSURLSessionDownloadTask *getTheNoticeFromTheServer = [session downloadTaskWithRequest:[NSURLRequest requestWithURL:[NSURL URLWithString:completeFilePath]]];
[getTheNoticeFromTheServer resume];
The error hits after I call resume. Again, this is only when run on the simulator in XCode 7. Works like a champ on the iOS9 device and on the XCode 6 simulator as well. Anyone else seen anything like this while using NSURLSession with XCode 7?
Thanks!
Scott
Well I thought XCode 7 Beta 3 fixed this, but it just changed the behavior. Now the app will run fine on the device by itself, or in the simulator. But the crash now happens when I run it on the device from within xcode...you know, like you would normally do during development and debugging. Awesome.
When I run my targeted iphone app on an ipad with iOS7, it renders in iphone mode and this is exactly what I want. In fact, when I print the size of the window bounds, it correctly prints out 320 x 480. However, when I run the same app on an ipad with iOS8, the app goes into full screen mode as the window bounds are now 1024 x 768.
Do you know how I can restrict the iOS8 ipad to render the app as an iphone only app and not a full screen ipad app?
NOTE: I did my testing on the same iPad device before and after the upgrade from iOS7 to iOS8. I'm also consistently able to repro this with the ipad simulators
This might be caused from a known bug in XCODE-6 that is fixed in XCODE-6.1 beta. If you are using the storyboard launch file, the iOS 8 iPad will not be scaled from iPhone mode, but will be treated as an actual iPad. To fix the bug, use static launch images by hitting use asset catalog on the following screen in the target options, general tab:
After this, make sure to have your static launch images uploaded to the .xcassets, or update to xcode 6.1 beta to fix the issue.
What are the differences in iOS 5.1 & 7.0 in the aspect App behavior when it is in background?
My problem is when switching to other app and switching back (let's say after 5 min / 30 mins) to my app, I am getting server error "connection lost". That was not happening with iOS 5.1, but happening in iOS 7.
I think there is something with the iPad running in the background in different way on iOS 7...
Any ideas?
Just want to make sure if this is just me. My app when running on the iOS6 simulator or a iOS6 device is serving iAds just fine. The same app running on the iOS7 Simulator or devices never serves ads.
** Failed to receive ad - The operation couldn’t be completed. Unknown error
If it makes you feel better, I'm getting this too. Works in iOS 6 simulator, but I get the error in the iOS 7 simulator and my iOS 7 device. I'm hoping this is just a problem with debug mode and not a problem when the app is deployed.
As of today Apple seems to have fixed it.