magic-js: React-Native iOS app rejected(Guideline 4.0 - Design) on AppStore for using @magic-sdk/react-native
✅ Prerequisites
- [yes] Did you perform a cursory search of open issues? Is this bug already reported elsewhere?
- [yes] Are you running the latest SDK version?
- [yes] Are you reporting to the correct repository (
magic-sdk)?
🐛 Description
IOS app rejected by AppStore with “Guideline 4.0 - Design”
Rejection Reason provided by app store:
Guideline 4.0 - Design We noticed that the user is taken to the default web browser to sign in or register for an account, which provides a poor user experience. Next Steps To resolve this issue, please revise your app to enable users to sign in or register for an account in the app. You may also choose to implement 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.
🧩 Steps to Reproduce
Publishing App to AppStore
🤔 Expected behavior
[What you expected to happen?]
😮 Actual behavior
[What actually happened? Please include any error stack traces you encounter.]
💻 Code Sample
[If possible, please provide a code repository, gist, code snippet or sample files to reproduce the issue.]
🌎 Environment
| Software | Version(s) |
|---|---|
magic-sdk |
|
| Browser | |
yarn |
|
| Operating System |
About this issue
- Original URL
- State: closed
- Created a year ago
- Comments: 17 (8 by maintainers)
@betashop Hi again, I was referring to this feature in our docs.
If you pass
showUI = falseintologinWithMagicLink, you can render your own modal informing the end user to check their inbox, instead of seeing Magic’s branded modal. Our popup modal that appears after the user submits their email address is web view. But if you created your own modal you wouldn’t render a web view to the end user.We are working on having this available for the other email login method
loginWithEmailOTP. It is currently in development.Yes, you should proceed with confidence. We haven’t seen this issue crop up more than once. Although, I can’t promise anything as things are constantly changing with Apple’s review process. Please do let us know if you run into issues.
We are not doing social login, we are using loginwithlink and they complaining about attached screen and asking us to show url/certificate so user know where they are entering email id. app store is saying to not use web view and use safari view for this with url and certificate should present in header.
Hi @Ariflo ,
I have attempted to resolve the issue by implementing the new split package, but unfortunately, app has been rejected by the App Store due to non-compliance with guideline 4. The reason cited was the usage of webview, which needs to be shown through the Safari view with the URL and its certificate so user know where they are inputing their email id.
I wanted to bring to your attention that this issue has also been faced by the Auth0 Library, as referenced in the following community post: https://community.auth0.com/t/react-native-ios-app-rejected-on-appstore-for-using-react-native-auth0/36793
Thank you for your time and consideration. I am looking forward to your response.