google review id link results in 404
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Priority:P2, Webcompat Score:6, firefox143 verified)
| Tracking | Status | |
|---|---|---|
| firefox143 | --- | verified |
People
(Reporter: solaceten, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: webcompat:contact-complete, webcompat:site-report, webcompat:site-wait)
User Story
platform:android impact:feature-broken configuration:general affects:all outreach-assignee:jrmuizel outreach-contact-date:2025-08-25 outreach-response-date:2025-09-08
Steps to reproduce:
- go to google my business and click on reviews "get more reviews"
- copy the short url and send in email
- open email on phone and url launches the google review page in firefox
- receive 404 not found that's all we know
Actual results:
Also the same issue as noted here:
https://github.com/mozilla-mobile/fenix/issues/16767
Example URL to open in fenix
Direct URL: https://search.google.com/local/writereview?placeid=ChIJj61dQgK6j4AR4GeTYWZsKWw
Note: Direct url of google review page. This is not working when you open it in Firefox android browser but the same works fine in all other browsers without any issues.
Expected results:
should be working but appears to be a bug.
The exact error is:
- That’s an error.
The requested URL /local/writereview?placeid=ChIJj61dQgK6j4AR4GeTYWZsKWw was not found on this server. That’s all we know.
Updated•2 years ago
|
Comment 2•2 years ago
|
||
This seems to be server-side UA sniffing, as this fails on Desktop with the Firefox Android UA string as well. We could spoof, but flipping from a Firefox UA to a Chrome UA might upset the account management, as this is behind authentication. I've emailed Google folks, and I'll give them a bit of time before exploring intervention options.
Updated•2 years ago
|
Any update or work around? This is causing me a few headaches as we've just printed and distributed many of these QR code links to Google Reviews.... and all our clients are complaining about 404s....
Thanks
@denschub (Dennis Schubert)
Any update?
Comment 5•2 years ago
|
||
If there is an update, it will be posted here.
| Comment hidden (metoo) |
| Assignee | ||
Updated•2 years ago
|
Updated•2 years ago
|
Updated•2 years ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
I've emailed Google folks, and I'll give them a bit of time before exploring intervention options.
It's been 1.5 years. I hope this doesn't come across as pushy, but maybe mail them again please :)
It might be time to start thinking about intervention options soonish like spoofing the UA. as shitty as this feels to me. Spoofing the UA would only hit Nightly and then Beta first which would give Google some more time to get this fixed on their end.
The user experience has been ruined by this for over 4.5 years now :/
https://github.com/mozilla-mobile/fenix/issues/16767
Further links I collected: https://github.com/webcompat/web-bugs/issues/160116#issuecomment-2943252286
since, I can't edit, my last message was supposed to quote like this. Sorry for the spam:
I've emailed Google folks, and I'll give them a bit of time before exploring intervention options.
It's been 1.5 years. I hope this doesn't come across as pushy, but maybe mail them again please :)
It might be time to start thinking about intervention options soonish like spoofing the UA. as shitty as this feels to me. Spoofing the UA would only hit Nightly and then Beta first which would give Google some more time to get this fixed on their end.
The user experience has been ruined by this for over 4.5 years now :/
https://github.com/mozilla-mobile/fenix/issues/16767
Further links I collected: https://github.com/webcompat/web-bugs/issues/160116#issuecomment-2943252286
Comment 11•1 year ago
|
||
The severity field for this bug is set to S3. However, the following bug duplicate has higher severity:
- Bug 1984432: S2
:denschub, could you consider increasing the severity of this bug to S2?
For more information, please visit BugBot documentation.
Updated•1 year ago
|
Updated•1 year ago
|
Comment 12•1 year ago
|
||
Google fixed this.
Updated•1 year ago
|
Comment 13•1 year ago
|
||
I can confirm the fix using the latest nightly.
Comment 14•1 year ago
|
||
Verified, works as expected with the RC build.
Tested with:
- Browser / Version: Fenix 143.0-candidate build 1
- Operating System: Google Pixel 5 (Android 14)
Updated•1 year ago
|
| Reporter | ||
Comment 15•1 year ago
|
||
Yes I can confirm this works great now. Thanks everyone, can't believe it takes so long for Google to respond and fix it.
Updated•1 year ago
|
Description
•