Migrate to short-term / refresh tokens
See original GitHub issueAs of September 2021, new apps created for Dropbox do not offer long-term token support. This blog post has more details, but essentially tokens must have an expiration date, and the app Oauth2 settings do not allow you to select “No expiration” anymore.
This results in the access tokens only lasting for a short amount of time (less than a day) before the git-remote-dropbox client throws an error when you try to interact with it:
Unable to refresh access token without refresh token and app key
Thus, anyone who has begun to using this tool after September 2021 must manually log in and retrieve a new generated access token every time their token expires, which is not ideal. It seems like git-remote-dropbox should either migrate to short-lived access tokens or refresh tokens, depending on what it is compatible with.
Issue Analytics
- State:
- Created 2 years ago
- Comments:23 (9 by maintainers)
Top GitHub Comments
Switching to the refresh token doesn’t invalidate the long-lived token, so if users are using that on another machine, it will continue to work.
Does
input()
break in the MINGW64 terminal in general? If it’s at least working in Git Bash (based on MSYS2, I think), then maybe you could just use Git Bash long enough for the migration and refresh token retrieval to work.