ITUNES ACCOUNT LOGIN CODE

As the name suggests, we use Internal to distribute the app internally for testing purposes. Each of these configurations has different bundle ID and App ID in the Apple Developer Portal.

In our Xcode project we have 3 different build configurations: Debug, Internal and App Store. That was pretty easy, but we know that things are often more complicated than they might appear. This is what is needed by the backend to verify the user identity with the Apple server. We added the Sign in with Apple capability using Xcode and then got the private key and the Key ID from the Certificates, Identifiers & Profiles section of our account in the Apple Developer Portal. The setup of certificates and app capabilities always sounds difficult, but that is the first necessary step in the Sign in with Apple implementation journey. Apple suggests using the user property as a unique identifier in your server rather than the email, as there are some cases where the app only gets the identifier back in the response that the server can use to match to an existing account. Together with the email, Apple provides a user identifier which is unique for all apps written by a single development team. Users have the same proxy email in all the apps that belong to the same Development Team. In this case, Apple provides a proxy email to the app ( that can be used to get in touch with the user. One of the features of Sign in with Apple is the ability for the user to not share their real email. There you can find some really good conversations with Apple engineers explaining some edge cases of Sign in with Apple that arenвЂ™t well documented anywhere else.

An example code with a Sign in with Apple implementation by AppleДЄnother good source of information that helped us to understand some edge cases was the Apple Developer Forum.

вЂњWhatвЂ™s New in AuthenticationвЂќ session from WWDC 2019.

вЂњIntroducing Sign In with AppleвЂќ session from WWDC 2019.

The initial deep diveД®ven if Sign in with Apple might appear easy to understand at first, it is important to read carefully the documentation and get a clear idea of how both the authentication flow and the integration between the app, the backend and Apple work. This is what we learned along the journey about implementing Sign in with Apple.

Moreover, we refactored our code on iOS in order to integrate Sign in with Apple with the existing social providers and the native login. The documentation was a good starting point but we faced some edge cases that may prevent the user to log in if not handled properly. Instead, we took it as an opportunity to provide a more secure and easy way to log in for our customers around the world.ДЇor my team ( Identity&Protection) it was the first time we implemented an Apple feature which was brand new for everyone. Following the App Store Guidelines, this new feature is a requirement for all apps that support social logins (with some exceptions).ДЄt Just Eat we didnвЂ™t see Sign in with Apple as a required feature we needed to implement. At WWDC 2019, Sign in with Apple was introduced as a new way for apps to authenticate users with their Apple ID in a few steps.

ITUNES ACCOUNT LOGIN CODE

Itunes account login