Most wellness apps break around midnight because nobody tests what happens when a third-party fitness API quietly revokes an old token. We spent three weeks building a step tracker integration before realizing our OAuth2 refresh flow swallowed error codes. Every time the access token expired after its standard validity window, the background sync job failed silently. Users opened dashboards to empty graphs and assumed the platform was broken.
The culprit was a mismatch between how the Fitbit authorization server signals an expired grant and how our Node.js backend caught exceptions. When an invalid token request hits their endpoint, it returns a precise status code along with a specific error body indicating the grant expired or got revoked entirely. Our initial error handler treated every 401 response as a simple signal to swap the refresh token for a new pair. But if a user revokes access from mobile privacy settings, or if the refresh token sits idle past its inactive expiration limit, that standard retry loop enters an infinite recursion of failed authorization attempts.
We fixed this by treating authentication state as a finite state machine rather than a simple database boolean. When a request returns an invalid grant error, the system must immediately invalidate the local session, flag the connection as severed, and trigger a friendly re-authentication prompt in the client interface. We wrote a lightweight middleware wrapper that intercepts outgoing API calls, checks local token timestamps, and preemptively refreshes credentials if they sit within a safety margin of expiration.
Here is a simplified pattern of how we structure that check before hitting provider endpoints:
async function ensureValidToken(userId) {
const tokenData = await database.getToken(userId);
const now = Date.now();
if (tokenData.expiresAt - now < 300000) {
try {
const freshTokens = await refreshFitbitToken(tokenData.refreshToken);
await database.saveToken(userId, freshTokens);
return freshTokens.accessToken;
} catch (error) {
if (error.code === 'invalid_grant') {
await database.clearToken(userId);
throw new AuthRevokedError('Please reconnect your fitness device.');
}
throw error;
}
}
return tokenData.accessToken;
}
Handling these edge cases changes how reliable your product feels. Users ignore OAuth specifications and grant types completely; they just want to see morning runs sync without opening developer tools. Build resilient boundaries around external APIs so your software feels like a dependable tool instead of a fragile script.
Top comments (0)