Skip to content
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

Re-install not working after reboot, Mac OS 10.9.5 #11

Closed
johnnyutahh opened this issue Jun 1, 2015 · 9 comments
Closed

Re-install not working after reboot, Mac OS 10.9.5 #11

johnnyutahh opened this issue Jun 1, 2015 · 9 comments

Comments

@johnnyutahh
Copy link

I've rebooted and re-installed this solution several times, but on the latest reboot and re-install, it's not working. Details here: http://apple.stackexchange.com/q/189576/13179

Thoughts?

@szhu
Copy link
Owner

szhu commented Jun 2, 2015

I have a feeling Google completely dropped the API recently, since this error message you're getting "Sign in error: The operation couldn't be completed. (com.google.HTTPStatus error 404.) is unlike the previous one about JSON errors.

I can't test this myself anymore because I opted to use Voice through Hangouts, which prevents Voice from going to Voice.

@johnnyutahh
Copy link
Author

Thanks szhu. Has anybody else recently used GrowlVoice successfully? Specifically, has anyone attempted a Google-Voice account re-login?

@johnnyutahh
Copy link
Author

It looks like Google may have broken the API used by GrowlVoice:
http://apple.stackexchange.com/a/189766/13179

@mralexgray
Copy link

FUCK. This SUCKS. Google is such an ASSHOLE, sometimes.

@szhu
Copy link
Owner

szhu commented Jun 2, 2015

I think this is simply an issue of Google not reaping any profits from Voice. (pure speculation btw)

@mralexgray
Copy link

Well - then they should have come to grips with that BEFORE they offered a product on which people depend on - to which they constantly REMOVE features and interoperability.

@mralexgray
Copy link

why is this closed? people are so OCD.. if the problem is at all hard.. they'd rather close it than see an open issue. whatever, lol.

@szhu
Copy link
Owner

szhu commented Jun 2, 2015

This is technically a "won't fix" so that's why it was closed, but I will go ahead and open a new, more generic issue stating that this is no longer working.

@szhu
Copy link
Owner

szhu commented Jun 2, 2015

Superseded by #12.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants