Can't log in Apple ID after installing wakatime

[billchen2k]

XCode version: 12.2 and 12.1

After installing wakatime, apple id can't log in. The error says "Try your operation again. If that fails, quit and relaunch the application and try again."

Installing on a real device is also impossible in this case, the only solution is to uninstall XCode completely and reinstall.

[YLS-]

I have the same problem with Xcode 12.2 (non-beta, installed directly from AppStore, no problem before Wakatime re-signed the app). Not being signed in with Apple ID prevents archiving (among others), so it mostly makes Xcode unusable if you want to do frequent releases.

I ended up using the latest beta version (without Wakatime) for archiving / AppStore releases, and using the normal version (with Wakatime) when coding. Not ideal but good enough of a workaround for now.

[renearias]

i have te same problem

[alanhamlett]

From a working Xcode.app without WakaTime, run the install script with copy argument. That creates a new unsigned XcodeWithPlugins.app with WakaTime in your Applications folder, and leaves the original Xcode.app signed. Use the original Xcode.app when releasing, and the copied XcodeWithPlugins.app for normal development when you need plugins.

curl -fsSL https://raw.githubusercontent.com/wakatime/xcode-wakatime/master/install.sh | sh -s copy

[alanhamlett]

Hopefully someday Xcode's Source Editor Extensions will support plugins without requiring user interaction: http://openradar.appspot.com/radar?id=6715695387639808

That's the only long-term solution. Until then, hopefully this workaround keeps working.

[gleich]

I am also having this problem. The copy seems to work in the meantime.

[Mh-ghadamyari]

I am also having this problem. the copy is working for me but it isn’t the way of fixing bugs if possible to you fix this bug. Thanks 🙏

[iOSGonzo]

Have this issue as well. Just confirmed by reinstalling Xcode and it broke once I installed Wakatime again. Copy method not working either.

[Mh-ghadamyari]

if it's possible to fix this bug I want to use waka time but I think you don't read us and don't want to fix this problem.

[jsyrtsov]

I have the same problem.

[gleich]

This seems to be a pretty popular issue. Any future viewers please just react 👍 instead of commenting. Thank you :)

[chachaxw]

From a working Xcode.app without WakaTime, run the install script with copy argument. That creates a new unsigned XcodeWithPlugins.app with WakaTime in your Applications folder, and leaves the original Xcode.app signed. Use the original Xcode.app when releasing, and the copied XcodeWithPlugins.app for normal development when you need plugins.

curl -fsSL https://raw.githubusercontent.com/wakatime/xcode-wakatime/master/install.sh | sh -s copy

It takes too much disk memory...I guess I will give up Waka time plugin on Xcode 😢

[scris]

It's because of the new rules made by Apple, which made Xcode working only when on the original sign, in order to enhance safety. There's a better workaround probably able to fix things up. See https://github.com/XVimProject/XVim2/issues/340#issuecomment-812899339

[yasghadamyari]

I have the same problem. if possible you please please please fix this bug if the Xcode users are important for you please fix this bug for us.

[alanhamlett]

It's because of the new rules made by Apple, which made Xcode working only when on the original sign, in order to enhance safety. There's a better workaround probably able to fix things up. See XVimProject/XVim2#340 (comment)

Thanks for the link! It's been hella difficult getting xcode-wakatime working after Apple broke plugins, and it seems our only current fix is what's causing the Apple ID issues. It's a catch-22, fixing the Apple ID login would mean disabling the wakatime plugin.

XVim has a large community behind it, so I'll go through their issues to see if anyone has found a workaround to enable plugins and also allow Apple ID login.

[alanhamlett]

Related to #36 which has more comments.

[GalvinGao]

From a working Xcode.app without WakaTime, run the install script with copy argument. That creates a new unsigned XcodeWithPlugins.app with WakaTime in your Applications folder, and leaves the original Xcode.app signed. Use the original Xcode.app when releasing, and the copied XcodeWithPlugins.app for normal development when you need plugins.

curl -fsSL https://raw.githubusercontent.com/wakatime/xcode-wakatime/master/install.sh | sh -s copy

IMO it might be a good idea to put such notice on the installation guide. Ran into this issue and the only way to get Xcode back to working seems to clean the Command Line Tools (as suggested here) and re-install Xcode completely :(

[elpheen]

For future reference, you don't have to delete everything and start over.

Simply rename the already modified Xcode to XcodeWithPlugins then download a fresh Apple signed copy of Xcode.

You'll use the original Apple one when you need to do codesigning, but otherwise the copy with Wakatime is 100% functional.

[shandogthecat]

For future reference, you don't have to delete everything and start over.

Thank you SO MUCH for clarifying this. Encountered this issue today and was dreading inadvertently messing it up, as it takes at least an hour to download a new copy of Xcode. At least this way I still have a copy I can work from in the meantime.