Just updated to macOS Mojave and then from Xcode 9 to Xcode 10 (via App Store). But when I start Xcode 10, it starts for a second and then immediately closes, no error messages or crash report dialogs are shown.
I opened the Console app and saw some log messages that might be related:
CODE SIGNING: cs_invalid_page(0x1048a3000): p=6061[Xcode] final status 0x23006a00, denying page sending SIGKILL
CODE SIGNING: process 6061[Xcode]: rejecting invalid page at address 0x1048a3000 from offset 0x282000 in file "/Applications/Xcode.app/Contents/SharedFrameworks/DVTKit.framework/Versions/A/DVTKit" (cs_mtime:1536705076.0 == mtime:1536705076.0) (signed:1 validated:1 tainted:1 nx:0 wpmapped:0 dirty:0 depth:0)
I solved it by deleting Xcode 10 (and also Xcode 10 beta that I had installed as well). Then reinstalled Xcode 10 from the App Store. Also restarted computer. Then it worked.
I deleted xcuserdata from within the xcworkspace and it fixed it for me... much faster than re-downloading xcode.
Related
I have recently upgraded both Xcode (to 11.5) and Mac OS to Catalina. Xcode has been working fine for a few days. I clicked on a JSON file in my project and Xcode hung (with SBBOD). I forced quit and rebooted but now Xcode will not load - it starts, but just shows SBBOD again. On startup, it tries to load my last project, I have tried launching from Finder by clicking on a PlayGround project but same issue!
Any suggestions for how I recover this situation?
While the cause is not resolved, I left Xcode running overnight and it is now working. This issue seems to be with displaying a large JSON file (about 1MB). Xcode is taking a few hours before it becomes responsive. I just left it to run.
My app has started failing on devices seemingly out of the blue. When debugging it just hangs and sits there. Doesn't crash. I've found the following errors in the device log:
Error (0) / kernel(Sandbox): TUE.myiOSApp(629) System Policy: MAP_JIT requires the dynamic-codesigning entitlement
Error (222) / DTServiceHub(FrontBoardServices): [FBSSystemService][0x658f] Sending request to open "com.MyAppName”
Error (589) / SpringBoard(FrontBoard): [com.MyAppName] Provision violated for watchdog scene-create: <FBSProcessResourceProvision: 0x1c54fa400; allowance: <; FBSProcessResourceAllowance; type: realTime; timeValue: 18.57s>; violated: YES>
Error (589) / SpringBoard(KeyboardArbiter): [<_UIKeyboardArbiterHandle: 0x1c4115720; PID 631: com.MyAppName <(null)>; hosting PIDs {(
Error (589) / SpringBoard(KeyboardArbiter): -[_UIKeyboardArbiter runOperations:onHandler:]_block_invoke Failed to access <_UIKeyboardArbiterHandle: 0x1c4115720; PID 631: com.MyAppName <(null)>; hosting PIDs {(
I noticed another line that mentioned the process wasn't killed by the OS because it was being debugged.
This started happening right after I added a new device to the developer profile at the Apple Developer portal. I redownloaded the profile and installed it in xCode and in Visual Studio for Mac. The first time I ran the app on the new device, it ran successfully and I could debug. After that it started freezing. It also freezes on the old device I had been debugging successfully on just moments prior.
I've tried cleaning the solution, deleting all bin/obj folders. Restarting the device. Rebooting my Mac, etc.. nothing works.
I've dug around a little bit regarding the MAP_JIT error, however, the only answers I've found is to ensure Xcode is up to date. I'm on Xcode 11.3.1 and the command line tools are installed.
I updated to the latest version of Visual Studio for Mac which did not solve the issue
Any ideas?
Thanks!
Sean
For the past months I have not been able to debug macOS or iOS apps through Xcode. What happens is the following:
Build and run app from Xcode.
Xcode says app is running, but no app has appeared and no debug output from app either.
Kill the process lldb-rpc-server.
App appears and runs as normal, but Xcode is no longer debugging.
Start a new debugging session by attaching it to the app's process.
App freezes again, until lldb-rpc-server is killed.
This OpenRadar has the same description.
I have tried re-installing Xcode (including command-line tools), but it didn't help. Any ideas?
Xcode: Version 9.3.1 (9E501)
MacOS: 10.13.4 (17E199)
The cause of this was that I had installed a GDB/LLDB-extension called Voltron. I was unaware that the installation also created/modified the .lldbinit in the home folder. Removing this file fixed the issue. See also this issue for Voltron.
Got some very good help from Apple.
I had received this warning msg when device was locked and I was running app on device, so when device is unlocked this warning goes
I have been building mac app on my mac mini and it always worked well but today i faced this error, searched a lot but no luck.
Message from debugger: unable to attach
What i tried:
Clear derived data
Quit Xcode
Restart machine
installation directory set to blank and also to /Applications
Tried Skip Install No / Yes
Using developer Signing certs
M using only Developer certificates and not provisioning profile to sign my cocoa app
Xcode 8.2
OSX 10.12.1
Please help :)
This is what fixed it for me, perhaps it will help others but I do realize the question was for 8.2. I had it set to Xcode 9 "New Build System" disabling this and switching to "Standard Build System" in the Project Settings under the File Menu. I had tried all the other things like killing DerivedData, clean build, restarting Xcode. I also verified that my dependent libraries were set correctly. The only thing that worked was disabling new "New Build System"
I just had this problem today. I have little demo code in a mac project(created with Xcode 9.4). This error just started to occur after I upgraded system to macOS Mojave 10.14. However, in Xcode 10 this project runs no problem(without changing anything). If you can use Xcode 10 it will probably be fixed.
Unfortunately, the above solutions didn't work for me (although I am sure they work for some people).
Here is what worked for me, in case this helps anyone else:
Close Xcode
Open Xcode and Create a new Xcode project
In the iOS template, select Single View App then click Next
yes, I know you are trying to get a macOS app attaching to the debugger :).
Give the iOS app any product name and organization identifier you would like and click Next
Create the new project anywhere you would like (I saved it to my desktop)
Build and run (cmd + r) the iOS app on a simulator like the iPhone 8 (starting a simulator and running the iOS app will take a little time, so have patients)
After the iOS app runs in the simulator, click to stop it from running (the stop button is next to the run button)
Open your macOS app that you are having trouble connecting a debugger to, and build and run it (cmd + r)
This, for some reason, allowed me to connect to the debugger with my macOS app...
Xcode version: 10.1, macOS Mojave version: 10.14.2
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.