System requirements
The dash runs in the browser, there is nothing to install. On a reasonably current computer that is the whole story: Chrome, Firefox, Safari or Edge will do. It gets interesting on older tablets and phones, because there is a hard limit there.
When signing in does not work at all
Section titled “When signing in does not work at all”On very old devices the sign in page loads, but that is as far as it goes. It is neither your account nor your password: before signing in, your browser solves a small calculation in the background that keeps mass sign in attempts away. Older devices no longer manage it, and without it there is no way in. A different browser does not help there, because it runs on the same dated foundation.
This affects devices that no longer receive updates, among them iPad Air 1, iPad mini 2 and 3 and iPad 4. They stay on iOS 12, and that is not enough.
What helps instead: a newer device or a computer. If you have none at hand and urgently need to reach your account, support can help; they will verify your identity in the process.
What a device has to bring
Section titled “What a device has to bring”- Computer: Chrome, Firefox, Safari or Edge, each in a current version.
- iPhone and iPad: iOS or iPadOS 14 and newer.
- Android: Android 9 and newer.
Older versions are not blocked, they simply fail at the sign in step.
Passkeys ask for more
Section titled “Passkeys ask for more”A passkey needs a device that can handle one, and very old devices cannot. There the authenticator app, recovery codes and SMS remain as the second factor.
The difference that causes the most trouble in practice is not creating a passkey but moving it: on newer devices a passkey is available on your other devices shortly after you create it, on older ones it stays on that single device forever. What this means in practice, and why recovery codes are essential in that case, is covered under account security.
What else matters
Section titled “What else matters”- JavaScript has to be allowed. The dash is an application, not a text page.
- Cookies for the session. Without them every sign in ends immediately.
- A reasonably correct clock. If the time is far off, one time codes are rejected and secure connections can fail.
For anything not covered here: support can usually tell quickly what is wrong once you name your device and browser.