One more thing. I noticed that my tokens didn't refreshed automatically (expired after 6 hours because renew-token wasn't generated with above command). Above command works perfectly only if i manually add: &token_access_type=offline at the end of a Auth2 Dropbox URL.
It's possible to add &token_access_type=offline to command that i don't need to add it manually?
You shouldn't need the --dropbox-client-secret and --dropbox-client-id flags when doing this.
When I tried this with a normal client-id and client-secret it worked fine, and also when I tried it with an app client I created it worked fine too.
$ rclone config create dropboxapp dropbox client_id=XXX client_secret=YYY
2022/06/29 10:18:17 NOTICE: Make sure your Redirect URL is set to "http://localhost:53682/" in your custom config.
2022/06/29 10:18:17 NOTICE: If your browser doesn't open automatically go to the following link: http://127.0.0.1:53682/auth?state=7mWvFx23hQfIzD_yu1ZpQQ
2022/06/29 10:18:17 NOTICE: Log in and authorize rclone for access
2022/06/29 10:18:17 NOTICE: Waiting for code...
2022/06/29 10:18:28 NOTICE: Got code
[dropboxapp]
type = dropbox
client_secret = XXX
client_id = YYY
token = {"access_token":"XXX", "token_type":"bearer","refresh_token":"YYY","expiry":"2022-06-29T14:18:29.27704262+01:00"}
$ rclone lsf dropboxapp:
# no files seen as it is the app
So I think you've probably not quite ticked enough buttons on the dropbox app config page