I’m working on developing an application that integrates with Google Drive and I need help with the app configuration settings. When users go to their Google Drive settings and look at the connected applications, they can see a checkbox that says “Use by default” next to my app.
I want to hide this checkbox completely so users don’t see this option at all. I noticed that some other apps like HelloFax don’t show this checkbox in their app settings.
I tried removing all the MIME types and file extensions from my app configuration, but then I get an error message. This makes me think that maybe the checkbox can only be hidden if the app doesn’t support creating new files.
Is there a specific setting in the Google Drive API configuration where I can control this behavior? Or does the visibility of this checkbox depend on what file operations my app supports?
The checkbox appears because your app is registered as a file creation handler in the Drive API settings. If your app declares the openWith or create intents, Google Drive will show that checkbox, allowing users to set your app as the default for particular file types. To avoid displaying the checkbox, you must ensure that your app only reads files or processes existing ones without indicating any file creation capability. However, if you received errors trying to remove MIME types completely, it suggests that creation functionality is integral to your app. Unfortunately, if your app needs this capability, there’s no way to hide the checkbox, as Google requires it for users to manage their default applications effectively.
You’re right - the checkbox shows up because your app can create files. I’ve run into this same problem before. The checkbox only appears when your Drive app declares creation intents in the manifest. Apps like HelloFax probably don’t have those creation capabilities defined, so no checkbox. If your app just views or processes files without creating new ones, the checkbox won’t show up. That error you got when removing MIME types means your current setup needs those declarations. I’d suggest changing your approach - maybe focus on modifying existing files instead of creating new ones, or build a workflow that doesn’t need the create intent. This way you’ll get rid of the checkbox naturally without messing with API settings.
Just dealt with this. the checkbox is tied to your app’s drive manifest config. When you register file handlers or set supported mime types for creation, Google automatically adds it. There’s no hidden setting to turn it off - it’s hardcoded. Only fix I found was restructuring my app to skip create intents completely, but that won’t work if you actually need file creation.