Posts

Post marked as solved
34 Replies
Thanks @ppinkney! This fixed our issue when signing in Safari on iOS13 + Catalina.However if the user hits cancel, we are not seeing the redirect to `redirect_uri`. Can you think of anything that comes to mind ?
Post not yet marked as solved
3 Replies
Also having this issue.Our sign in flow works flawlessly on every browser except Safari on iOS13 and latest Safari on Catalina. It breaks when the native Safari auth popup is involved.We follow the flow described in: https://developer.apple.com/documentation/signinwithapplejs/incorporating_sign_in_with_apple_into_other_platformsThe most interesting part is once you click on the sign in button no network requests are shown in Safari dev console, but I can see the URL changing briefly.
Post not yet marked as solved
1 Replies
They very recently added a 'usePopup' feature. I couldn't get it to work, can you ? It is supposed to communicate via web events. Can't get it working though.Our solution was to not use the Apple API because we have a single page app and obviously can't receive a POST... So the Apple has to POST to our server.Our request flow works like this once user clicks sign in with apple:1. Request our server at /user/auth/apple with our own redirectUrl. That gets put into some server side state.1. That redirects to apple auth with redirect_uri of /user/auth/apple/callback1. Once apple completes it redirects to /callback. Server creates the user and then redirects to the url passed in step 1.This breaks when using Safari / native auth. Not sure how to proceed.
Post not yet marked as solved
2 Replies
Are you seeing the `AppleIDSignInOnSuccess` web event at all ?No matter what I try, I can't see it. And I can only see the ` AppleIDSignInOnFailure` web event when I use the X on the browser. I don't see it when I click cancel.