|We are seeing this Firefox bug (or a variant of it) get triggered https://bugzilla.mozilla.org/show_bug.cgi?id=548397|
|This showed up in our error reporting and the stack trace format is clearly a Gecko stack trace.|
|Example URL https://m-wikihow-com.cdn.ampproject.org/v/m.wikihow.com/Dress-for-Skiing?amp=1&_js_v=7 embedded as an iframe on https://www.google.com|
|The UAs are sometimes:|
|Mozilla/5.0 (Linux; Android 6.0.1; SAMSUNG SM-G920F Build/MMB29K) AppleWebKit/537.36 (KHTML, like Gecko) SamsungBrowser/4.0 Chrome/44.0.2403.133 Mobile Safari/537.36"|
|And more often:|
|Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B143 Safari/601.1"|
@cramforce I must be thick. but how do you know it's Firefox. You said:
What do you see in your logs? An example? For example on the Chromium bug, it shows it had been deployed at a point that would create the same issue than Firefox.
The UA override list for Firefox Android is public
Before b2g (aka Firefox OS) went RIP, the UA override list was
For all UA overrides with Google and services, we directly negotiate with google on a specific mailing-list. So that would have been known if there was an issue.
All of that said, I wish I understand better your issue on how to help you.
The reason why we know it is Firefox is because the error report we receive uses Firefox's stack trace format, which is distinctly different from Chrome and WebKit. We don't really have an immediate problem. The issue is clear in terms of how we can fix it (although we might have found a new bug in Firefox), we were just wondering why we see these UAs, as that drove our debugging session into the wrong direction.