When I try to do anything in Playground, this pops up before I even finish typing a word.
Error running playground.
Failed to launch iOS stub for playground: The operation couldn’t be completed. (Mach error -308 - (ipc/mig) server died).
and when I just try to run IOS Simulator I get the following error
Unable to boot the iOS Simulator.
oh and this error just popped up
An error was encountered while running (Domain = DTiPhoneSimulatorErrorDomain, Code = 2)
I tried rebooting, I closed out and opened again, I deselected file and reselected. Just keeps happening. Anyone have a solution?
Your firewall is blocking the debugger, you need to allow it to connect:
TCP out 127.0.0.1:63748
Or allow the debugserver process open access (whichever you, or your firewall, prefer(s)).
Upon enabling it, and restarting Xcode everything should work like a charm.
Note/Update:
If you're having trouble finding, or allowing, the debugserver simply try, temporarily, disabling your firewall and restart xcode. Does the playground work? Oh, and don't forget to make sure you've got the assistant view open and the output box showing.
Currently the Xcode 6 beta needs to reside in \Applications for the playground and simulator to work. After you move it there you need to reboot.
This error popped up for me when I closed the simulator before Xcode finished attaching my application to it. Opening the simulator and running the app again solved this problem.
Related
I have stoppped appium server and then I tried to capture object through UIAutomatorViewer, but still it throws the error as "Unexpected error while obtaining UI Hierarchy". I have tried the following options.
Stop Appium server in the background.
Disconnected mobile device & connect it back.
3.close the uiautomatorviewer.bat file & restart it again.
Restarted the device
a. Turn on USB DEBUGGING
b. Enable view attribute inspection
c. Select the debug app option and choose io.appium.uiautomator2.server
adb devices to recognise my device.
I have exit and restarted uiautomatorviewer
After tried all the above options, still I get the same error.
Please help to get this issue resolved.
UIAutomatorviewer Error
I sometimes start to get the following error
2017-04-02 18:55:22.645937+0200 Stamps[730:111791] Connection peer
refused channel request for
"dtxproxy:XCTestDriverInterface:XCTestManager_IDEInterface"; channel
canceled Failed to run tests: The operation
couldn’t be completed. (DTXProxyChannel error 1.)
Last time, when this happened, I just did some random actions with clean my project, remove derived data etc., and it was fixed. Now, it happens again - just after a start of the app, it closes and log contains this error.
What does it mean and is there any workaround here?
I use XCode 8.3, Swift 3.1, test on device 6s with 10.3 installed.
Surprisingly, to fix this, I just replugged my iPhone to another port
When I use the iOS simulator I've no issues with attaching to a process. But when I want to attach to a process on my iPhone it doesn't work. When I type in the process name and click on Attach it takes a while before showing me the following error:
It seems that I get the same error for any process identifier, even when the process identifier doesn't exist:
I think this issue is due to my iPhone (5S iOS 8.3), because on another iPhone (5) I don't have this issue. Can someone please help me...
This issue was only occurring on my iPhone 5S and after a factory reset the issue didn't occur anymore.
Issue
Most times, when I try to debug my custom keyboard extension, I receive the following error and then the keyboard disappears (presumably crashes, so the system removes it from screen and replaces it with the standard keyboard)
plugin com.db.Trype.TrypeKeyboard interrupted
(Note: Trype is the name of my keyboard.)
Process
I am debugging the keyboard the following way:
I have the keyboard extension as a target.
I've modified the TrypeKeyboard scheme to run my app executable on launch.
The keyboard has been added in the Simulator's Settings App.
I've tried different version of Xcode-Beta and tried restarting the simulator, computer, etc., all to a varying degree of temporary success.
Anyone else run into this error and have a suggestion?
Update:
Here is an accompanying error message. Maybe there is some way to print out more of the UserInfo?
viewServiceDidTerminateWithError:: Error Domain=_UIViewServiceInterfaceErrorDomain Code=3
"The operation couldn’t be completed. (_UIViewServiceInterfaceErrorDomain error 3.)"
UserInfo=0x7fc99c900a50 {Message=Service Connection Interrupted}
After messing around with it some more, I'm beginning to conclude this is an iOS 8/Xcode bug with the way that extensions are debugged.
Xcode sometimes seems to build project and install multiple versions of the extension keyboard into the iOS simulator. It also occasionally kills the extension and reloads it. Very strange behavior. Just sitting and staring at the debugging sidebar shows it get killed (disappear) and then relaunch.
The first is a successful launch.
The second is an unsuccessful launch where the extension appears to hang and wait to attach.
recently I was playing around with the custom keyboard extension in iOS 8 Beta with Swift (Xcode beta 6), but I keep getting this error when I run it on a simulator, it seems to be quite random and I've no idea what causes it:
plugin com.name.app.extensionName interrupted
Hub connection error Error Domain=NSCocoaErrorDomain Code=4097 "The operation couldn’t be completed. (Cocoa error 4097.)" (connection to service named com.name.app.extensionName) UserInfo=0x7b087720 {NSDebugDescription=connection to service named com.name.app.extensionName}
I have no idea what to do. I can't test the app on a real device at the moment, therefore I'm stuck here. It happens on all types of simulators, I already reset them and restarted Xcode and my computer.
I hope you can give me any advice or maybe even know a fix!
I had this problem in Today Extension written in Objective-C. After updating to XCode 6.0.1 and building my project it started saying about missing ARM64 Architecture. When added arm64 it started working well. Try to play with it
I tried a variety of things to resolve this and ultimately what fixed it was "cleaning" my application (on the "Product" menu). I don't know what that really does, but I "cleaned" it, then restarted the simulator and suddenly everything is working again.