What continuing a process into the launch leaves on top when the login that
created the session cannot bring the launch's splash: the launch's first
screen, the feed. It is a root of the restarted stack, so it carries no
back.
The password login and the two-factor actions that complete one create the
session on the password login path; the 451 launch brings the
location-permission splash only on account-recovery, so their result type
excludes it. The registration is not one of them: its path has its own first
screen (RegistrationFirstScreen).
What continuing a process into the launch leaves on top when the login that created the session cannot bring the launch's splash: the launch's first screen, the feed. It is a root of the restarted stack, so it carries no
back.The password login and the two-factor actions that complete one create the session on the
passwordlogin path; the 451 launch brings the location-permission splash only onaccount-recovery, so their result type excludes it. The registration is not one of them: its path has its own first screen (RegistrationFirstScreen).