Both of remote backup options doesn't work (Google Drive and Dropbox)

[xscd]

Currently both of the remote backup options doesn't work.

Description

Google Drive tells that the browser which Zap opens is insecure and unsupported. Dropbox has suspended activity of Zap and needs a manual review.

Expected Behavior

Both remote backup options should work.

Actual Behavior

Both remote backup options doesn't work.

Drive:

Dropbox:

Possible Fix

Drive recommends this: https://support.google.com/accounts/answer/7675428

Dropbox, no idea probably contacting them as Zap?

Steps to Reproduce

• 1. Create new waller
• 2. Select Drive or Dropbox as remote backup option
• 3. Try to enter login credentials
• 4. Good Luck!

Context

I want my channel state backups in remote. I don't trust my HDD since it makes weird noises and will probably fail soon. I can't currently use the wallet.

Your Environment

I use Linux and the AppImage edition (don't know if there are any *.deb which wouldn't work anyway because I don't use Debian or Ubuntu anyway)

• Zap version: Zap-linux-x86_64-v0.6.2-beta.AppImage
• Operating System and version: Void Linux x86_64

[welcome]

👋 Thanks for opening your first issue here! If you're reporting a 🐞 bug, please make sure you include steps to reproduce it.
To help make it easier for us to investigate your issue, please follow the contributing guidelines.

[bolatovumar]

Looks like Dropbox has a guide about this issue here: https://www.dropbox.com/developers/reference/developer-guide#production-approval

[bolatovumar]

Tried it as well and getting the same error:

I managed to get the Dropbox backup working by creating my own app in Dropbox and replacing the Dropbox clientId in default.js with my newly created app's id. Looks like the existing Zap Dropbox and GDrive apps just need to be renewed or something. Ping @korhaliv @mrfelton @JimmyMow.

[mrfelton]

The issue with dropbox is resolved and should be working with the 0.6.2 release.

The issue with Google has also been resolved but will not work with the 0.6.2 release. The fix for this will be included in our next release.