Understanding login failures when signing into Gearset
When Gearset shows “There’s a problem logging you in”, it means the sign-in process failed before Gearset could complete authentication. These errors usually come directly from the identity provider (Salesforce, Google, LinkedIn, etc.), not from Gearset itself.
If you click “Further information >” on the error banner, Gearset will show the underlying OAuth error:
Error reason – usually a short code like invalid_grant, invalid_client, access_denied, OAUTH_APP_ACCESS_DENIED
Error description – a human-readable message returned by the provider if it exists
This article explains some common patterns behind these errors across providers. The exact meaning can vary per provider, so if you’re an admin, always refer back to your provider’s own docs as well
Check the exact error message
After you click “Further information >” on the error banner, you’ll see the specific error reason and error description (for example, OAUTH_APP_ACCESS_DENIED or invalid_grant). These come directly from the provider and indicate what went wrong.
If you contact Gearset support, please include both the errorReason and errorDescription — they help us narrow down the root cause quickly.
Possible causes
IP restrictions
Your Salesforce org or profile may restrict logins to certain IP addresses. If Gearset’s IPs are not allowlisted, login attempts may fail.
You can review how to allow Gearset’s IP addresses here:
Connected app access
If you see an error beginning with OAUTH_APP_ACCESS_DENIED, Salesforce is preventing your user from accessing the Gearset connected app. This often happens due to the recent Salesforce connected app restrictions change.
Please check this document to learn How to install the Gearset Connected Apps.
Safari on older macOS versions
Some users on Safari, particularly macOS 10.14 Mojave, have reported issues with modern OAuth login flows due to cookie and redirect handling.
If you are using Safari and cannot sign in:
Try Chrome, Edge, or Firefox, or
Update macOS/Safari if possible.
If login works in another browser, it is likely a browser/cookie support issue rather than a Salesforce or Gearset issue.
Other provider-specific issues
You may see generic OAuth error codes such as:
invalid_grant
invalid_request
invalid_client
access_denied
invalid_scope (Google/LinkedIn)
These codes can mean different things depending on the provider, and they come directly from that provider’s OAuth implementation. Gearset cannot interpret them automatically, but you can check the provider’s documentation below:
If the error reason or error description matches one of these categories, your identity provider or admin may need to adjust the connected app, scopes, or access policies.
If the problem continues
If retrying the login and checking the sections above doesn’t resolve the issue:
Click “Further information >” on the Gearset login screen.
Copy error reason and error description (if present)
Click "The above didn't help" and send us a short message via that includes:
The error reason and error description
Which login option you used
We’ll review the details and get back to you with next steps.