I am implementing Sign in with Apple using the JS framework.When the user (me, right now) signs in for the first time, I get data I need!The parameters look like thisParameters:{"state"=>"[state]", "code"=>"[code]", "id_token"=> "[jws token]", "user"=>"{\"email\":\"[the email I need]\"}"}My scope is just "email," I don't need (or want) their name.Next, I try signing in again (same everything)But, I get this optionWhen I click "continue" the data looks like thisParameters:{"state"=>"[state]", "code"=>"[code]", "id_token"=> "[id token]"}As you can tell, there is no user object, no email, nothing I can use!If I do the code response and get an access token, I can't use it. There's no public, known endpoints to just get the email they used. There's no point in storing the email if I can never check for it the next time they sign in.This is happening on multiple browsers on macOS 10.14.4.On my iPhone running iOS 13 developer beta 3, every time I click the button, I get the option to "share" or "hide" my email (even though, as shown above, I've sign in before), and sharing the email actually shares it, while hiding it.. well hides it.However, the user data is always there.This bug(?) only appears when clicking Continue, which I can assume appears on devices that aren't running iOS 13. It's quite a problem on devices that aren't this small set of devices, so I hope this is either known, easily fixable, or something! Thanks for any help you can provide.

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?

I saw the descriptionYou may verify the refresh token up to once a day to confirm that the user’s Apple ID on that device is still in good standing with Apple’s servers.in https://developer.apple.com/documentation/signinwithapplerestapi/verifying_a_user .I have two question about the description:Why should we verify the refresh token instead of access token to confirm the user's Apple ID is still in good standing with Apple's server?The doc said refresh token can only verify once a day. But i can verify refresh token multiple times in practice. Is there some conflict between documentation and implementation?https://www.dropbox.com/s/l6ncxxvumil6sfs/1571217862017.png?dl=0Update on 10/17/2019:For apps running on other systems, use the periodic successful verification of the refresh token to determine the lifetime of the user session.I also saw the description above in in https://developer.apple.com/documentation/signinwithapplerestapi/verifying_a_user . I think periodic is also conflict with once a day.

We've implementing SIWA on iOS and a web application using Sign in with Apple JS. I've setup a service ID tied to the application ID and can succesfully get callbacks on both platforms. I'm noticing that the user id provided by the iOS app is different than the id provided by the web application.We were expecting these to be different so we can store on our end and identify the user without having to use their email.

All app icon sizes are correct in assets catalog, but app icon does not appear under Apps Using Apple ID in device settings. Is there another place to set app icon for sign in with apple?Thanks.

We’re not receiving email claim in the id token on the initial authorization request with Sign in with Apple API.We faced this issue just 3 times, on 2 different apps with 2 different bundle IDs. This is not a persistent issue, most of the time it works fine.Is the email always in the id token? What are the cases in which the email isn't there?

I'm integrating the social login using apple sdk on a big brazilian e-commerce.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', redirectURI: 'https://www.oursite.com.br/login/callback', usePopup: true, })The app url is: https://www.oursite.com.br/loginobs: url is an example.Login code:try { const data = await AppleID.auth.signIn() return data //doest receive } catch (error) { console.error({error}) }THE PROBLEM IS:When popup is opened and appleid and password is correctly submit, the popup does`t retuns the promise.When cancel button is trigger the popup does`t close and error is not calledJust when popup is closed by navigation button the error is calledI need help, whats the problems on implementation?

When I use the Generate and Validate Tokens endpoint - https://developer.apple.com/documentation/sign_in_with_apple/generate_and_validate_tokens with an Authorization Grant Code, the endpoint returns a refresh_token and id_token among other things. When the id_token expires, I can use the refresh_token to create a new one. However, when I use the refresh token on this endpoint, it doesn't return a new refresh_token. Why is that?

In the following environment: iOS 14 beta, Xcode Version 12.0 beta 6 (12A8189n) try to implement user Apple Login with Firebase. Works until password entering screen and then hangs up on simulator or finished with error on device. Sign In with Apple is enabled in App.

We have changed return URLs for one Service ID, but the change is not propagated. The old return URL still works and we get "Invalid web redirect URL". We even tried deleting Service ID with old return URLs and created new Service ID with new redirect URLs. But the only one that works is the one that we deleted.

Is it possible to change one's Apple ID yet retain all information and data associated with the former identity?

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?

Something seems to be wrong in the Apple Sign In modal. After pressing the Continue button and going through Face ID, it displays Sign Up Not Completed and does not proceed. This was working fine a few days ago, but then I had to download a new provisioning profile and now it is broken. There are no errors in the log when this happens, but when I close the sign in modal it logs: [core] Authorization failed: Error Domain=AKAuthenticationError Code=-7003 "(null)" The operation couldn’t be completed. (com.apple.AuthenticationServices.AuthorizationError error 1001.) Please help! I even spun up a fresh new project and made new ID / Provisioning profile and this error is still happening. Thanks!