funny0facer
funny0facer
I can confirm. Without this patch, I was not able to build it on Arch Linux.
did you read and follow this information: https://github.com/vitalif/grive2#different-oauth2-client-to-workaround-over-quota-and-google-approval-issues ?
The steps seem to have changed, but I did not have any problem to create a new token. Here are the steps I did in form of pictures: 
you have to provide values for --id and --secret. Then click on the link and approve the access. You might need to click on "advanced" or "extended". My german screenshot...
you do not need to rename the actual binary. I just created a new project and changed to the new layout to check what might gone wrong on your side....
Congratulations, sounds great! I did not have an issue on firefox to authenticate, but yes, maybe an addon.
> Here's the underlying Qt bug: https://bugreports.qt.io/browse/QTBUG-86407 Are you sure? If I am not mistaken, the referenced bug was fixed in 6.7 in march ( https://codereview.qt-project.org/c/qt/qtbase/+/546540 ). 6.7.1 fixed the...
In general, packaging requests should be sent to the distro, not to an upstream project.
did you read https://github.com/vitalif/grive2/issues/404 and follow the steps there?