I built a .NET application using the DrEdit sample code and deployed it for my test user group through the Chrome Web Store. Every single time I launch the application, it shows a permission dialog saying the app wants to request access to my Google Drive data.
I’m not sure if this is normal behavior for Google Drive apps or if there’s something wrong with how I configured the authorization in my .NET code. Has anyone experienced similar permission requests that keep showing up? Should the app remember the permissions after the first approval, or is it supposed to ask every time?
Any guidance on whether this is standard functionality or indicates a problem with my implementation would be really helpful.
Been there with Google Drive integrations. Token storage is a nightmare, but there’s an easier way.
Skip the .NET token management headaches. Set up an automation flow that handles Google auth once and manages everything through API calls.
I’ve done similar integrations where the permission dance made users want to quit. Moving Google Drive ops to an automation platform saved my sanity. It handles OAuth properly and gives your .NET app clean webhooks.
Your app hits the automation service, which already has persistent Drive access. No permission popups, no debugging refresh tokens.
The flow processes Drive operations and sends results back. Way cleaner than wrestling with Google’s OAuth in your code.
Latenode works great for this. Handles the Google Drive auth mess and gives you reliable endpoints: https://latenode.com
Yes, this sounds like a token persistence issue. I faced the same problem when I first deployed my Google Drive application. It seems like your application is treating each session as new and losing stored credentials every time it launches. To resolve this, I recommend using Google’s UserCredential class with a file-based token store. Ensure that the token store path remains consistent across restarts and that your application has permission to read and write to that location. Additionally, verify your OAuth consent screen in the Google Cloud Console; if it remains in testing mode, it may lead to unusual authorization problems. Getting your app verified and published can help it function beyond your test group.
sounds like ur auth creds aren’t saved right. i had that too - my app lost tokens from session to session. ensure u save them somewhere persistent, not just in memory. that fixed my issue. it shouldn’t ask every time after the 1st approval.
The repetitive permission requests you’re encountering likely stem from how the authorization tokens are being handled in your application. Ideally, Google Drive apps should ask for permissions only once and store the refresh token, which allows subsequent access without prompting the user again. Based on my experience with the Google Drive API in .NET, it sounds like your application may not be saving the authentication tokens properly. When you authenticate, you receive an access token that quickly expires and a refresh token that you must store. Make sure to persist the refresh token, whether it’s in a file, database, or registry, rather than just in memory, as I did initially. This change should resolve the issue and stop the permission prompts from appearing each time.