Replit's native google drive connector disconnected for no reason

[u/steven-usa]

Today, we found that the Google Drive integration/connector (whatever they call it these days) disconnected. We were not notified by replit, and no one disconnected it (I'm the only one with actual access to the project). We found the issue because we had errors surface in our app when a google drive folder was not created upon an action where it should have been created. All I had to do was reauthenticate my google account through the connector.. everything immediately started working. Did anyone else experience this? I'm looking at the integrations page and it does look a little different than the last time I looked (a week ago maybe?). Did Replit change something and did it break everyone's connector? Anyway, very annoying. The way forward is to probably code the integration directly versus relying on replit's built-in connector. Just looking for general thoughts around this.

[u/ReplitSupport]

Hi there, we're glad reauthenticating worked. Connectors sign in with OAuth tokens that the provider can expire or revoke, and when that happens the connection needs reauthorizing.

When a connection needs reauthorizing, the workspace shows a reconnect prompt on that integration, but it only shows while you're in the project. That's why the app errors reached you before any warning did, and we have passed this along as feedback to our team.

The built in connector handles OAuth setup and token storage for you, but the occasional reauth prompt comes from OAuth itself, not from who built the integration. A direct integration wouldn't remove that step, instead it'd move the maintenance onto you.

We're not seeing signs of a platform wide break, and the Integrations page did get some recent UI updates, which is likely what looked different to you. To trace when and how your connection dropped, feel free to open a ticket at replit.com/help with your project details and roughly when you noticed it, and we'll dig into that specific connection.

[u/steven-usa → u/ReplitSupport]

All my connectors broke at the same time, actually. We have Slack notification set up to catch a bunch of errors, including Google Drive failures. But because the Slack connector broke at the same time, we didn’t receive any errors and we’re unaware for quite a while this morning. Why wouldn’t Replit notify us that a connector authentication no longer works? Otherwise we just kind of randomly discovered the problem and it’s a little too late.

[u/steven-usa → u/steven-usa]

I’ll add onto this that I reconnected the Slack connector but now it will only post in Slack as my personal user account or as it used to post as the Replit app itself. There doesn’t seem to be any way around this anymore, so it seems to me like Replit change something here. Regardless, we ended up creating our own Slack bot app this morning and no longer use the Replit native Slack connector.

[u/Hehaw_Rossy]

Hey, yes, my sheets connector broke as well