Post not yet marked as solved
Hey,
any updates on this? Is it still happening for your app? Since the release of iOS17 some weeks ago our monitoring shows also a lot of failing requests for initial product loadings for iOS17 only - none of the current iOS updates has fixed this. I already opened a Ticket for this.
https://feedbackassistant.apple.com/feedback/13232149
Hey,i can confirm that we at Yazio have the same Issue and our Support gets a lot of Messages regarding this bug. We have not changed the Sign in with Apple code since a while and have the exact same feeling that this started on all Watch Series when WatchOS 6.1.3 was released.The support team is doing the same and telling the customers to unpair and pair their watch.BestSebastian
Post not yet marked as solved
Get the ASAuthorizationAppleIDCredential from the delegate// ASAuthorizationControllerDelegate
publicfunc authorizationController(controller: ASAuthorizationController,
didCompleteWithAuthorization authorization: ASAuthorization){
...
}Get the String encoded JWT from the credential:String(data: credential.identityToken, encoding: .utf8)Go to https://jwt.io and decode the JWT// Header
{
"kid": "eXaunmL",
"alg": "RS256"
}
// Payload
{
"iss": "https://appleid.apple.com",
"aud": "***",
"exp": 1581598403,
"iat": 1581597803,
"sub": "***",
"c_hash": "***",
"email": "***",
"email_verified": "true",
"auth_time": 1581597803
}In the header you can see the "kid".This kid will match with one of the kid from https://appleid.apple.com/auth/keys{
"keys": [
{...},
{
"kty": "RSA",
"kid": "eXaunmL",
"use": "sig",
"alg": "RS256",
"n": ...,
"e": "AQAB"
},
{...}
]
}At some point you are sending the identityToken to your backend. Your backend has to check the header to get the correct kid to get the correct key from the auth/keys. So you have to fix the issue on the backend.
Post not yet marked as solved
The identityToken of ASAuthorizationAppleIDCredential contains in the header the "kid" you need to match with the list I guess.
Post not yet marked as solved
Small Update for the Button Problem:With 6.1 Apple changed something with the WKInterfaceObjectRepresentable so my SwiftUI implementation of the WKInterfaceAuthorizationAppleIDButton does not work. The .onTapGesture from SwiftUI is not recognizing the taps anymore.
Post not yet marked as solved
Thanks for the reply. I will have a look on the issues. If you have questions regarding the Sign in with Apple things on the watch just ask. One of the major issues we have at the moment is the behaviour of the Capabilities in the apple dev center. Sometime the Sign in with Apple Capability of our Watch Target changes from "App Id ***" to "Primary App" - then the Apple Sign in wont work anymore on the watch.We also discovered problems with the complete "Sign in with Apple" if you're using multiple apps with "Sign in with Apple". Sometimes your Apple Id Credentials wont show up in the Action Sheet if there are other Apps that are using Siwa. After removing them from the Settings the Credentials show up. Because of the great release notes for 13.1 and 13.2 ("There are no release notes for this software update") I have no Idea if this is fixed or not, because this happes just sometimes and randomly.
Post marked as Apple Recommended
Update: We are not blocked anymore. 🙂
Hey,1. If I "sign in with apple" with the primary app, and then i want to use the secondary app, do i have to sign in again?Yes, you have to sign in again. As an example: You have an iOS App with an independent watchOS App. If you register on the iOS App you can login on the watch without a registration. It is more a shortcut to login. Siwa uses app groups to detect if two different apps/targets should use the same account. Without app groups you would need an other account on the watch because the watch app would not know that their was already an account registered. Or am I already signed in because I have signed in with the primary app? NoOr can I architect it in such a way that allows me to sign in to one of the grouped apps, and then stay signed in when using another grouped app?NoBestSebastian
Post not yet marked as solved
Hey,I added Sign in with Apple to the Yazio iOS App and the independet watchOS App written in SwiftUI. If you catch some error cases you can share them with me 🙂. Our implementation is a bit different to others. Most of the apps I've seen are using the same button for registration or login at the same page. We're using the Siwa button at the end of our onboarding and another one at our Login form. I'm always open for feedback.BestSebastian
Post marked as Apple Recommended
Waiting also for an update!
Thanks for that info. Added a feedback report.
Post not yet marked as solved
Same problem with Xcode 11.0 GM (11A419c). Pairing does not work.
