Clerk dev failing for latest devices when using device emulation about javascript

[jescalan]

We think that this is likely an issue with google, in that they do not yet trust the latest device emulation's fingerprint - if this is the case, we're not able to resolve this one and it would have to be a fix coming from google.

It is possible however that the issue happens because it's using our default shared OAuth credentials for dev instances. It's a bit of a long shot, but it may resolve the issue if you go into your clerk dashboard for the app you're using, navigate to "User & Authentication" > "Social Connections", and clicking the settings cog for the google OAuth connection, and check the "use custom credentials" box and fill them out with your own google app's credentials. Let us know if this does the trick!

[theonlyway]

Yeah I tried switching to my own oauth provider still no go. Doesn't look like there is any config options on the provider to set allowed user agents so I guess we can't really do anything until Google does something.