I keep coming back to this article, because it seems like the only one on the Internet that covers this topic in detail. That's the sign of a good post :)
Scenario: I'm using expo on an iPhone. I've implemented Sign in with Apple to the point now, where I can click on a button and I get swung out to appleid.apple.com page in Safari.
This opens an action menu for apple ID the first go round. And I click continue. Subsequent logins don't prompt with the action menu, as AppleID is already in use for the expo app.
I then get prompted to open Expo, because of the redirect (bad UX, but hey, I can't see a better way yet).
Now, I'm redirected to the page where I was last in my expo app.
If I use a React useEffect hook to run Auth.currentAuthenticatedUser() on page load, I get "not authenticated" as a response, after returning from appleId auth page.
If I shake the phone and reload the app, I become authenticated by my app (i.e. Auth.currentAuthenticatedUser() works just fine.
Question: I feel like I'm missing a crucial step here. What is it? :)
I figured this out a while back... In short I was being a bit dumb...
The useEffect hook was worthless, because when the user is returned from to the app after successful authorization, they are not immediately recognized as being signed in, so an Auth.currentAuthenticatedUser() will throw an error.
One problem I had (still have) is it takes about 3 seconds after returning from the Auth provider to for the data.payload.event, signIn, to be "heard" by the hub. This delay only seems to occur on a mobile.
Anyhow, to provide better UX, I return the user to a page that has a, "Continue with" button, that sends them to a loading page until the signIn event occurs and I can trigger the app into action or handle an error from that point on.
Still way too many clicks and popping in/out of windows, which I'm thinking about how to reduce.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I keep coming back to this article, because it seems like the only one on the Internet that covers this topic in detail. That's the sign of a good post :)
Scenario: I'm using expo on an iPhone. I've implemented Sign in with Apple to the point now, where I can click on a button and I get swung out to appleid.apple.com page in Safari.
This opens an action menu for apple ID the first go round. And I click continue. Subsequent logins don't prompt with the action menu, as AppleID is already in use for the expo app.
I then get prompted to open Expo, because of the redirect (bad UX, but hey, I can't see a better way yet).
Now, I'm redirected to the page where I was last in my expo app.
If I use a React useEffect hook to run Auth.currentAuthenticatedUser() on page load, I get "not authenticated" as a response, after returning from appleId auth page.
If I shake the phone and reload the app, I become authenticated by my app (i.e. Auth.currentAuthenticatedUser() works just fine.
Question: I feel like I'm missing a crucial step here. What is it? :)
I figured this out a while back... In short I was being a bit dumb...
The useEffect hook was worthless, because when the user is returned from to the app after successful authorization, they are not immediately recognized as being signed in, so an
Auth.currentAuthenticatedUser()will throw an error.One problem I had (still have) is it takes about 3 seconds after returning from the Auth provider to for the
data.payload.event,signIn, to be "heard" by the hub. This delay only seems to occur on a mobile.Anyhow, to provide better UX, I return the user to a page that has a, "Continue with" button, that sends them to a loading page until the
signInevent occurs and I can trigger the app into action or handle an error from that point on.Still way too many clicks and popping in/out of windows, which I'm thinking about how to reduce.