The responses from EM above are not inspiring and if, as he suggests, v5 cannot be used in conjunction with previous versions then that's the final nail in the coffin for me and v5. 'Losing' a record has never happened to me before when using previous versions and has shaken my faith in a previously totally reliable product. Unlinking and re-linking to Dropbox has not worked (i.e. Turning off automatic sync and attempting to sync manually via the pull-down method is ineffective. The record was created on another iOS device using v4.5.4 and has evidently synced into Dropbox OK as it's present on all other instances apart from v5.6.0 on my phone.

The first sign of this was failing to find a record in v5 that I then found successfully in v4.5.4. I've recently been trying to use v5.6.0 on iOS (having quickly abandoned it on Mac for the usual reasons including low info display density and dropping Dropbox sync) and although after having initially got it to sync with Dropbox it now refuses to do so. I'm expecting to be redirected to localhost with query parameters containing an authorization code.ĭoes anyone know what I'm doing wrong? The behavior looks very similar to what's described in: Obtain OAuth2 Access Token for Dropbox Core API with Codenameone's Oauth2 Class, but there's no direct answer there.I'm a longtime user of mSecure on iOS, Mac and Windows.

There are also no query parameters on the redirected URL. The problem I'm seeing is that the API does not redirect the browser to the specified redirect URL ( After I provide my credentials and click Allow to grant access, instead of being redirected to localhost I'm redirected to, which fails to load (error 404).

The test code (roughly the same as ) is a simple dialog with an embedded browser control to display the API login page. I'm using DropNet as the client library and using the Token (implicit grant) flow option. I'm attempting to connect to the Dropbox API using OAuth2.

Www dropbox com iniciar connect