[GH-ISSUE #342] App got rejected by Apple #216

Closed
opened 2026-03-03 16:46:45 +03:00 by kerem · 1 comment
Owner

Originally created by @BirknerAlex on GitHub (Feb 27, 2017).
Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/342

Hello,

we've implemented this Library now into our new App Release. I've using OAuth 2 with auth code web flow.

OAuthSwift redirects the user into the Safari browser instead of using a Safari View Controller inside the App and that's it what Apple claimed while the app review.

Apple Review:

We noticed that the user is taken to Safari to sign in or register for an account, which provides a poor user experience.

Next Steps

Please revise your app to enable users to sign in or register for an account in the app.

We recommend implementing the Safari View Controller API to display web content within your app. The Safari View Controller allows the display of a URL and inspection of the certificate from an embedded browser in an app so that customers can verify the webpage URL and SSL certificate to confirm they are entering their sign in credentials into a legitimate page.

Is there any option to change it to this behavior? Did someone already get the same result in a Review?

Regards,
Alexander

Originally created by @BirknerAlex on GitHub (Feb 27, 2017). Original GitHub issue: https://github.com/OAuthSwift/OAuthSwift/issues/342 Hello, we've implemented this Library now into our new App Release. I've using OAuth 2 with auth code web flow. OAuthSwift redirects the user into the Safari browser instead of using a Safari View Controller inside the App and that's it what Apple claimed while the app review. Apple Review: > We noticed that the user is taken to Safari to sign in or register for an account, which provides a poor user experience. > > Next Steps > > Please revise your app to enable users to sign in or register for an account in the app. > > We recommend implementing the Safari View Controller API to display web content within your app. The Safari View Controller allows the display of a URL and inspection of the certificate from an embedded browser in an app so that customers can verify the webpage URL and SSL certificate to confirm they are entering their sign in credentials into a legitimate page. Is there any option to change it to this behavior? Did someone already get the same result in a Review? Regards, Alexander
kerem 2026-03-03 16:46:45 +03:00
  • closed this issue
  • added the
    question
    label
Author
Owner

@BirknerAlex commented on GitHub (Feb 27, 2017):

Nevermind, I've found the option to handle this.

if let oauthswift = AppState.oauthClient {
    oauthswift.authorizeURLHandler = SafariURLHandler(viewController: self, oauthSwift: oauthswift)
}
<!-- gh-comment-id:282676750 --> @BirknerAlex commented on GitHub (Feb 27, 2017): Nevermind, I've found the option to handle this. ``` if let oauthswift = AppState.oauthClient { oauthswift.authorizeURLHandler = SafariURLHandler(viewController: self, oauthSwift: oauthswift) } ```
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/OAuthSwift#216
No description provided.