-
Notifications
You must be signed in to change notification settings - Fork 56
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
get key failed from google #33
Comments
Google might change the way to store the key. I will take a look. Thanks. |
I've also been using this package for a while now and am experiencing the same error. |
The original way the library get the secret token key from the google website cannot 100% guarantee success now. I plan to re-write the project to handle this issue in another efficient way: caching the token key so that we don't have to fetch the token key every time. I also plan to add some new features, such as supporting long text input. It will be expected to have some breaking changes. Thanks. |
There are two patterns for Google Translate page URL ( https//translate.google.com ) contents and the contents sometime doesn't contain Google might is introducing new process about TTS into Google Translate But @timothydillan found that we can play TTS mp3 URL without the |
@horihiro Wow, it's really cool that we can access the URL without a token key! Thank you for your investigation. It's really informative.
|
Please try |
@horihiro thanks, even if I fair this is dangerous:
|
Hmm, In my environment, the following url can be downloaded. |
The approach #33 (comment) by @horihiro has been implemented in PR #37 by @freddiefujiwara. Thank you all. 🎉 |
Hi
this is not an issue, just a note.
I'm using google-tts (THANKS) in https://github.com/solyarisoftware/jointts, my work in progress package.
I also used google-tts in past an run smoothly.
recently I experiencing some errors like
Error: get key failed from google
(google-tts-api/lib/key.js:30:32). I presume it's a Google API reject/error. Apparently errors arise random (e.g. not related to API calls rate).Workaround (not rocket-science): because the google API raise error occasionally, I retry until I got success.
In few shots the API return success (I admit, that's dirty):
Any idea?
Thanks
giorgio
The text was updated successfully, but these errors were encountered: