I am getting stale requests for all my web-service calls when running on iOS simulator, however running on a device runs perfectly fine
I've compared the calls themselves using Charles, and they are getting made exactly the same
This is only happening in one particular computer, I've tried running on simulator on other PC's and they also run fine, using the exact same project settings, through an SVN checkout
I've tried deleting derived data in Xcode, doing a clean, reset content and settings, uninstalling/re-installing Xcode... even creating a new account on the PC and installing a fresh copy of Xcode there, but the problem persists..
Any ideas on what the problem could be?
Greatly appreciated
Really old, but it might help someone... I had manually changed the time on my computer, so the time that was sent in the request from the simulator being received by the server mismatched, causing these stale requests apparently... (re-checking set date and time automatically, fixed this issue)
Related
Any ideas? It was working an hour ago, now everything is dead and the status page says all is good
try disconnecting any devices you have connected.
I just tried everything SO suggested, reboots, wifi restart, iphone hotspot, nothing helped, so I unplugged my device and suddenly xcode connected and teams were fetched.
Just to say, I've had this issue a few times in the past week.
I'm using Xcode 6.4 with OS X Yosemite (v10.10.2), and from time to time, it just hangs on the "Fetching list of teams" message.
Most of the time, it works fine, but then it'll start to time-out, or throw an error like this:
The solution: reboot my MacBook. It fixes the issue every time.
It's odd. All other applications can happily access the internet, but for just this one part of Xcode, it seems unable to fetch the data it needs, and only a reboot sorts it out. I didn't have this issue before.
And it's hard to identify if this is an issue with Xcode 6.4 or OS X Yosemite, and Xcode demanded that I upgrade to the latest OS before it'd let me update to 6.4 (so I could actually debug an issue with iOS 8.2) so both updates happened on the same 1-2 days.
Bug ? Bug ? Did I say "bug" ? Course not. It's an undocumented feature.
(Sigh.)
Five hours later
I've just had the same issue again...
However, this time, I turned off WiFi on my MacBook, then turned Wifi back on again.
And the problem went away.
It (almost instantly) managed to load the list of (two) teams that I belong to.
Hope this helps.
I know that is late for answer but maybe my solution could help others.
IT ALWAYS WORKS FOR ME:
Step 1:
Go to Xcode --> preferences --> accounts
Step 2:
Select your team name and click in view details
Step 3:
Click in
Final step:
Go to Window --> Organizer and try to upload again your app :D
i resolved this by deleting my accounts and setting them up again. none of the solutions above worked.
This worked for me by disconnecting from my WiFi then reconnecting.
Quit xcode and simulator. Open organizer and click on Upload again. This worked for me.
I tried adding the account again and also reconnected the wifi but it did not work for me but quitting xcode did.
Actually I think it is an issue at Apples server.
I just got through once 30 minutes ago but had set the wrong build version and now I get the same error again. I think we have to wait.
i had same issue when i had changed my account's password.
first time, i just authorized it through new passoword. (it's not working)
and then.
remove all appstore accounts on xcode
add same account with new password.
it work.
Just keep retrying, I suspect the issue is on apple's server side and retry attempts will eventually get through.
You should get the list back within a second or two, so you can cancel the attempt and retry quickly rather than wait for the timeout.
Restarting wifi seems to help some people but not others.
Check your internet connection.
Upgrade XCode, 7.2 fixed this for me.
I noticed that I had some connection problems.
The ethernet cable was not fully plugged in.
On wifi, make sure you have a good signal.
I had same issue, and I resolved it.
I got hint from #jab11
I have external storage for TimeMachine. Around a week ago TimeMachine start to fail backup my disk.
I plugged out external storage not properly When it happens.
So, try like below.
Plug in your external storage if you have one.
Check your partition's health. (In my case, I erased partition which is causing fail to backup)
open Xcode Organiser, then upload your binary.
I hope this help.
For me, I removed all accounts in XCode -> Preference -> Accounts and ADD account again, then it's working well.
I have been at this for hours and am about to start flipping tables. This problem cropped up out of nowhere after working on this app successfully for about a month. No changes to build settings or build schemes or anything that I can think of.
If I build and run the app on an iPhone 4 I have no problems at all. If I build and run the app on an iPhone5S it will:
On the first attempt: Build successfully, appear to install the app on the device and launch it, but then fail with "error: failed to launch '.../MyApp.app' -- NotFound".
On the second attempt: Build, run, have a happy little debug session and everything is perfectly fine and dandy.
On the third attempt: Build successfully, begin to launch the app, and then will fail with "error: failed to launch '.../MyApp.app' -- Failed to get task for process -1". The phone will then become unresponsive, and the only way to bring it back is a hard reset.
Once or twice throughout the past few weeks I've had this problem happen, but after resetting everything was fine. Turning on or off building for arm64 doesn't seem to make a difference, and I can't think of anything else that would be different between the two devices.
Even a hint would be appreciated.
UPDATE: I changed the build scheme to "Wait for app to be launched manually", and by launching it myself after it's been built it seems to avoid the crashing. Obviously this doesn't fix whatever the underlying problem is, but at least I can function now.
Looks like this is a known bug, and it's resolved in Xcode 5.0.2.
I'm experiencing this very same issue but the workaround I've found is to disconnect and reconnect the phone before running the app. Using this workaround, I haven't experienced the error as frequently as otherwise, but it's still a rather tedious process...
This problem is known back to first Xcode 5 Previews. It helps to disconnect and connect the phone again. MY worst experience was Preview 4 with iPad. It till happens occasionally, but very rare compared to before.
I am developing an ios app that doesn't need an internet connection. I'm using phonegap and jquery-mobile. I'd like to develop offline, but XCode gets stuck with a status saying 'Attaching to iosproj' (iosproj is my project name). After that I cannot stop the stuck task, and have to force-quit XCode. With an internet connection however, everything works just fine. Grateful for any clues.
Edit: XCode seems to install the app fine without a network, but it gets stuck before/durimg receiving the deviceready event.
Update 1: The app runs fine on the simulator with or without the n/w. It is purely the XCode-iOS simulator interaction.
Update 2: When using phonegap (Apache cordova), there's an easy work-around to work offline. Once the project has been built and installed (with a n/w), all subsequent updates to html/js/css/img can be made directly to the www directory in the simulator's Library (under your app folder, in ~/Library/Application Support/iPhone Simulator/6.0/Applications).
The Simulator itself attempts to make an Internet connection to Apple as it launches. In particular, the itunesstored process attempts to connect to ax.init.itunes.apple.com and phobos.apple.com.
[That information comes from LittleSnitch. You would be well advised to install LittleSnitch so that you can be sure of exactly what connection is being attempted here. No one - certainly no developer - should be without it.]
If you find this troublesome (that is, if the connection failure is causing you to be unable to run your app in the Simulator at all) you should file a bug report with Apple. However, I've had no difficulty with this, so perhaps this an Xcode bug. I'd suggest first updating to Xcode 4.5.2 in case it is fixed there.
My app has been running fine on iPhone simulator. I have hit an issue (discussed here: Intermittent error accessing core data model / contacts database) and now all of a sudden, it won't build and run on iPhone simulator. I have the following error:
Couldn't register com.yourcompany.XXX with the bootstrap server. Error: unknown error code.
This generally means that another instance of this process was already running or is hung in the debugger.(lldb)
Any thoughts? I have tried totally closing and resetting iPS as well as deleting the app and reinstalling but to no avail.
Very frustrating!!!
Reset your iphone simulator and clean up your xcode project.
Type
apple-alt-shift-k
in xcode.
It happens quite a lot for me, especially during frequent restarts of the simulated app. I tracked it down to (at least sometimes) a race condition or deadlock when the simulated app is shutting down and a new one is starting up.
Quitting the simulator usually work
If that does not help, restart Xcode
Sometimes processes may linger and restarting the Mac is ususally the quickest way to recover (although clever use of the killall command can salvage the situation if it is really inconvenient to restart).
Quit the iPhone simulator and run it again.
Quit the simulator and xcode.Also delete the app from your simulator.... and if it does not work goto target setting and change something like name of app in bundle identifier . and it should work
You are using Core Data. So its possible you changed the dataModel and NSManagedObject class is changed. So it will crash until you delete application from simulator and run your project again..
My app runs fine on the simulator. However, when I run it on my iPhone, it gets as far as displaying the splash screen and then just stays there. It's an iPhone 3GS and the software version is 5.0.1. That's what happens when Debugger = None. When Debugger = GDB, I get an error message, 'Thread 1: Program received signal: "SIGABRT"', which I have learned can mean almost anything. I'm running Xcode 4.2.1.
I'm coming off a long hard night of battling with this error message, which appeared seemingly out of nowhere in a stable mature app. I tried to roll back with time machine, I deleted the Derived data for my project in Organizer a few times and did some of the other stuff recommended in this thread.
XCode 4 hangs at "Attaching to (app name)"
It got ugly. For a while, I couldn't even reboot my machine. Eventually, I was able to relaunch finder and suddenly the Simulator was working again. Two more pieces of information, I used to have to click allow in two dialog boxes when running on my phone but now it's only one (the one about code signing, I forget what the other one was about). Second, I find all the build architecture target stuff confusing but I set all my Base SDKs to be latest iOS. Lastly, I tried Product --> Clean and then Build but that didn't fix it. As you may have gathered, I'm getting my butt kicked. Any help would be much appreciated.
Dessie
Many times I have experienced Xcode going "crazy" with a physical device connected. At times I saw the behavior you describes; other the app simply refused to start;
In all of those cases, I could fixed it in either of two ways:
disconnect the iphone and connect it again;
reboot the device.
This is a very common problem that is easily fixable.
1) remove the app from the device
2) reboot the device
3) close Xcode and you must restart, logging out will not work