Signing in checks your API token first, and errors give Screenly's reason
A token Screenly doesn't accept is caught at sign-in, and a failed add or update shows the reason Screenly gave.
Fixes
- Signing in checks your token with Screenly first. A token Screenly doesn't accept shows "Unable to sign in" on the sign-in page, instead of signing you in and failing when you add a page.
Improvements
- When adding or updating a page fails for a reason the extension doesn't recognize, the error includes the reason Screenly gave.