Hi, I'm building a MacOS app that will be published outside of the AppStore (Using an installer). In the app we have an option to sign-in with Apple & Google. While trying to archive the app and distribute with a Developer ID, xcode presented us with this error, and once the entitlements were removed the sign-in with Apple/Google stopped working. Is there a way to archive the app and distribute with Developer ID and also support sign-in with Apple/Google? Thanks!

Can we remove apple sign in /signup option from iOS and can only have signup with email id

When the user's identity (sub) is changed when the app is migrated. When the migration is initiated, it is still when the receiving team confirms. In addition, when can the Exchange identifiers endpoint be used?

Subject: Request for Resolution on Guideline 4.0 - Design: Null Display Name Issue with AppleAuth Provider by Firebase in React Native App Dear Apple App Review Team, I am writing to express my concern and seek assistance regarding the rejection of my React Native app from being published on the Apple App Store. The rejection reason cited is Guideline 4.0 - Design, specifically stating that my app requires users to provide their name and/or email address after using Sign in with Apple. Additionally, there is a null display name issue from the AppleAuth provider by Firebase. I want to assure you that I have made every effort to comply with Apple's guidelines and provide a seamless user experience. However, it appears there may be a misunderstanding or miscommunication regarding the implementation of the name and email address requirement as well as the null display name issue. Regarding the name and email address requirement: My app integrates Firebase's AppleAuth provider to facilitate Sign in with Apple. During the authentication process, the necessary permissions and scopes are requested to retrieve the user's name and email address from Apple. The obtained name and email address are stored securely within my app, eliminating the need for users to provide this information separately after using Sign in with Apple. Regarding the null display name issue: Upon thorough testing, I have identified a problem where the display name returned from the AppleAuth provider by Firebase occasionally appears as null. This issue is unexpected and unintended, as the display name should be populated correctly based on the information retrieved from Apple during the authentication process. I have reviewed my code and integration with Firebase, following all the guidelines and recommendations provided by Apple and Firebase documentation. I kindly request your guidance and assistance in resolving both the name and email address requirement misunderstanding and the null display name issue from the AppleAuth provider by Firebase. I am committed to rectifying these issues promptly to ensure compliance with Apple's guidelines and provide an optimal user experience. Thank you for your attention to this matter. I eagerly await your response and guidance on how to address the Guideline 4.0 rejection and the null display name issue effectively. Please feel free to reach out to me if you require any additional information or have further questions. Sincerely, dev nihar

Null Display Name Issue with AppleAuth Provider on Firebase using react native Dear Apple App Review Team, I have been diligently working on my app, which heavily relies on Firebase for authentication purposes. Specifically, I am utilizing the AppleAuth provider to offer seamless authentication options to my users. However, during the review process, it came to my attention that the display name from the AppleAuth provider is being returned as null. This issue is concerning, as it directly affects the user experience and functionality of my app. It prevents users from being able to see their display name correctly, which can lead to confusion and frustration. Moreover, it undermines the trust and reliability of the app, which I have worked hard to establish. I have thoroughly reviewed my code and integration with Firebase, and I can confirm that I have followed all the necessary guidelines and recommendations provided by Apple and Firebase documentation. The null display name issue appears to be an unexpected and unintended consequence. To rectify this problem, I kindly request the assistance and guidance of the Apple App Review Team. I would greatly appreciate it if you could provide me with specific instructions or steps to resolve the null display name issue with the AppleAuth provider on Firebase. I understand the importance of maintaining high-quality standards on the Apple App Store, and I am fully committed to resolving this issue promptly. I value the collaborative relationship between developers and the Apple App Review Team and believe that by working together, we can ensure the best possible experience for our users. Thank you very much for your attention to this matter. I look forward to your prompt response and guidance on how to handle this issue effectively. Please feel free to contact me if you require any additional information or have any further

Hi there, when using Touch ID, the call back following a request to auth/authorize does not include any user information ( user={} ), but it does if the user log in using a password. Is there a reason ? How to handle that Thanks

I push a new application to store. ;When i try to log in with FaceId, i get an error like this "Sign up not completed". what am i missing? could you help pls :) you can access the app from https://apps.apple.com/tr/app/lone/id6447771266?l=tr

Hello, I have multiple apps that i would like to login with apple login connected to same backend. I enabled sign in with apple on all and told them to "group with primary app id" which is one of them. I went and created 1 service id and key and used that on the backend to login the user. I can login fine on the primary app id but not on the grouped ones. Am I missing anything setup wise?

Maximum number of apps have been associated to this primary app. Max limit: '5'We want to add a lot more Secondary Suite of Apps to a Primary Authentication app. Please help us on the limit 5 and is it possible to increase this limit?

Hello, I have transfer app to another account but i not change bundle id of app. ASAuthorizationAppleIDCredential identity token generate by bundle id and team id associated apple developer account. Could you let me know identity token changes if the bundle ID remains unchanged?

Hello, We are experiencing difficulties integrating the Apple Sign-In provider. Our third-party service is unable to forward emails to the private address @privaterelay.appleid.com. I received a "hard debounce" error. We have configured the following on Apple: DKIM is OK - Our email signature is using our domain. We are unsure what else to do. Could you please assist us?

Hi. I transfered an app that uses apple login. but, I didn't do the Transferring your apps and users to another team process, So, I'm working on Bringing new apps and users into your team. Is it possible to transfer a user with just Bringing new apps and users into your team.? I'm having trouble with the part where I get the access_token from the Bringing new apps and users into your team. action. I've only entered it with the NEW TEAM's information. POST /auth/token HTTP/1.1 Host: appleid.apple.com Content-Type: application/x-www-form-urlencoded grant_type=client_credentials&scope=user.migration&client_id={client_id}&client_secret={client_secret} client_id : APP bundle ID client_secret : Created by referencing [Create the client secret] in Generate and validate tokens. require 'jwt' key_file = 'key.p8' team_id = 'TeamID' client_id = 'AppID' key_id = 'KeyID' ecdsa_key = OpenSSL::PKey::EC.new IO.read key_file headers = { 'kid' => key_id } claims = { 'iss' => team_id, 'iat' => Time.now.to_i, 'exp' => Time.now.to_i + 86400*180, 'aud' => 'https://appleid.apple.com', 'sub' => client_id, } token = JWT.encode claims, ecdsa_key, 'ES256', headers puts token POST /auth/token HTTP/1.1 Host: appleid.apple.com Content-Type: application/x-www-form-urlencoded grant_type=client_credentials&scope=user.migration&client_id={client_id}&client_secret={client_secret} { "error": "invalid_client" } Thank you.

I follow the below link to set up an apple login. https://developer.apple.com/documentation/sign_in_with_apple/sign_in_with_apple_js/configuring_your_webpage_for_sign_in_with_apple I configured - AppleID.auth.init({ clientId: 'tech.onetable.onetableadmin', scope: 'name email', redirectURI: 'https://local.test:5000/api/apple_auth', state: 'lilylsunisabigsb', usePopup: true, }) The process stuck at the page below, both "cancel" and "continue" buttons are not reponsive, there is a error saying " Your request could not be completed because of an error. Please try again later.". I checked the console of this popup window, it shows an error saying "POST https://appleid.apple.com/appleauth/auth/oauth/authorize 403"

I'm integrating the social login using apple sdk on my site Actually our login flow require the apple id popup solution to prevent user get out site, actually Im using this configurations on init: Init code: window.AppleID.auth.init({ clientId : 'example.client.id', scope : 'name email', redirectURI : 'https://mtest.thecompleteuniversityguide.co.uk', state: "origin:web", usePopup : true }) APP URL : https://mtest.thecompleteuniversityguide.co.uk/log-in Login code: async function appleSignIn() { try { const result = await window.AppleID.auth.signIn(); console.log("result: ", result); // Handle successful response. //applesocialsignsucess(data); } catch ( error ) { // Handle error. console.log("Error", error); } } document.addEventListener('AppleIDSignInOnSuccess', (event) => { // Handle successful response. console.log("Successfully Login "+event.detail.data); }); document.addEventListener('AppleIDSignInOnFailure', (event) => { // Handle error. console.log("Error "+event.detail.data); alert("Error "+event); }); THE PROBLEM IS: When the popup is opened and the apple id and password are correctly entered, the promise is not returned. When the cancel button is pressed, the popup does not close and no error is generated. The error is only called when the popup is closed using the navigation button. I require assistance; what are the issues with implementation?

Hello, I'm trying to renew my Appstore Connect subscription but unfortunately I'm facing problems. Our Account Holder ID is locked and when he tries to log in an error message keeps showing up saying "This Apple ID has been Locked. Contact your Administrator or Manager to reset your password and unlock your account." whose the admin or manager in this case? I contacted the support multiple times and they referred me to this link. https://support.apple.com/en-us/HT201487 We tried these steps but sadly no luck. whenever he tries to change the password an error message keep popping up saying "Need to reset your password? Contact your organization’s Administrator or Manager and ask them to reset the password for your Managed Apple ID"

Apple ID Good morning! We have a published App. We are trying to update. We do not change anything in the existing login process in the app that is already published. However, we are being refused by requesting the user's email when he logs in by Apple ID. In our App, our customers can register any email they want and not just their Apple ID email. How can we go about approving the update of our App that already works this way in the Apple Store?

I know that "Sign in with Apple" option is required for any app that offers other social logins like Facebook when submitting to the app store. I can't find out, though, if offering "Sign in with Apple" is required just to do a TestFlight beta for an app that isn't yet in the app store. Is it required?