Is this a…:
Standard bug
Steps to reproduce this issue:
I tried logging in using the QR code and the Waze app.
When receiving the 2FA code (which takes quite some time), I just got a “something went wrong” after entering it. The “remember system” checkbox was checked.
Waze App was current beta.
Environment where the bug occurs…:
ROW
Permalink:
n/a
Browser name and version:
Librewolf 145.0.1-2
Are you using scripts? Please detail which ones.:
Many (but n/a as the problem was on the app to login)
2 Likes
Hello @Alpha_VA.
Thank you for reporting the problem. I have filed an internal ticket for this case and will keep you posted on any updates.
I want to additionally ask you: is it reproducible for both iOS and Android platforms on your end?
Regards,
Vladyslav
2 Likes
I’m using Android only, so I cannot make any statement on iOS.
Hi @Alpha_VA,
Thank you for your clarification on that. Can you please also specify what exact time it happened, whether you can still reproduce it consistently?
All the best,
Vladyslav
So, I tried it just now, 2050 MET:
Findings:
With Firefox beta (embedded): does not work
with Chrome (embedded): does work
Firefox uses NoScript to block unwanted scripts. In the embedded mode, the control elements are not shown thus I cannot enable any blocked domain. Looks like some scripts got blocked, as it worked with Chrome.
Another thing: Chrome is routed directly where Firefox is routed via VPN and a special IP (assigned to me). Might also be a reason.
Not the most common setup, but in the Internet, you must expect everything and cannot rely on anything.
1 Like
Hi @Alpha_VA,
Thank you for the provided details! I’ve transferred this information to the team and I’ll keep you posted here regarding further updates.
Best wishes,
Vladyslav
Hi @Alpha_VA,
Are you able to find out which network requests are being blocked? We ask because we cannot debug a custom setup, especially if things are being blocked browser-side.
Awaiting for your feedback.
Regards,
Vladyslav
Hi!
I tried it again with Firefox Beta and this time, it did work. No clue what has changed. As mentioned, Waze uses the system standard browser in embedded mode so the usual control elements showing what might be blocked (and then could be unblocked if that was the reason) are hidden.
1 Like
@Alpha_VA,
If embedded mode is the issue, could you please try signing in at www.waze.com/signin instead? The credentials should carry over to WME.
Awaiting your feedback.
Best wishes,
Vladyslav
As I said, I tried it again and could signin even with the embedded variant. So I cannot reproduce the issue anymore.
@Alpha_VA,
Thank you for your confirmation that the issue is not reproducible on your end anymore.
I will close this report as fixed now.
If you have any questions or additional feedback, please don’t hesitate to reach out—we’re happy to help!
Regards,
Vladyslav