Duolith docs

Errors E0400 to E0499

E0402 Sign-in that comes back through a link

Message sign-in comes back to the app through a link, which this app's shell cannot receive

Words in italics are filled in when the compiler reports it, such as the element's name or the list of known ones.

Why

A magic link opens the app from an email, and on Android a provider's page in a Custom Tab (Apple, or Google at an authorizationEndpoint of the app's own) returns to redirectUri as a link that opens the app. Either finishes only when the shell hands that link to sign-in. The iOS and Android shells duolith builds do (decision 0141), so these sign-ins build and work there. A shell that does not hand links over, such as one of your own that leaves the effects bridge's receivesLinks false, fails such a sign-in with this code on the phone, when it starts, before anything opens or any email is sent, rather than start a sign-in that never finishes (decision 0110). Sign in with Google through Credential Manager (no authorizationEndpoint), with a password, or with a provider at a path of the app ("/mock-provider") needs no link.

How to fix it

Have the shell pass every link that opens the app to EffectsBridge.openLink and set receivesLinks, as native/android's MainActivity and native/ios's DuolithViewController do. Otherwise sign in with a password, or with Google with no authorizationEndpoint.

In a terminal

duolith explain E0402

Mentioned in