I just updated to xcode 7.0 and now my app is hanging at the splash screen.
I'm using a Google Maps Pod.
At first a clean & build caused a build fail stating that the Enable bitcode needed to be switched off.
I did that. My app now builds, however when I install it to the simulator or iPad it hangs on the splash screen.
There are no issue flags being displayed and the app appears to just hang forever until forced closed.
Everything was working fine until this xcode 7.0 update. Any ideas?
A previous post xcode 7 issues
stated that there are some problems with content in the view controller when compiled with 7.0. The solution was to completely reassemble the views piece by piece until it starts working. This is not a practical response because of time constraints and financial aspects at work. I uninstalled xcode 7.0 and then went to the Apple developer archives and reinstalled xcode 6.4.
The app now runs correctly. Hopefully this will get sorted out by 7.1.
Related
After upgrading to Xcode 7.0.1, I can run my old apps without problems (after updating Swift syntax), but any new apps I try to build will invariably freeze the launch screen on any attempts to build and run on any simulator or device.
I can make any changes to the storyboard I want, but as soon as I create any code linkages to a button, textfield, etc, I get the nothing but the launch screen when I build & run.
There are no compiler errors, no warnings, nothing to even give me a hint of what the heck is going on. I've cleared derived data, clean & build, reset content & settings, & removed/reinstalled Xcode without any luck.
Does anyone have any idea what's going on here, or can someone tell me where I can start digging to find the issue? I'd post a screen shot if there were something to post, but I've got nothing.
I'm running Yosemite 10.10.5 with Xcode 7.0.1 with Swift
Everything was working perfectly when debugging my keyboard on Xcode 6.2 running iOS 8.2. After updating to Xcode 6.3 and iOS 8.3, I seem to be having difficulty getting the debugger to work. Has anyone experience similar problems? I've tried cleaning my build, uninstalling/installing my app, but nothing seems to work.
What happens is I build and run, and when I switch between keyboards to get to mine it just never pops up, instead it jumps to the default one. Upon ending the task, and doing it again it works perfectly, just not when I'm attempting to debug.
Some of the information from this answer is a bit outdated, but it was useful to me. I am still convinced that extension debugging on devices is 90% broken with XCode 6.3.2 and iOS 8.3. I've been debugging successfully from the simulator, though, and occasionally I'll get the device process to attach correctly from within XCode, but more often than not it just quits on me.
Originally, I thought this was an issue of the code I was writing, but I've just downloaded four or five WatchKit projects even one from Apple. All of them, fail to load.
I've uninstalled Xcode, reinstalled it and still nothing. Any one else experiencing the same issue? Workarounds? Solutions?
You can see in the screenshot above what the loading screen looks like.
I am already bloody sick of official Xcode 6.2 & WatchKit Simulator. It is so super flaky. Here's another fun fact, if there is some constraint in your storyboard that the watchKit doesn't like then it will also keep looping in an infinite loop without letting anyone know why its doing that. What you need to do is
Drag and drop & add another WKInterfaceController to your storyboard
Make that one your main by dragging the arrow on it
Delete the old watchKit app controller
Now start adding elements one by one and keep testing till it doesn't work any more on the simulator (infinite spin of death)
Try clean and build and even after that it keep the spin ball of death then the last change you made to the storyboard is what it didn't like.
I had to spend hours debugging this crap.
UPDATE:
If the above steps don't work for you then try this
launch Xcode
compile and build & launch iPhone simulator
Now don't shutdown the simulator instead do Xcode --> Product --> Stop
This will keep the simulator running but swill top the iphone app running on it
Do Build --> Clean
Do build again
Now launch watchkit simulator
If you need to stop and start always do Xcode --> Product --> Stop
These steps have always worked for me while making watchkit apps
I experienced this a lot with Xcode 6.2 beta 1. I only got this a few times with beta 2 and 3. Here is what I would do to get it to work.
Reset the simulator via menu->IOS Simulator->Reset Content and Settings…
Quit the simulator
Clean the Xcode project
Restart Xcode
Build and run the iOS App (not the Watch App)
Stop the iOS App
Build and run the Watch App
This would generally fix the app just spinning for me. With beta 1 sometimes I would have to do this two or three times to get it up and running. Once I had it running, it would usually not do it again for a while. With beta 2 and 3 I only saw this a few times.
I always get this issue with Xcode 6.3. I've spent a lot of time on resetting caches in simulator, cleaning/rebuilding projects and so on.
But only one thing always helps me. I just add new blank interface controller on my storyboard and create sequence to it from my main controller.
And when I get this infinite loading of my app, I just swipe to my blank controller and than back to my main controller. After that everything works fine.
In my case nothing here proposed helped. I had to select the module name in addition to the Custom Class name:
This was as a result after renaming the watch kit app. Maybe this is helpful for someone else, since the "spinning wheel of death" itself doesn't give much insight :-/ .
I'm having trouble running my app in a simulator or connected device after upgrading to xcode 6.1.
Whenever I run my app, am getting a black screen. I tried all possible solutions found online like cleaning and resetting, changing command line tool ,reinstalling ,rebooting etc...
I tried creating a new simple test project and it worked. But my older project is not launching. I even tried making my rootviewcontroller as a simple view with just background color, still its not launching.
Is this an SDK issue?
Any help will be great,
Thanks
I have been having this weird problem with Xcode 4.3.2, of course after the recent update.
After successfully building and running on the simulator several times, xcode seems to not be able to connect to the simulator and can't even stop the project; it's like the simulator does not exist. I have tried:
Stopping the project – doesn't work.
Quitting the simulator – doesn't work, xcode still shows it's running on the simulator even when I quit the simulator.
Cleaning the project – doesn't work.
I have to force quit xcode to get it communicate with the simulator. Nothing else works. It gets quite frustrating to do it every half an hour. This only started with 4.3.2.
I always stop before building and running, so it is not an issue of simulator/xcode getting thrashed by me.
Any suggestions?
I have found by chance, it is not a solution by any means -
When xcode hangs, saying it is running the app, but nothing is on simulator, opening the simulator from the dock by clicking on the dock icon (not using command+tab) seems to work.
It is very weird,but it works; atelast till xcode fixes it.
I had the same damn issue on XCode 4.5.1, but I resolved it just now.
When the program is running, it gets compiled but doesn't show anything on the simulator. just click on iOS Simulator icon in dock in order to bring it to front. Click iOS Simulator on top left -> Reset content and settings -> then force quit the iOS Simulator and run the program again. !!
Besides a restart, there is one other way I've managed to get around this:
Let's say your app hangs, go to the targets selector in the top of the Xcode window and change your sim target to a new SDK (or if you don't have another SDK, change it to a universal app and run on the opposite device simulator).
Then, when your app loads on the new device/OS completely, quit the sim, change your targets back, et voilà!
Uninstall application from Simulator and again run. Then it will works fine :)
This has frustrated me for -years- now but stumbled across what appears to get things going again for me:
Hide the simulator (iOS Simulator -> Hide iOS Simulator) or Cmd-H, then reopen the simulator.
The problem seems to happen when something CPU intensive is happening in the background (like a Time Machine backup) on my old 2 core MacBook.
Xcode 4.6.3 update (June 13, 2013) resolves the following issue:
Hang when debugging in iOS Simulator on OS X 10.8.4. 13722320
https://developer.apple.com/library/mac/#releasenotes/DeveloperTools/RN-Xcode/
You can try to update your Xcode to see if that works for you..