[Due for payment 2026-03-30] [$250] Batch non-critical navigation logs during app startup

[mountiny]

Proposal here

Background: The app's logging library supports several severity levels. Among them, Log.warn() immediately flushes to the server via an API call, while Log.hmmm() batches  entries locally and sends them only when the buffer fills (150 lines) or a timeout expires. Both ultimately deliver messages to the server - they differ only in timing. During app initialization, React Navigation's navigationRef is briefly unready. Seven navigation helpers check for this state and log a message when they encounter it.

Problem: When the app initializes and the navigation reference is momentarily unready, navigation helpers fire Log.warn() calls that each force an immediate server flush, competing for bandwidth with critical data-fetching operations.

Solution: Downgrade seven Log.warn() calls to Log.hmmm() in navigation helpers that log expected "navigationRef not ready" states. The log messages remain unchanged - the same information reaches the server, just batched rather than flushed individually. This drops startup Log API calls from 18 to 2 with no loss of observability or change to navigation behavior.

Issue Owner

Current Issue Owner: @eh2077

Issue Owner

Current Issue Owner: @eh2077

Upwork Automation - Do Not Edit

• Upwork Job URL: https://www.upwork.com/jobs/~022034239234242976099
• Upwork Job ID: 2034239234242976099
• Last Price Increase: 2026-03-18

[MelvinBot]

Proposal

Please re-state the problem that we are trying to solve in this issue.

During app startup, React Navigation's navigationRef is briefly unready. Six navigation helpers detect this state and call Log.warn(), which forces an immediate server flush per call. These redundant network requests compete for bandwidth with critical data-fetching operations at startup.

What is the root cause of that problem?

Log.warn() calls Logger.add() with forceFlushToServer=true (Logger.js:115), forcing an immediate API call for each log line. Log.hmmm() calls Logger.add() with forceFlushToServer=false (Logger.js:125), batching logs until the buffer hits 150 lines or a timeout expires. The "NavigationRef is not ready" messages are expected, transient conditions during startup — not actionable warnings — so they don't need immediate flushing.

The six locations using Log.warn() for this expected condition are:

1. src/hooks/useRootNavigationState.ts:20
2. src/libs/Navigation/Navigation.ts:254
3. src/libs/Navigation/AppNavigator/createSplitNavigator/SplitRouter.ts:38
4. src/libs/Navigation/helpers/navigateToWorkspacesPage.ts:25
5. src/libs/Navigation/helpers/isOnSearchMoneyRequestReportPage.ts:7
6. src/libs/actions/Session/index.ts:986

What changes do you think we should make in order to solve the problem?

Change Log.warn(...) to Log.hmmm(...) in each of the six locations listed above. The log messages themselves remain unchanged — the same information still reaches the server, just batched rather than individually flushed. No navigation behavior changes.

What alternative solutions did you explore? (Optional)

• Remove the logs entirely: Rejected because the messages are useful for debugging navigation timing issues — we just don't need them flushed immediately.
• Debounce/deduplicate the Log.warn calls: Unnecessary complexity when simply switching to Log.hmmm() achieves the same batching behavior built into the Logger.

---

Next Steps for Contributor+ team: Reply with @MelvinBot implement this to create a draft PR, @MelvinBot <your feedback> to refine this analysis, or explain why you are rejecting Melvin's proposal.

[melvin-bot]

Triggered auto assignment to Contributor-plus team member for initial proposal review - @eh2077 (External)

[melvin-bot]

Job added to Upwork: https://www.upwork.com/jobs/~022034239234242976099