OpenID Connect Playground VS AWS Device Farm

I too found this hard to reason, but figured it out: If you're demoing using https://openidconnect.net for example, set your Client ID to https://openidconnect.net Likewise, your ClientID should match the id of the website your are using this on. This was mentioned in the GitHub readme too but didn't click until trying the demo. - Source: Hacker News / 7 months ago

Browserstack - 30 minute trail available AWS Device farm - 1000 minutes trail with aws free tier You can also go DIY with setting up playwright and configuring it to emulate safari browsers. Source: 10 months ago

You can still use it for building, just not testing. You can probably automate tests using The AWS Device Farm or similar system, but it may be easier to just install each build on your own device and run the tests manually. Source: about 1 year ago

Something I found last minute: Unfortunately this is not supported by AWS Device Farm and it's not clear when it will ever be. This means that this is only supported locally, or for any remote/grid servers that have built-in support for it. I happen to run into the error DevTools is not supported by the Remote Server. If anyone has any solutions or workarounds for this, I'm all ears! - Source: dev.to / over 1 year ago

Don’t muck with automating simulators, it’s a PITA: we used Https://aws.amazon.com/device-farm/ and it was ok. This was pretty ok: Https://bitrise.io As much as I hate Microsoft, https://appcenter.ms was workable, but required the most calories and was slow. Source: over 1 year ago

Also https://aws.amazon.com/device-farm/ helps testing on devices if you've got it built. Source: over 1 year ago