You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After calling authorizeFromControllerV2 and the user dismisses the authentication dialog, the openURL routine is called.
The issue I am having is that when that call to openURL is made, although the DBMobileSafariViewController dialog has been dismissed and is not visible the dismiss has not fully completed. A call to get the topController still returns the DBMobileSafariViewController.
Is it possible that when dismissing the DBMobileSafariViewController the callback to openURL is made in the completion block of the dismiss of the DBMobileSafariViewController.
This way within openURL a UIAlertController can be properly displayed if desired.
The text was updated successfully, but these errors were encountered:
Thank you Greg. Right now I have a workaround where I call dispatch_after on the main queue waiting 1 second and by then the Authorization screen is fully dismissed by then and I can display my UIAlertController. But for completeness when the call back is called the Authorization screen should already be fully dismissed.
After calling authorizeFromControllerV2 and the user dismisses the authentication dialog, the openURL routine is called.
The issue I am having is that when that call to openURL is made, although the DBMobileSafariViewController dialog has been dismissed and is not visible the dismiss has not fully completed. A call to get the topController still returns the DBMobileSafariViewController.
Is it possible that when dismissing the DBMobileSafariViewController the callback to openURL is made in the completion block of the dismiss of the DBMobileSafariViewController.
This way within openURL a UIAlertController can be properly displayed if desired.
The text was updated successfully, but these errors were encountered: