I’m facing a confusing issue when trying to use a Google Drive application with multiple Google accounts in the same browser. The problem seems to be with how Chrome Web Store handles app installations versus how the Drive API recognizes them.
The Issue:
When I install a Drive app through Chrome Web Store while logged in as User A, everything works fine. But when I switch to User B in the same browser, the Drive API says the app isn’t installed for that user. However, if I go back to Chrome Web Store, it shows the app as already installed.
Current Workaround:
The only solution I’ve found is to first uninstall the app while logged in as User B, then reinstall it again. This forces the Drive API to recognize the app for the second user. But this creates a really confusing user experience because the Web Store and the app give conflicting messages about installation status.
Question:
Is there a better way to handle Chrome Web Store app installations so they work properly with Google Drive API for multiple accounts in the same browser? This seems like a fundamental usability problem that many users would encounter.
This happens because Chrome Web Store apps install to the browser, but Google Drive API permissions stick to individual accounts. Install as User A? The browser gets the app, but only User A gets API access. I’ve dealt with this a lot in multi-account setups - that uninstall/reinstall workaround you mentioned is still the most reliable fix. Google hasn’t figured out how to make their APIs play nice with multiple accounts yet. Try using separate browser profiles for different accounts instead. Each profile keeps its own app installs and permissions, so you won’t run into these conflicts.
Been there. This account switching mess happens because Google’s systems don’t talk to each other properly.
Ditch the manual install dance. Set up automation that handles Drive API authentication for each account programmatically.
I built a workflow that authenticates users through OAuth directly with Drive API - skips the Chrome Web Store entirely. When someone needs access, the system walks them through proper API authorization for their specific account. No more browser vs account permission conflicts.
The automation handles token management, refreshes expired auths, and provisions new users automatically. Takes 30 minutes to set up but saves hours of uninstall/reinstall headaches.
Don’t fight Google’s broken architecture - automate around it. Much cleaner and your users get a smooth experience regardless of which account they’re using.
I’ve been fighting this same issue for months at work. The problem is how Google handles auth scope inheritance between browser sessions and account permissions. Chrome Web Store installs create browser-level registration, but Drive API needs per-account tokens that don’t auto-propagate. Skip the uninstall/reinstall nightmare - go straight to each user’s Google Account settings instead. Hit Security > Third-party apps with account access and manually grant permissions there. This dodges the Web Store mess completely and gets proper API access without reinstalling constantly. Takes longer upfront but kills the endless reinstall loop.
yup, totally get it! chrome is like, “we got this for everyone!” but then the api’s like, “nah, just for u.” it’s a pain. ur workaround seems to be the best bet for now.