Dropbox com.android.packageinstaller.InstallAppProgress has leaked IntentReceiver

My apologies for any offense or miscommunication here. Like you, we want to make sure the best content and answers are available to other developers. We agree that having the user re-authorize the app is a bad experience but it seems the confusion here is around the notion that re-authing the user (via startOAuth2Authentication) is necessary, when in fact it isn't. As Steve was trying to point out with his comment, you only need to have the user authorize the app once, after which you can store and re-use the resulting access token. This is covered in the tutorial here:

https://www.dropbox.com/developers/core/start/android#authenticating

Only if the user explicitly unlinks the app do you need to prompt them to re-authorize. If they do unlink the app, API calls with the old access token will fail with DropboxUnlinkedException, documented here:

https://www.dropbox.com/static/developers/dropbox-android-sdk-1.6.3-docs/com/dropbox/client2/exception/DropboxUnlinkedException.html

Likewise, this can occur if you restart a previously authorized app but don't load up the previously acquired access token. You can create a session using a previously stored access token without having the user re-authorize the app using this constructor:

https://www.dropbox.com/static/developers/dropbox-android-sdk-1.6.3-docs/com/dropbox/client2/android/AndroidAuthSession.html#AndroidAuthSession(com.dropbox.client2.session.AppKeyPair,%20java.lang.String)

I hope this helps!