You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 13, 2025. It is now read-only.
Based on the intended use-case of the app, I suspect you only need to use the "photoslibrary.appendonly" scope (and maybe the "photoslibrary.readonly.appcreateddata" scope to read files that the app has uploaded.)
However, I see the app is requesting essentially full read/write rights of my google photos via the "photoslibrary" scope.
The only reason I can figure for this is that the app wants to check to see if an album exists already before creating a new one. Personally, I'd prefer to not have that particular feature in order to have the app have narrower access to my photos account.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Based on the intended use-case of the app, I suspect you only need to use the "photoslibrary.appendonly" scope (and maybe the "photoslibrary.readonly.appcreateddata" scope to read files that the app has uploaded.)
However, I see the app is requesting essentially full read/write rights of my google photos via the "photoslibrary" scope.
The only reason I can figure for this is that the app wants to check to see if an album exists already before creating a new one. Personally, I'd prefer to not have that particular feature in order to have the app have narrower access to my photos account.
The text was updated successfully, but these errors were encountered: