Bug: nothing happens when adding "drive" backend after authorizing rclone app in browser and returning to RSAF

[soredake]

After authorizing app in browser, I see this:

And after returning to app, I see this:

[chenxiaolong]

Thanks for reporting this. I'm able to reproduce this (sometimes).

The rclone authorization flow in RSAF is very finicky. It relies on parsing logs from rclone authorize because there's no other way to obtain the token after a successful login. The problem you're seeing is caused by a timing issue and happens if rclone logs the token after a short delay (instead of immediately).

I believe I found a decent way to fix this. I'll upload a test build shortly.

[chenxiaolong]

This should be fixed by #56. Please give this test build a try:

• arm64-v8a: https://files.pub.chiller3.com/issues/RSAF/issue55/RSAF-1.23.r2.g7e3c1e3-arm64-v8a-release.apk
• armeabi-v7a: https://files.pub.chiller3.com/issues/RSAF/issue55/RSAF-1.23.r2.g7e3c1e3-armeabi-v7a-release.apk
• x86: https://files.pub.chiller3.com/issues/RSAF/issue55/RSAF-1.23.r2.g7e3c1e3-x86-release.apk
• x86_64: https://files.pub.chiller3.com/issues/RSAF/issue55/RSAF-1.23.r2.g7e3c1e3-x86_64-release.apk

These are signed with the same key as the release builds. When you install it, it should update your existing RSAF app.

[soredake]

Yes, this pr fixes this problem, thank you!

[chenxiaolong]

Great, thanks for testing! I'll merge the PR and release a new version.