Xcode 10 stuck while trying to launch app (tccd process)

[absolutlabs]

Hello

After unsigning, Xcode fail to launch the app on the simulator. It's stuck (/frozen) on "Waiting for iPhone .. to start / Attaching to .. on iPhone .. ". I then need to "force quit" to stop xcode.

I found that the tccd process is around 100%, sometimes even more, which is not the case when not unsigning.

It appears on both Xcode 10.0 and Xcode 10.1 beta. (macos mojave)

I tried to check / uncheck the permission for xcode to access the contacts, it didn't help as it did with previous versions :/

Note : It works fine when launching app on device, even if the tccd process is high too.

[nayzak]

Same issue. It reproduces only in macOS Mojave. But there is no need to force quite Xcode. After some time (5-10 minutes) application launches in simulator and after that application launches fine on reruns.

[absolutlabs]

I just successfully unsigned Xcode 10 using the install script of https://github.com/wakatime/xcode-wakatime .
Everything works (or seems to work) fine

[nayzak]

I also unsigned Xcode using sudo codesign -f -s with self signed certificate, it did not help.

[inket]

The error that I found with tccd is:

error 09:56:34.309918 +0900 tccd Failed to copy signing info for 24646, responsible for file:///Applications/Xcode.app/Contents/MacOS/Xcode: #-67062: Error Domain=NSOSStatusErrorDomain Code=-67062 "(null)"

It seems not having a code signature is a no-go with the new macOS permissions database (tccd).

As @absolutlabs mentioned, codesigning it with a self-signed certificate will get it to work fine.

[Ycong]

@absolutlabs Works for me.

[showtestlog]

does anyone solve it?

[Adamus7]

The error that I found with tccd is:

error 09:56:34.309918 +0900 tccd Failed to copy signing info for 24646, responsible for file:///Applications/Xcode.app/Contents/MacOS/Xcode: #-67062: Error Domain=NSOSStatusErrorDomain Code=-67062 "(null)"

It seems not having a code signature is a no-go with the new macOS permissions database (tccd).

As @absolutlabs mentioned, codesigning it with a self-signed certificate will get it to work fine.

May I know where did you get this log?