I have recently started getting this warning in Xcode when working in Simulator mode. Apple were not able to help and suggested I submit a bug report, which I have done. But I wondered if anyone here has experienced the same?
It occurs when the keyboard is used during Simulator mode only. The screen freezes for a few seconds and then carries on. Very frustrating.
-[UIKeyboardInputManagerClient handleError:forRequest:] will retry sending handleKeyboardInput:keyboardState:completionHandler: to keyboard daemon after receiving Error Domain=NSCocoaErrorDomain Code=4097 "connection to service named com.apple.TextInput" UserInfo={NSDebugDescription=connection to service named com.apple.TextInput}
Related
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.
This is the log in console.
2016-10-19 4:35:30.377 PM com.apple.CoreSimulator.CoreSimulatorService[761]: Error saving /Users/myusername/Library/Developer/CoreSimulator/Devices/14ABD200-69D3-441D-8FAA-731F5F00F678/data/tmp/com.apple.lsdidentifiers.plist : (null)
/Library/Developer/CoreSimulator/Devices/14ABD200-69D3-441D-8FAA-731F5F00F678/data/tmp/ is an empty folder.
Meanwhile, my xcode can not load xib or storyboard properly. "Internal error occurred, Editing functionality maybe limited"
I did clear /Users/myusername/Library/Developer/CoreSimulator/Devices/ folder, doesnt help, re-install xcode doesnt work.
environment: OS: EI 10.11.6, xcode: 8.0 simulator:Version 10.0 (SimulatorApp-700.5.3
The error message is benign and can be ignored. Sorry about the noise in syslog. The issue has since been resolved in the Xcode 8.1 betas.
If you deleted ~/Library/Developer/CoreSimulator/Devices while CoreSimulatorService was running, the service will be in an inconsistent state. You should SIGKILL it to cause it to relaunch in a new state.
Your 'Internal error occurred, Editing functionality maybe limited' error message is likely unrelated to either of those things. Most users see that because they're trying to use multiple copies of Xcode.app at the same time. It's perfectly fine to have multiple Xcodes installed, but you can only use one at a time. If that's not the issue you're seeing, you will need to provide more information about the error.
fixed it by turn off System Integrity Protection in El Capitan.
I totally have no idea when I updated mac os, and got this issue.
Until I noticed that I cant start mysql, which has similar issue 'Could not create unix socket lock file /tmp/mysql.sock.lock'
Then I thought something went wrong with my os settings.
steps:
Restart your Mac.
Before OS X starts up, hold down Command-R and keep it held down until you see an Apple icon and a progress bar. Release. This boots you into Recovery.
From the Utilities menu, select Terminal.
At the prompt type exactly the following and then press Return: csrutil disable
Terminal should display a message that SIP was disabled.
From the menu, select Restart
for more information https://apple.stackexchange.com/questions/193368/what-is-the-rootless-feature-in-el-capitan-really
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 want to know about this error. Why this is happening. When I type some text, my keyboard doesn't respond . It gives this error :
-[UIKeyboardInputManagerClient handleError:forRequest:] will retry sending
generateCandidatesWithKeyboardState:candidateRange:continuation: to keyboard daemon after
receiving Error Domain=NSCocoaErrorDomain Code=4097 "The operation couldn’t be completed.
(Cocoa error 4097.)
I have to wait some time so that I can type the text again. Please suggest me how can I remove this error.
Thanks a lot.
I have only seen this happen on the simulator. I was able to resolve the issue by resetting the simulator through iOS Simulator -> Reset Content and Settings...
Some time simulator is not working .
iOS Simulator -> Reset Content and Settings
and Click.
Xcode->Product->Clean ..
It is working for me.
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.