nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Child Item

DBClientsManager authorizeFromController after unlinkAndResetClients

Steve L.

I've found that calling DBClientsManager authorizeFromController after unlinkAndResetClients when using browser-based authentication results in an empty browser screen.

I don't think I'm doing anything unusual, just basically the following

    [DBClientsManager unlinkAndResetClients];

and some time later

    [DBClientsManager authorizeFromController:[UIApplication sharedApplication]
                                   controller:self
                                      openURL:^(NSURL *url) {
                                      [[UIApplication sharedApplication] openURL:url];
      }];

Note it works as expected if the Dropbox app is installed and when using the "in app browser authentication" that was available prior to ObjectiveDropboxOfficial 3.0.11.

I'd appreciated any insights as to what is happening and how I might resolve it.

Find more posts tagged with

API

Abuse

Accepted answers

Steve L.

In the end I worked around the problem. I can't definitely say it was in our code but I am working on the assumtion it was.

All comments

Greg-DB

Thanks for the report Steve. I just tried this though, and it's not reproducing for me. To help us track this down, please let me know:

- Are you seeing this on physical devices (if so, which) and/or the simulator?

- What version(s) of iOS are you seeing this with?

- Is there anything potentially intefering with your network connection to www.dropbox.com?

- Does the page reliably display properly if you don't call unlinkAndResetClients?

Thanks in advance!

Steve L.

Digging deeper, this only occurs if I invoke connect from deep in our view hierarchy and so is unlikely to be a general problem and quite possibly is application specific.

I'll keep investigating.

Steve L.

In the end I worked around the problem. I can't definitely say it was in our code but I am working on the assumtion it was.