-
Notifications
You must be signed in to change notification settings - Fork 28
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't log in even after uninstalled wakatime #52
Comments
I have the same problem, every time I reinstall Xcode it runs fine, and when I install wakatime plugin after few days I have "Couldn't communicate with a helper application". It's really annoying, hope It will be fixed soon because currently, wakatime for me is almost unusable because of this. |
if it's possible for you please fix this bug as soon as you can. |
Please fix this bug... |
I agree with the others. Please fix this issue. I love this plugin for helping me analyze my work. However, when it comes to releasing software to the app store, it prevents me access to my Apple account for signing and verification. |
Does keeping two versions of Xcode (one with WakaTime and one without for publishing) help? We've been trying to find a way to fix this, but it doesn't seem possible without Apple's help currently. |
Please please fix this bug... |
Currently we don't have a way to fix it without help from Apple. |
Apple's response:
|
Is that mean you can not fix this issue? |
It's sort of continued from Issue #49, and on Xcode 12.3 here.
Even after uninstalling wakatime, the issue still won't fix. It would still say "Couldn't communicate with a helper application". Seems like the easiest way to solve it might be to reinstall Xcode.
Seems like the problem was my keychain and certificate files for Xcode were deleted during installation.
Probably due to the same reason, my Github account on Xcode can't stay logged in. It requires me to reenter my token every time I quit and reopen Xcode.
It might be a good idea to suggest clone your Xcode as the default installation method on the installation page
The text was updated successfully, but these errors were encountered: