I have an Xcode 4.2 project with ios5 targeting 4.3 and am now suddenly getting "wait_fences: failed to receive reply: 10004003" error.
It occurs on the 4.3 Simulator (don't have a 4.3 device). It does NOT occur on 5.0 simulator or device.
App runs as before and when the keyboard appears, all is good. When I tap the keyboard. I get the error. Description is displayed once in the console. Subsequent runs still crash app but error is not written to console! (So I'm assuming subsequent crashes are the same) It's suddenly started occurring and I can't see anywhere the in the code, changes could affect it.
Has anyone else experienced this same issue and or managed to resolve it?
NB: I have already read the other posts regarding this error.
Have now confirmed that it is not the code so my iOS Simulator must have been corrupted some how.
Related
I am currently testing the Apple News JSON format using XCode / News Preview / Simulator and randomly running into a new error that was not occurring prior to today.
I am attempting to load the article.json file into the News Preview app (it's been working up until today). The article.json file gets successfully loaded with no errors in the console but the Simulator is claiming that the channel is not available for me. Here is what the error message on the Simulator reads:
Channel Unavailable
This channel isn't currently available in your region.
The News Preview and Simulator were working just fine until today. I have tried re-installing XCode and News Preview (and Simulator because I re-installed XCode) but the problem persists. Other colleagues of mine are now experiencing the same problem.
I tried also clearing all the content in the Simulator and tried wiping the device clean and also tried going to the "Debug" menu in Simulator and setting the Location specifically there, as well, without any success.
Is there a way to fix this or is there a way to know if there was a recent developer push to the Simulator code base?
Just to add a bit more detail, I am attempting to load the official Apple News article preview files, not my own article.json files (I tried loading my own json files, as well).
Any help is appreciated.
Hey I also just had this issue and have been troubleshooting since yesterday. Not sure what is causing it, but it only happens for my on devices simulators from iPhone 7 and newer.
Try running the preview on iPhone 6 or an older-gen iPad, etc... that's working for me.
The solution on only one of my machines was to enter the Publisher ID into the News Preview application, which is the first thing that is asked when launching the News Preview app. After entering the Publisher ID, everything seemed to return to normal - for all of my colleagues and I.
See my comment above about my new macbook and the new problem it is having.
Right in the middle of working in Xcode, when adding a simulator to it, it crashed. When I reopen Xcode, it crashes again but gives opportunity to send error report to apple. In the window I can read:
ASSERTION FAILURE in /Library/Caches/com.apple.xbs/Sources/DVTiOSFrameworks/DVTiOSFrameworks-11515/IDEiOSSupportCore/DVTiPhoneSimulator.m:615
Details: Unexpectedly found two active proxied devices for companion dvtdevice-iphonesimulator:E32D007F-6826-4EE3-BD9A-DB9B8CE1796F: dvtdevice-iphonesimulator:F8874B60-9233-423E-9C9C-2DC3E3A3509D and dvtdevice-iphonesimulator:F8874B60-9233-423E-9C9C-2DC3E3A3509D
I have removed Xcode from my computer and reinstalled it from scratch. But to no avail. There is something hiding in the cache that I should get rid of, but I have no clue what it could be.
So I upgraded to Xcode 7.3.1 and now my Xcode will build, and deploy my apps (yes every app, even a brand new blank one) to the simulator but the app never launches on the simulator and the debugger never attaches, Xcode just hangs and has to be force quit. I've completely wiped out Xcode and all simulators and re-installed to no avail. I've scoured Stack Overflow and Google trying every piece of advice and still no luck. Anyone anywhere have any idea how to solve this issue? If I downgrade to 7.2.1 I'm able to debug in the simulator just fine.
Let me know if you need more information.
My Apps run just fine on the simulator, and if I try to attach the debugger to a running app it wont and Xcode hangs in the attempt, when attempting to attach this way at least Xcode doesn't have to be force quit.
FYI, I can debug on a device this is only a simulator issue.
I had this same issue, and tried fixing my projects and reinstalled Xcode twice before I was able to get Simulator to crash and give me an error report that called out Cylance. Luckily I have access to administer our Cylance portal, so I was able to work through the issue to narrow down the problem.
Symptoms:
When running an app from Xcode, the Simulator launches but the application does not launch within the Simulator
Trying to stop the application from within Xcode does not work, and generates no messages
Trying to re-run the application from within Xcode generates the following message: ‘An instance of “APPLICATION NAME” is already running. Choose “Stop” to terminate and launch a new instance.’ But pressing Stop does nothing.
Xcode will not quit, and eventually the user must Force Quit to exit Xcode
Within the OS X console, the following messages are displayed:
6/3/16 7:35:38.000 PM kernel[0]: AMFI: com.apple.dt.ins(pid 2239) - [deny-mmap] main process is a platform binary, but mapped executable file is not: /Library/Application Support/Cylance/Desktop/CyMemDef.dylib
6/3/16 7:35:38.000 PM kernel[0]: AMFI: com.apple.dt.ins(pid 2239) - [deny-mmap] mapped file has team identifier XXXX: /Library/Application Support/Cylance/Desktop/CyMemDef.dylib
Resolution:
The problem is caused by Memory Protection being turned on within the policy assigned to the Mac within the Cylance portal.
To resolve the issue, place the Mac into a zone/policy that does not have Memory Protection turned on. Auto Quarantine and Protection Settings can be left on.
During my testing, I was not able to come up with a list of exclusions that allowed me to leave Memory Protection on, so I ended up disabling it completely.
I am having following problem with the location service with IOS on the simulator:
using phonegap 2.2.0 with xcode 4.5.2,
Cordova.plist EnableLocation = YES
navigator.geolocation.getCurrentPosition(myPositionSuccess, myPositionError, {maximumAge: 300000, timeout:10000, enableHighAccuracy : true});
myPositionSuccess is never called, with following error at navigator.geolocation
locationManager::didFailWithError (null)
I just tried it on the simulator. Any Idea?
Exit the simulator & run your app again. Worked for me.
I was having the same error with XCode Version 4.3.2 & cordova/phonegap 2.1.0
The simulator was unable to get my location even when I ran Google Maps in Safari. That led me to the conclusion that it was more than just my project that was at fault.
I am still unable to figure out exactly why restarting the simulator worked, but there is one possible reason.
I usually shut down my Mac without quitting most of my running apps & the "Reopen windows when logging back in" option checked. The simulator, however, is one of the apps i definitely quit. But the last time I shut down, I did not quit it. So, like I said, possible reason.
Hope this helps you.
Another thing may be to check the location setting in your simulator, I believe the default setting is none which means the geolocation will not find anything. If you are running your simulator, go to Debug > Location > City Run or some other choice and then try to use the geolocation function again it should work fine.
I know this is a bit old but I was looking for an answer on this when I remembered the location setting so I figured I would post here for future reference in case anyone needs it.
I keep getting this error when launching my app on the iOS Simulator:
Couldn't register com.mycompany.MyApp 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.
I've read other reports of this error and it seems there is no obvious fix for it (restarting the iOS Simulator, restarting Xcode etc..)
At this point here's a list of things I've tried:
Restarting the Simulator
Restarting Xcode
Rebooting my machine
Deleting my app's Derived Data, and Cleaning
Deleting the iOS Simulator App Support directory
Reverting to a 2 weeks old version of the app (which was working 2 weeks ago)
Deleting the application in the Simulator (by clicking-holding on it and hitting the X button)
Upgrading Xcode form 4.1 to 4.2, and running the app both in iOS Simulator 4.3 and 5.0
Nothing worked, I still get the same bootstrap error.. Any (and at this point I really do mean ANY) suggestion would be appreciated.
Edit: Just wanted to add that the app runs fine on a device. I only get this error on the simulator...
As the GDB said:
This generally means that another instance of this process was already running or is hung in the debugger
So find out it and kill it. ;)
I restarted the mac, and it run successfully.
Tip: Well, this may be not work sometimes, so I strongly suggest that you press cmd+. to make sure that you do have stopped the simulator (or device). I find that in most cases the simulator (or device) will not stop exactly when it crashes. I rarely met this issue again with pressing the cmd+. every time it crashes or even just normal exit. Hope this will be helpful. :)
I just closed my xcode & restart my device(ipad2) and it works for me :)
You can try this :: Couldn't register with the bootstrap Server
Another solution, go to clear the memory of the iphone simulator
Simulator > recovery content and setting
then run the program again.
i just change the identifier and the app can work again.
I had to change my bundle identifier finally
No matter you reboot all devices and cleanup all , it gets stuck hard in the debugger..
don't know how to clear it..
As I experienced, device (or simulator) restart does solve the issue,
BUT it would be better not to couse it.
Also my experience is that:
You can find the place of crash by cousing it. In such time developers usually press "STOP the running scheme" this could cause zombie process stuck in device.
BUT
if you press "COUNTINUE program execution", debugger will terminate the process, it will not become a zombie.
I had this error too and I noticed that it works for me if you close the simulator and stop the program and then change your company name.
I don't know why but it works for me.
I opened Activity Monitor and searched for my app name, and found another instance of it listed. I used Activity Monitor to quit that instance, and the problem went away for me.