You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
For some users on Android and Chrome (using commonvoice.mozilla.org/es), selecting the microphone button in the "Collaborate" view results in a 503 error.
To Reproduce
Hard to reproduce exactly, as not everyone experiences it. I have seen it on a number of occasions with different versions of android and using Chrome browser. Essentially the steps to reproduce would be
register as a new user on an android device using Google Chrome
click on "Colaborar"
hit the microphone icon to start recording
the page hangs for a few seconds and then loads a 503 error page reading "Estamos experimentando un tiempo de inactividad inesperado"
Expected behavior
Hitting the microphone button allows user to read the fragment aloud.
Screenshots
Desktop or Mobile (please complete the following information):
OS: Android
Browser: Chrome
Version: Various
Additional context
I'm not sure whether this is relevant, but I believe everyone who ran into this problem was on the Spanish language site ("/es").
The text was updated successfully, but these errors were encountered:
Lguyogiro
changed the title
[BUG] 504 for Android users when pressing the microphone button
[BUG] 503 for Android users when pressing the microphone button
Jul 27, 2022
Describe the bug
For some users on Android and Chrome (using commonvoice.mozilla.org/es), selecting the microphone button in the "Collaborate" view results in a 503 error.
To Reproduce
Hard to reproduce exactly, as not everyone experiences it. I have seen it on a number of occasions with different versions of android and using Chrome browser. Essentially the steps to reproduce would be
Expected behavior
Hitting the microphone button allows user to read the fragment aloud.
Screenshots
Desktop or Mobile (please complete the following information):
Additional context
I'm not sure whether this is relevant, but I believe everyone who ran into this problem was on the Spanish language site ("/es").
The text was updated successfully, but these errors were encountered: