-
Notifications
You must be signed in to change notification settings - Fork 5
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
Not receiving any authentication code #2
Comments
Hello? Is there anybody with the same issue? |
Hi, sorry for the late response! I am currently not maintaining this project anymore, but thanks for the information. In case I will start working on it again I will keep it in mind. |
Hi :) sorry to hear that :/ it’s a really useful project. Do you have any idea why this happens? |
Thank you! Yes it is. But also very time consuming. So I just tested it as well and you are right. Alexa says: "You just received a code on your phone. ..." However, I am not getting a code as well. So the frontend is working fine. The request for the code is sent to my backend. However, then something is happening in the backend. This code is not public though. So nothing much you can do. Sorry! |
Also the backend responds with the correct status code otherwise an exception would be raised and alexa would respond differently. Not entirely sure what is happening TBH. Maybe it just gets lost in the backend 🙈 |
Thank you so much for checking! |
Yeah, I've run into the same problem. Would it be possible for you to search up the confirmation code on your end? It would be greatly appreciated! |
Hello :)
I tried to get this skill to work. When entering my Telegram (and mobile) number and asking Alexa to start the authentication, there is no code being sent to my phone or telegram. Why is that?
If I replace the country code with a 0, I get sometimes a message saying this number has no telegram account.
I also tried to delete my account on your website which didn't seem to work. I can still login using the same google account
Hope this helps you to find the bug :)
The text was updated successfully, but these errors were encountered: