auto-sign in with sign in link in separate browser by mukhrr · Pull Request #90488 · Expensify/App

mukhrr · 2026-05-13T12:15:13Z

Explanation of Change

Fixed Issues

$ #89545
PROPOSAL: #89545 (comment)

Tests

Log in with existing account and request magic code
Navigate to email and locate the magic link - change to staging if needed
Open an new INCOGNITO window and navigate to the staging link
Verify the "Here's your magic code" page is displayed
Verify there's a link to "Just sign In here"
Click the link

Verify you are in Home page
Verify that no errors appear in the JS console

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

web specific fix

Android: mWeb Chrome

android_web.mp4

iOS: Native

web specific fix

iOS: mWeb Safari

ios_web.mp4

MacOS: Chrome / Safari

web.mp4

melvin-bot · 2026-05-13T12:15:21Z

@DylanDylann Please copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9b9d213285

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: ccdd6e18a5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

codecov · 2026-05-13T17:26:29Z

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines	Coverage Δ
...s/Navigation/helpers/getStateToResetAfterLogout.ts	`100.00% <100.00%> (ø)`
src/pages/ValidateLoginPage/index.web.tsx	`100.00% <100.00%> (+2.63%)`	⬆️
src/libs/Navigation/AppNavigator/AppNavigator.tsx	`0.00% <0.00%> (ø)`
src/libs/Navigation/NavigationRoot.tsx	`76.00% <66.66%> (-2.00%)`	⬇️
... and 107 files with indirect coverage changes

trjExpensify

Nice, we talked about this one on the parent issue. 👍

DylanDylann · 2026-05-15T06:48:20Z

@codex review

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 859c304e5a

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

DylanDylann · 2026-05-15T08:54:06Z

@mukhrr Ohh wait. Could you reproduce the bug on main?

mukhrr · 2026-05-15T09:44:04Z

@DylanDylann yes

DylanDylann · 2026-05-18T07:56:59Z

    }, []);

    useEffect(() => {
-        if (!!login || !cachedAccountID || !is2FARequired) {


Why do you remove this condition?

The condition wasn't removed, it was split across two effects to satisfy Codex's earlier "don't reschedule exitTo" feedback #90488 (comment)

DylanDylann · 2026-05-18T07:57:12Z


-        // The user clicked the option to sign in the current tab
+    useEffect(() => {
+        if (exitTo || login) {


Why do we need the login condition here?

login being set means this browser initiated the login → there's an original tab, handled by the existing isUserClickedSignIn goBack flow + JustSignedInModal. The HOME redirect must only fire when login is empty (fresh/incognito, no original tab). Without the login guard we'd hijack the normal "head back to your original tab" flow.

DylanDylann · 2026-05-18T07:58:46Z

BUG 1: The white screen is displayed between two loading indicators

BUG 2: After signing out, the app returns to the magic code screen

Screen.Recording.2026-05-18.at.14.56.04.mov

mukhrr · 2026-05-18T15:54:32Z

BUG 1: The white screen is displayed between two loading indicators

Fixed bug 1. working on the 2nd one which is a bit tricky to fix

BUG 2: After signing out, the app returns to the magic code screen

mkhutornyi · 2026-06-14T10:07:58Z

Reviewer Checklist

I have verified the author checklist is complete (all boxes are checked off).
I verified the correct issue is linked in the ### Fixed Issues section above
I verified testing steps are clear and they cover the changes made in this PR
- I verified the steps for local testing are in the Tests section
- I verified the steps for Staging and/or Production testing are in the QA steps section
- I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
- I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
I checked that screenshots or videos are included for tests on all platforms
I included screenshots or videos for tests on all platforms
I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
I verified tests pass on all platforms & I tested again on:
- Android: HybridApp
- Android: mWeb Chrome
- iOS: HybridApp
- iOS: mWeb Safari
- MacOS: Chrome / Safari
- MacOS: Desktop
If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
I verified there are no new alerts related to the canBeMissing param for useOnyx
I verified proper code patterns were followed (see Reviewing the code)
- I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
- I verified that comments were added to code that is not self explanatory
- I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
- I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
- I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
- I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
- I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
- I verified the JSDocs style guidelines (in STYLE.md) were followed
If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
I verified that this PR follows the guidelines as stated in the Review Guidelines
I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
If a new component is created I verified that:
- A similar component doesn't exist in the codebase
- All props are defined accurately and each prop has a /** comment above it */
- The file is named correctly
- The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
- The only data being stored in the state is data necessary for rendering and nothing else
- For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
- Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
- All JSX used for rendering exists in the render method
- The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions
If any new file was added I verified that:
- The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
If a new CSS style is added I verified that:
- A similar style doesn't already exist
- The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
- I verified that all the inputs inside a form are aligned with each other.
- I added Design label and/or tagged @Expensify/design so the design team can review the changes.
If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp

android.mov

Android: mWeb Chrome

iOS: HybridApp

ios.mov

iOS: mWeb Safari

msafari.mov

MacOS: Chrome / Safari

web.mov

mkhutornyi · 2026-06-14T11:26:39Z

btw, just fyi, separate-session 2FA has bug on both Staging and NewDot.

Go to the sign-in page, enter the 2FA account's email → this emails the magic-code link https://new.expensify.com/v//.

Open a fresh incognito window.

Paste/open the /v/... link there.

Click "Just sign in here".

Observe: blank page (spinner never resolves into anything, no 2FA prompt).

Expected: Two-factor authentication required Page

Actual: Blank page:

REC-20260602090546.mp4

I think the expected behavior is to show enter 2FA code page instead of 2FA required page as link already expired and never able to proceed on first-trying-to-sign-in browser.
Let's not block on this as already broken on production.

msafari.mov

Expected:

This PR:

mkhutornyi · 2026-06-14T11:30:15Z

I tested as many cases as possible but still be on a look out for any blockers.

MelvinBot · 2026-06-14T11:35:57Z

🤖 MelvinBot — regression re-review

Verdict: No new blocking correctness bugs. Prior review comments look addressed (the getStateToResetAfterLogout justification was reworded correctly, and the separate-session 2FA + Back-button regressions are fixed). Below are the possible regressions worth confirming in QA, ordered by blast radius.

1. `AppNavigator` Suspense fallback — highest blast radius (ALL platforms)

AppNavigator.tsx changes the fallback from null to a full-screen LoadingIndicator (absoluteFillObject + fullScreenLoading: componentBG @ opacity: 0.8, zIndex: 10). This now renders on every AuthScreens/PublicScreens lazy-chunk resolution — not just the sign-in swap. On native the chunk is bundled (resolves fast), and the web prefetch usually masks it, but a slow cold web load or sign-out could now show a loader flash where it was previously blank. Make sure B1 (no flash on cold start) and B4 (no flash on logout → PublicScreens) genuinely pass on throttled web.

2. `isUserClickedSignIn` redirect: `goBack()` → focus-effect `navigate(HOME, {forceReplace})`

The redirect moved from a mount-only goBack() to a useFocusEffect that fires on every focus while isUserClickedSignIn is true. Correct for the fresh-window target (nowhere to go back to), but note the behavior change:

After a separate-session sign-in, login is never cached and autoAuthState stays JUST_SIGNED_IN, so isUserClickedSignIn stays true. The user can therefore no longer revisit /v/... to view the code — any focus bounces them to HOME. Acceptable, but a real behavior change from the old goBack.
Confirm A1.2 (Back ≠ /v/) doesn't produce a navigate loop if forceReplace is downgraded to a push.

3. Signed-in "view the code" path is sensitive to `autoAuthState`

isUserClickedSignIn is !login && isSignedIn && (SIGNING_IN || JUST_SIGNED_IN). A2.2 passes because autoAuthState is NOT_STARTED. But a signed-in user with no cached login who opens /v/... while their session's autoAuthState is still JUST_SIGNED_IN (lingering from a recent magic-link sign-in) would be redirected HOME instead of seeing ValidateCodeModal. Narrow edge — flagging for awareness, not blocking.

4. Permanent spinner is still reachable by design

When isCompletingDirectSignIn is true but authToken never lands (stuck case), the loader stays up indefinitely and only a 30s Log.alert fires — observability only, no recovery UX. This matches the pre-existing production behavior the team chose not to block on, but it is a permanent spinner with no user-facing timeout/error. Worth a product confirm.

Things I checked that are NOT regressions

2FA separate-session: dropping !!login from the 2FA modal guard correctly surfaces the 2FA prompt for fresh sessions; isCompletingDirectSignIn's !is2FARequired guard prevents an infinite loader. During the SIGNING_IN phase the existing === SIGNING_IN loader branch still shows (no blank gap).
NavigationRoot try/catch fallback: Log is imported; on a rejected reset it falls back to {index:0, routes:[{name: HOME}]} — no blank screen. ✅
getStateToResetAfterLogout: preserves the old logout behavior (clear params only for REPORTS_SPLIT_NAVIGATOR, preserve TRANSITION_BETWEEN_APPS params) and adds VALIDATE_LOGIN → HOME. Unit tests cover all branches.
Static review only — I couldn't execute the Jest suite here, so rely on CI for the green check.

This is an automated re-review from MelvinBot — a second set of eyes, not a substitute for human review.

chatgpt-codex-connector

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e18daffab5

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

Open a pull request for review
Mark a draft as ready
Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

mukhrr · 2026-06-14T11:43:42Z

I think the expected behavior is to show enter 2FA code page instead of 2FA required page as link already expired and never able to proceed on first-trying-to-sign-in browser.

This makes sense to me. Let's just confirm it cc @trjExpensify

trjExpensify · 2026-06-15T18:43:29Z

Yes, I would think if the user clicks "Just sign in here" and has 2FA enabled, we would then show them the 2FA entry screen prior to navigating into the product. CC: @NikkiWines do you agree with that?

NikkiWines · 2026-06-15T22:05:16Z

Yep, that makes sense to me 👍

github-actions · 2026-06-15T22:30:40Z

🚧 @blimpich has triggered a test Expensify/App build. You can view the workflow run here.

OSBotify · 2026-06-15T22:35:29Z

✋ This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

github-actions · 2026-06-15T22:36:41Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, and Web. Happy testing! 🧪🧪
Built from App PR #90488.

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-16202168d9c-d12cd93-5bfdf2fbd6b61d26df62a0e4ecc329053b8b6cf9/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-1620216-d12cd93-473c8c4f32d26c826536223299d5fff474c25fa7/index.html

Web 🕸️
https://90488.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

mukhrr · 2026-06-16T00:05:16Z

Just sign in here" and has 2FA enabled, we would then show them the 2FA entry screen prior to navigating into the product

Oh @blimpich i had not pushed this yet) can I still push here?

mukhrr · 2026-06-16T00:13:58Z

Or ideally can we a separate issue for that ? cc @trjExpensify

trjExpensify · 2026-06-16T00:38:27Z

This PR is now merged, so you can't. Please prepare another PR so we can follow-up with that. 👍

mukhrr · 2026-06-16T04:12:45Z

This PR is now merged, so you can't. Please prepare another PR so we can follow-up with that. 👍

Here is it is #93656! cc @mkhutornyi

blimpich · 2026-06-16T16:05:41Z

Ah that's my bad, I misunderstood and thought the behavior had already been implemented and you were just asking for confirmation that it was indeed the correct behavior 🙁

OSBotify · 2026-06-16T20:09:14Z

🚀 Deployed to staging by https://github.com/blimpich in version: 9.4.9-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-06-16T20:13:17Z

🤖 Help site review: no changes required

I reviewed the changes in this PR against the help site articles under docs/articles and concluded no help site updates are needed.

Why

This PR is a bug fix for issue #89545 — "Blank page opens when login via magic link different session." The changes are entirely internal navigation/loading behavior:

Show a loading indicator instead of a blank screen while the lazy AuthScreens chunk downloads (AppNavigator.tsx).
Redirect Home after a separate-session magic-link sign-in, and reset the nav state after logout so a consumed /v/... code can't strand the user (NavigationRoot.tsx, getStateToResetAfterLogout.ts, ValidateLoginPage/index.web.tsx).
Add observability (a stuck-sign-in Log.alert) and unit/UI tests.

This restores the already-expected behavior (the user should log in) rather than introducing or changing any user-facing feature, setting, label, or workflow. The existing Login Troubleshooting article documents login problems at the appropriate level and doesn't describe this blank-page bug as expected behavior, so nothing there needs to change.

Because no documentation changes are required, I did not open a draft help site PR.

@mukhrr, please confirm you agree that no help site changes are needed here. If you believe a doc update is warranted, let me know what behavior should be documented and I'll create the draft PR.

mitarachim · 2026-06-16T22:10:46Z

Deploy Blocker #93753 was identified to be related to this PR.

mitarachim · 2026-06-16T23:06:00Z

Deploy Blocker #93758 was identified to be related to this PR.

OSBotify · 2026-06-17T18:12:08Z

🚀 Deployed to production by https://github.com/puneetlath in version: 9.4.9-0 🚀

platform	result
🕸 web 🕸	success ✅
🤖 android 🤖	success ✅
🍎 iOS 🍎	success ✅

auto-sign in with sign in link in separate browser

9b9d213

mukhrr requested review from a team as code owners May 13, 2026 12:15

melvin-bot Bot assigned mukhrr May 13, 2026

melvin-bot Bot requested review from DylanDylann and trjExpensify and removed request for a team May 13, 2026 12:15

melvin-bot Bot removed the request for review from a team May 13, 2026 12:15

chatgpt-codex-connector Bot reviewed May 13, 2026

View reviewed changes

Comment thread src/pages/ValidateLoginPage/index.website.tsx Outdated

added necessary tests

ca6e2cf

mukhrr marked this pull request as draft May 13, 2026 13:12

fixed eslint

ccdd6e1

mukhrr marked this pull request as ready for review May 13, 2026 17:06

mukhrr mentioned this pull request May 13, 2026

[Due for payment 2026-06-24] [$250] Login - Blank page opens when login via magic link different session #89545

Closed

7 tasks

chatgpt-codex-connector Bot reviewed May 13, 2026

View reviewed changes

Comment thread src/pages/ValidateLoginPage/index.web.tsx Outdated

fix exitTo navigation rescheduling

859c304

trjExpensify previously approved these changes May 13, 2026

View reviewed changes

chatgpt-codex-connector Bot reviewed May 15, 2026

View reviewed changes

Comment thread src/pages/ValidateLoginPage/index.web.tsx Outdated

Merge branch 'main' into fix/89545

af0ac5e

mukhrr dismissed trjExpensify’s stale review via af0ac5e May 15, 2026 09:45

applied forceReplace to navigation

6780966

DylanDylann reviewed May 18, 2026

View reviewed changes

fixed intermediate blank page between two loading spinner pages

3a8fe41

fixed eslint

e18daff

mkhutornyi approved these changes Jun 14, 2026

View reviewed changes

melvin-bot Bot requested a review from blimpich June 14, 2026 11:30

chatgpt-codex-connector Bot reviewed Jun 14, 2026

View reviewed changes

Comment thread src/pages/ValidateLoginPage/index.web.tsx

blimpich approved these changes Jun 15, 2026

View reviewed changes

blimpich merged commit 1620216 into Expensify:main Jun 15, 2026
35 checks passed

mukhrr mentioned this pull request Jun 16, 2026

redirect 2FA in incognito while 2FA is enabled #93656

Merged

53 tasks

OSBotify mentioned this pull request Jun 16, 2026

Deploy Checklist: New Expensify 2026-06-16 #93740

Closed

46 tasks

applause-bot Bot mentioned this pull request Jun 16, 2026

[Due for payment 2026-06-30] Login - User is asked to go back to original session to enter 2FA after clicking sign in here #93753

Closed

7 tasks

applause-bot Bot mentioned this pull request Jun 16, 2026

Login-Spinner appears briefly after opening expired magic link and logging in with new account #93758

Closed

7 tasks

Uh oh!

Conversation

mukhrr commented May 13, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Explanation of Change

Fixed Issues

Tests

Offline tests

QA Steps

PR Author Checklist

Screenshots/Videos

Uh oh!

melvin-bot Bot commented May 13, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

codecov Bot commented May 13, 2026 • edited by github-actions Bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Codecov Report

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented May 15, 2026

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

DylanDylann commented May 15, 2026

Uh oh!

mukhrr commented May 15, 2026

Uh oh!

DylanDylann May 18, 2026

Choose a reason for hiding this comment

Uh oh!

mukhrr May 18, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann May 18, 2026

Choose a reason for hiding this comment

Uh oh!

mukhrr May 18, 2026

Choose a reason for hiding this comment

Uh oh!

DylanDylann commented May 18, 2026

Uh oh!

mukhrr commented May 18, 2026

Uh oh!

mkhutornyi commented Jun 14, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

mkhutornyi commented Jun 14, 2026

Uh oh!

mkhutornyi commented Jun 14, 2026

Uh oh!

MelvinBot commented Jun 14, 2026

🤖 MelvinBot — regression re-review

1. AppNavigator Suspense fallback — highest blast radius (ALL platforms)

2. isUserClickedSignIn redirect: goBack() → focus-effect navigate(HOME, {forceReplace})

3. Signed-in "view the code" path is sensitive to autoAuthState

4. Permanent spinner is still reachable by design

Uh oh!

chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

💡 Codex Review

Uh oh!

Uh oh!

mukhrr commented Jun 14, 2026

mukhrr commented May 13, 2026 •

edited

Loading

codecov Bot commented May 13, 2026 •

edited by github-actions Bot

Loading

mkhutornyi commented Jun 14, 2026 •

edited

Loading

1. `AppNavigator` Suspense fallback — highest blast radius (ALL platforms)

2. `isUserClickedSignIn` redirect: `goBack()` → focus-effect `navigate(HOME, {forceReplace})`

3. Signed-in "view the code" path is sensitive to `autoAuthState`

mukhrr commented Jun 16, 2026 •

edited

Loading