-
Notifications
You must be signed in to change notification settings - Fork 312
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
Mobile Safari webview fails to match user agent #458
Comments
Wow, that's a pretty intense custom property. Would you be able to post some sample user agent strings here and the expected browser + version props that we should extract? That would help get this updated faster. Thanks. |
Sure. Just as a warning, it seems that the UAs don't contain the exact Safari version, but do contain the OS version (which is most of the time roughly the same), so there would potentially need to be some kind of lookup table.
|
Note, I think the output of |
Another example for iPad:
|
Hey,
We at Genius are facing an issue where we're seeing a large portion of our users having no set mobile safari browser version, and after some investigating, we tracked down the cause. It turns out that if you open a webview inside another app (e.g. if you are using the twitter app and click on a link there), it opens in a browser instance within that app, making the user agent matching fail.
It would be great if Mixpanel could automatically translate the iOS version to the bundled Safari webkit version (which is what we had to do in order to fix this), so that we always have accurate Safari versions, that would be awesome!
We found what could be considered a workaround, not for overall version but for specific browser features, by adding a custom computed property. For instance, we used this query to determine what percentage of our users would support a new CSS feature:
The text was updated successfully, but these errors were encountered: