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

Why was DBClientsManager authorizeFromController browserAuth removed in a point release?

Steve L.

This is going to sound like criticism, and I guess it is, but please bear with me. The criticism is intended to be constructive and professional, not personal.

In the dropbox-sdk-obj-c GitHub project

Commit https://github.com/dropbox/dropbox-sdk-obj-c/commit/8936d7fc0be220e4cb1664b17ea6829044230a52 on April 12 removed the browserAuth option, thus removing the option of an In-app auth. I cannot find any discussion or rationale for this change in the Dropbox developer forums nor in the GitHub issues.

Suffice to say I relied on this functionality.

Do you believe it is acceptable to lose API functionality in a point release without fair warning and with no rationale or documentation? As pointed out in another forum thread, the change wasn't even documented.

There are many of us desperately trying to get our apps converted before the V1 switch off. An unstable API is not making it easier.

If there is a good reason for removing the functionality please document it. If not, please restore it ASAP and *please* stop making breaking API changes in point releases.

Find more posts tagged with

API

Abuse

Comments

Steve L.

By the way, the documentation at https://github.com/dropbox/dropbox-sdk-obj-c#handling-the-authorization-flow still refers to the in-app web view authentication flow.

Greg-DB

Thanks for the feedback Steve. We unfortunately had to remove this functionality in order to support users using the Google Sign In flow to sign in to Dropbox when authorizing a Dropbox API app. Google is dropping support for processing their OAuth flow in web views. We do have information about this in the release notes for 3.0.11.

And thanks for pointing out the outdated documentation. The "web view" there is now referring to the SFSafariViewController. I'll ask the team to update that.

Steve L.

I guess you're hands are tied if Google has made the change. I'll investigate adjusting the browser chrome to better simulate the in-app web view.