Repository navigation
Login-Tapping try new Expensify directs to log out page #102728
Description
If you haven’t already, check out our contributing guidelines for onboarding. To join our Slack channel, fill out this form.
Version Number: V9.5.0-0
Reproducible in staging?: Yes
Reproducible in production?: No
If this was caught during regression testing, add the test name, ID and link from BrowserStack: https://test-management.browserstack.com/projects/2219752/test-runs/76512659/folder/13176927/41237621/1815563624?sort=%2Bname
Email or phone of affected tester (no customers): [email protected]
Issue reported by: Applause Internal Team
Bug source: Exploratory - Significant User Experience Deterioration
Device used: Redmi note 10s android 13
App Component: User Settings
Action Performed:
- Launch app
- Tap troubleshoot - reset and tap switch to classic
- Tap try new Expensify
- Note user sign out page is shown
- Close and reopen app
- Note user is directed to new dot page
Expected Result:
Tapping try new Expensify must directs to new dot page.
Actual Result:
Tapping try new Expensify directs to log out page.
Workaround:
Unknown
Platforms:
- Android: App
- Android: mWeb Chrome
- iOS: App
- iOS: mWeb Safari
- iOS: mWeb Chrome
- Windows: Chrome
- MacOS: Chrome Safari
Screenshots/Videos
Bug7274152_1790836643460.Screenrecorder-2026-10-01-12-02-10-779.1.mp4
Applause Internal Information
Exported by: Julia Ponikarchuk
Bug ID: 7274152
Metadata
Metadata
Assignees
Type
Projects
- Status
Activity
applause-bot commentedon Oct 1, 2026
While Applause doesn't embed attachments for this bug, here are the links for quick view:
https://platform.applause.com/services/links/v1/external/5f6347f60ab107fd3345c859a772881e98cbf7d43206854eff7fb30ee3093c68
melvin-bot commentedon Oct 1, 2026
Triggered auto assignment to @yuwenmemon (
DeployBlockerCash), see https://stackoverflowteams.com/c/expensify/questions/9980/ for more details.melvin-bot commentedon Oct 1, 2026
💬 A slack conversation has been started in #expensify-open-source
github-actions commentedon Oct 1, 2026
👋 Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open `StagingDeployCash` deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:
MelvinBot commentedon Oct 1, 2026
Deploy Blocker Analysis
Likely cause (medium confidence): chore(deps): Update NitroSQLite to 9.8.2 (
Expensify/App#101437, bychrispader, merged 2026-09-30, on Deploy Checklist: New Expensify 2026-09-30).Recommendation: Revert #101437 together with its companion native change. It is a dependency bump, so the revert should be clean.
Why: NitroSQLite 9.8.0+ throws
Database OnyxDB is already openwhen a database is opened a second time in the same Android process. Older versions silently replaced the open connection. When Android HybridApp starts a new NewDot JS runtime in the same process after "Try new Expensify," Onyx fails to open its store. NewDot then starts with no session and shows the sign-in page. A cold restart clears the native state, so the open succeeds and NewDot loads.Investigation details
Evidence chain
react-native-nitro-sqlitefrom 9.6.0 to 9.8.2 (package.json:204) and turns onthreadSafeandperformanceMode(package.json:456-459).cpp/operations.cpp) that lives as long as the Android process, not the JS runtime. Nothing closes them when a runtime is torn down.sqliteOpenDbthrowsDatabaseAlreadyOpenif the name is already in that map. 9.6.0 and 9.7.0 overwrote the entry (dbMap[dbName] = db).OnyxDBat startup. If that throws, the store stays unset and every read fails withStore is not initialized!.Not verified
Database OnyxDB is already openorStore is not initialized!during the repro.Other candidates (lower)
NetworkStore.tsandenhanceParameters.ts, but only adds logging.HybridAppHandler.tsx,actions/HybridApp,actions/Session,actions/App.ts, or the Troubleshoot page.Fix-forward options (if you don't revert)
Next Steps: Reply with
@MelvinBot <your feedback>to refine this analysis.view run
chrispader commentedon Oct 1, 2026
Looking into this!
chrispader commentedon Oct 1, 2026
I've found the fix for this deploy blocker and i'm about to publish 2 new versions of NitroSQLite:
v9.8.3is going to include just the fix. We can bump the dependency immediately to fix the deploy blocker.v10.0.1includes the fix + more features and performance improvements that are already being worked in this issue and this PR. The PR will still have to be reviewed and QAd separately.chrispader commentedon Oct 1, 2026
Chris's AI release helper here. 🤖
The NitroSQLite 9.8.3 dependency updates are ready for review:
Both PRs stay limited to NitroSQLite dependency and lockfile updates. Their descriptions include this blocker's Reset → Classic → Try New Expensify reproduction and expected result, along with an iOS regression check. Manual native and staging QA remain pending.
cc @NicolasBonet
Julesssss commentedon Oct 1, 2026
PRs cherry-picked
m-natarajan commentedon Oct 1, 2026
Not repro, Redmi note 10s android 13, 9.5.0-3
Screenrecorder-2026-10-01-23-47-12-387.mp4
melvin-bot commentedon Oct 1, 2026
If you are the assigned CME please investigate whether the linked PR caused a regression and leave a comment with the results.
If a regression has occurred and you are the assigned CM follow the instructions here.
If this regression could have been avoided please consider also proposing a recommendation to the PR checklist so that we can avoid it in the future.
melvin-bot commentedon Oct 1, 2026
@yuwenmemon / @Julesssss / @NicolasBonet
The solution for this issue has been 🚀 deployed to production 🚀 in version 9.5.0-5 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:
The following checklist (instructions) will need to be completed before the issue can be closed. Please copy/paste the Contributor+ Checklist from here into a new comment on this GH and complete it. If you have the K2 extension, you can simply click: [this button]. If no checklist is needed for this issue, you can click: [no checklist button]