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.
Related
I have an iPad app, XCode 6, iOS 7, Storyboards and ARC. If I change the target to 7.x, the app works fine on the simulator running 7.0.
However, if I change the simulator to 8.0, the app doesn't recognize the CoreData store created when running under 7.x (the store is still there, just not found when running on the 8.0 simulator.) Also, none of the objects (UIButtons, UITextboxes, etc) show up either!
I don't have iOS 8 installed on my iPad (afraid stuff like this will affect my users), but the question is: just because something doesn't run on the simulator v8.0, does that mean that setting the lowest target to iOS 7, it won't run on the device if it is running iOS 8?
The iOS 7 simulator is on a separate (virtual) machine from the iOS 8 simulator. So any data you created one of these machines, will not be found on the other.
I have a piece of software I wrote using xcode 5. Since I upgraded to xcode 6, the app looks strange when I run it on a physical device using the emulator. Not entirely sure what is going on or how I could fix it. It's not respecting the full size of the screen.
I am testing on an iPhone 5s (NOT simulator -- the app looks fine in the iPhone 5s simulator). I am connecting my phone to my comp and running it via xCode.
I am having the same issue with another project I built using xcode 5 and trying to run again in xcode 6...
thoughts anyone?!
Here is a screenshot of what is going on:
I have an iPhone with iOS 8 installed on it, but when I connect it to Xcode 5.1, it doesn't recognize it.
As with the other answers, it seemed fairly random whether or not my iOS 8 device was being picked up by Xcode 5.1. It appears that it works if you have the iOS 8 device plugged in before you start Xcode 5.1. When you do that, you will get a screen indicating the symbols are being processed:
After this completes, the device is selectable. I am pretty sure this needs to be performed with each new beta. That might explain why it appears to suddenly stop working.
If this isn't working for you, make sure you have the latest Xcode 6 Beta to match the iOS 8 Beta version, and connect the device while Xcode 6 is running. The same "Processing Symbol" files process will occur and then Xcode 5.1 seems to work.
the only decent way to make it work is to create a symbolic link to a folder that contains binary for iOS8. You can make fool Xcode 5.1 saying "yes, iOS 8 is ok." via a symlink:
In my case I have Xcode 5.1 on Mavericks HD, and Xcode 6.0 beta 4 on Yosemite HD.
I did:
sudo ln -s /Applications/Xcode6-Beta4.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/8.0\ (12A4331d) /Volumes/MAVERICKS/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/DeviceSupport/8.0\ (12A4331d)
and Xcode 5.1 did work with my iOS8 iphone.
(note the space before /Volumes/MAVER... )
PS: for every beta, I have to patch again... :(
You need to download the Xcode 6 Beta. It's available in the iOS Developer Center, where you downloaded the iOS 8 Beta.
I have connected my iPhone with iOS 8 installed to Xcode 5.1.First time it doesn't recognize.but when i unplugged device and connect again , Device Recognized.
I dont know the reason Anyway i am sure that you can also connect your IOS8 installed device to Xcode5.1 ....
I've been using Xcode 5 to build on an iOS 8 device just fine. Now all of a sudden, it won't let me anymore.
first use xcode6 build on your iPhone5s.
second open xcode 5 ,unpluge device and connect again.
then device recognized.
Open xcode 6 and wait until device is recognised. When done, close xcode 6 and open xcode 5.1 and your device is going to be automatically recognised.
That way you can run your application on a device with iOS 8 with the old xcode.
I am using XCode 5, with an iPhone 5s as the dev device. Every other time I run the app I get a pop that says "Could not launch [app name] \n busy". My iPhone 5s then appears to crash and the only way it will respond is if I hold the home and lock button until it resets.
The application is a single view application, the only thing I have done is added the Parse.framework from here and used
[Parse setApplicationID:appID clientKey:clientKey];
[PFAnalytics trackAppOpenedWithLaunchOptions:launchOptions];
In applicationDidFinishLaunchingWithOptions, along with some UI that isn't hooked up to anything.
I'm not sure if this has to do with Parse or possibly the App settings.
So to be clear, the behavior is:
Fresh reset > Build and Run application on iPhone 5s > application runs fine > Build and Run application on iPhone 5s > application appears to launch but screen remains black and iPhone is no longer responsive except the screen will turn off when the lock button is pressed (but not back on) > Build and Run application on iPhone 5s > XCode says "could not launch app - busy" > hard reset iPhone
When I run this on the 64-bit simulator it works fine.
Edit 1:
I have tested with multiple applications now that we know work on multiple other devices (iPhone 5, iPhone 4, iPhone 4s) and the simulators. I don't have another iPhone 5s so it is hard to compare exactly but everything crashes my 5s..
My device was completely stuck with black screen. "To fix you have to hard reboot, holding the power and home button until the phone reboots - doesn't lose any of the data you have on your phone (a concern the first time I did it)." as stated here:
http://blog.paulhadfield.net/2014/01/iphone-hangs-when-running-from-xcode.html
For iPhone7 there is a different approach:
Press and hold down the power button located on the right side of
the iPhone 7.
While holding down the power button, press and hold
down the Volume Down button on the left side of the iPhone 7.
http://www.hongkiat.com/blog/force-reset-iphone7-7plus/
You were using your phone when you ran the app. Make sure you don't use your phone after you press build and run, otherwise it will be "busy"
Which Xcode version do you use? Same issue with Xcode 5.0.1 + iPhone 5S (iOS 7.0.4). It crashed my iPhone 5S even by the simple application created by Xcode's default project template.
It seems this issue has been fixed in Xcode 5.0.2. Xcode 5.0.2 works fine for me by now.
I've got the same problem for several times. It seems that this problem always happens when iCloud or other background App is running & the App I was debug is already in running mode.
My suggestion is: Avoid any background App running when debug and Make sure the App debugging is fully killed before restart a debug.
It is obvious a bug in iOS 7 + Xcode 5.
I had the same issue and upgrading to Xcode 5.0.2 resolved it.
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.