Authentication().login goes to a background thread but doesn't bring back to main about auth0.swift HOT 3 CLOSED

What is your actual issue? That you want to update Ux on the main thread? In that case you should call the main thread inside your closure and this is your responsibility. If you want to see this in action, please take a look at the samples:

https://github.com/auth0-samples/auth0-ios-swift-sample

from auth0.swift.

No, I think you misunderstand, I am saying that if a method goes to the background thread it should either state it in its docs or bring you back to the main thread when it is done internally, I don't think the user should have to guess the thread the callback will be on?

from auth0.swift.

Network requests should be handled async as they should never block the main thread. Have a look at URLSession which is what our network layer uses. You will see the completion handler (callback) is scheduled on the delegate queue. So this is standard and expected behaviour, no need for us to document this.

In a callback the developer should only switch to the main thread when it is necessary to do so, typically Ux changes. Otherwise they run the risk of unnecessarily blocking the main thread, which goes against best practice.

from auth0.swift.