[Sentry: APP-EQF] NitroSQLite too many SQL variables on Android

[mountiny]

Sentry

https://expensify.sentry.io/issues/APP-EQF

Impact (snapshot at filing)

• Users (total since first seen): 2
• Events: 3
• Users (last 14d): 1
• First seen: 2026-06-06
• Last seen: 2026-06-22 (ongoing)
• Platform: Android hybrid (org.me.mobiexpensifyg)
• App version(s): 9.4.0-0, 9.4.16-2
• Affected route(s) (parameterized): Settings_Troubleshoot
• Mechanism: onunhandledrejection (reported as handled in Sentry tags)

Stack trace (top frames, first-party only)

No first-party stack frames available in Sentry for this issue.
Error: NitroSQLiteError: [NativeNitroSQLiteException][SqlExecutionError] too many SQL variables

Suspected cause

A NitroSQLite query is likely building an IN (...) clause (or equivalent bound-parameter list) that exceeds SQLite's variable limit (~999) when run against a large local Onyx database. Affected users appear to be power accounts (11–50 policies, 10,000+ reports, 1,001–2,500 personal details), which matches David Barrett's Android loading investigation where local DB work is a bottleneck.

Reproduction

Unknown — see Sentry events linked from the Sentry issue. Last known context: Android hybrid, Settings_Troubleshoot, production release new.expensify@9.4.16-2.

Related

• Sibling Sentry IDs (if any): none identified
• Prior GH issues: #87844 (Onyx storage errors umbrella), #87868 (NitroSQLite disk full)

Issue Owner

Current Issue Owner: @chrispader

[saadamjad]

Hi, do we have upwork job for this issue?

[melvin-bot]

📣 @saadamjad! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[Bakomebandias]

Picking this up! 👋

Fix plan: Investigate NitroSQLite 'too many SQL variables' error on Android. Will identify the query exceeding SQLite's SQLITE_MAX_VARIABLE_NUMBER limit and batch it properly.

Will use GitHub Codespace for Android environment. PR coming shortly. @Bakomebandias

[melvin-bot]

📣 @Bakomebandias! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

1. Make sure you've read and understood the contributing guidelines.
2. Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
3. Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
4. Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.
   
   Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

[melvin-bot]

@chrispader Uh oh! This issue is overdue by 2 days. Don't forget to update your issues!