Has anybody else run into this? For some reason, every user we onboard who connects using Gmail over Nylas has their grant expire within a week or two, which has made it impossible for us to roll our functionality out to more users. The Nylas help desk articles are really unhelpful, blaming the user for changing passwords or gmail making other changes that prompt the deauthentication, but when talking to the users, they claim they have not made any changes to their gmail account.
Hello, Oskar!
We try and cover the generic cases in the articles, for Gmail grants this typically happens if your GCP Application that was/is used as a connector is unverified by Google, or if your app is requesting a very broad scope range.
Could you double-check if any of those is the case?
If not, we’re happy to look into these specific grants to help with their cases specifically.
Our tool is not verified by Google, it hasn’t gone through the verification process. We’re adding the users as test users. The weird part is I have a Gmail account that’s connected and that doesn’t disconnect automatically, but other users we’ve added do get disconnected. In terms of broad scope range, we need to be able to read, write, and send emails because we need to be able to create draft emails (we don’t actually send them but there’s no separate permission for that).
The problem is that we are trying to validate and test our use case and functionality before going through the verification process. But it seems like unless we are verified, we can’t actually do that? Because test users get kicked out?
I’m new to Nylas and seem to be having the same issue - certain Gmail accounts being disconnected even though I have them set up as test users, while other Gmail accounts are staying connected just fine.
I’m assuming it has to do with the lack of verification of my app for now, but is there a way on the GCP side to prevent that from happening with dedicated test users? Not sure if I just have to contact Google or something.
Hello @bryson ,
This could be related to Google’s restrictions on unverified applications. Here’s a bit more detail on what might be happening and how to address it:
Why Some Users Disconnect
Unverified Google applications have a 100-user authentication limit over the app’s lifetime. Once this limit is reached, new users may be unable to authenticate, and existing connections can become unstable. The inconsistent behavior you’re seeing (some accounts staying connected while others disconnect) usually indicates the app is approaching or has exceeded this limit.
Next Steps
If you’d prefer not to go through the Google verification process, we also support a Shared Google Cloud Project option that’s already verified. This is available on certain plans — let us know if you’d like to explore that route, and we can loop in our Sales team to help set it up.
Let us know if you have any questions.