5 ms·

> Create new Drive files, or modify existing files, that you open with an app or that the user shares with an app while using the Google Picker API or the app’s

> Create new Drive files, or modify existing files, that you open with an app or that the user shares with an app while using the Google Picker API or the app’s file picker. Yeah, this should do the trick. From the cursory look seems like there’s no Google Picker UI for Android though? Google actions are somewhat ridiculous here (they should audit iA’s app, not their cloud), but the reason is pretty solid IMO. If you choose an overly broad scope, be prepared for scrutiny.

Gigachad 2y ago
You don't need a google drive specific picker. Drive adds itself in to the OS file picker, on iOS at least. And that lets any app access any file without even using the drive api or having an api key. The key point is that iOS and Android control that access so the app can't open a file the user didn't select. If you want that functionality, you can do it easily for files the app created itself, or if you want access to literally everything without user oversight, you need a security audit.
- mvdtnz 2y ago
  This is the second time I have seen you in this thread talk about how the iOS picker behaves. This is irrelevant. We're not discussing iOS.
  - notpushkin 2y ago
    I’d expect something similar on Android actually – there is the relevant API at least.
  - consteval 2y ago
    It is relevant, because it demonstrates it's both possible and common. Therefore, complaints about this not working in Android speaks more to insufficiencies in the file picker, not true capabilities. A lot of people are arguing you need more powerful permissions due to hard requirements. Well, it's not a hard requirement in this case, it's a defect with the Android file picker and it should be fixed THERE. If the Android file picker does not currently work this way, which I bet it does.
- notpushkin 2y ago
  In some cases you might want to retain access to the file. I think the OS file picker doesn’t allow that while the Google Picker does.

Gigachad 2y ago

You don't need a google drive specific picker. Drive adds itself in to the OS file picker, on iOS at least. And that lets any app access any file without even using the drive api or having an api key. The key point is that iOS and Android control that access so the app can't open a file the user didn't select. If you want that functionality, you can do it easily for files the app created itself, or if you want access to literally everything without user oversight, you need a security audit.

mvdtnz 2y ago
This is the second time I have seen you in this thread talk about how the iOS picker behaves. This is irrelevant. We're not discussing iOS.
- notpushkin 2y ago
  I’d expect something similar on Android actually – there is the relevant API at least.
- consteval 2y ago
  It is relevant, because it demonstrates it's both possible and common. Therefore, complaints about this not working in Android speaks more to insufficiencies in the file picker, not true capabilities. A lot of people are arguing you need more powerful permissions due to hard requirements. Well, it's not a hard requirement in this case, it's a defect with the Android file picker and it should be fixed THERE. If the Android file picker does not currently work this way, which I bet it does.
notpushkin 2y ago
In some cases you might want to retain access to the file. I think the OS file picker doesn’t allow that while the Google Picker does.