fix: android pressability issue with measureAsyncOnUI patch by MelvinBot · Pull Request #86160 · Expensify/App

MelvinBot · 2026-03-24T02:43:48Z

Explanation of Change

Note: This PR is a recreation of #85745 on top of current main. The original branch had no common ancestor with main, making it impossible to merge. All changes are identical.

This PR adds a react-native patch based on the upstream PR facebook/react-native#51835 to fix an Android-specific issue where onPress events do not trigger for Pressable components when used inside a Tooltip on certain Samsung devices.

Root Cause: In the new architecture, Pressability.measure() reads layout information from the shadow tree. When a tooltip uses a Reanimated animation (e.g., scale: 0 during entry), the shadow tree retains the stale value while the UI thread has already updated. This causes Pressability to incorrectly compute the pressable region as having zero size, making the button untappable.

Fix: Introduces a new measureAsyncOnUI method that measures views using the native view hierarchy on the UI thread instead of the shadow tree. This ensures correct measurements even when Reanimated has modified the view's transform on the native side.

The patch modifies:

JS: Pressability.js to call measureAsyncOnUI instead of measure; adds measureAsyncOnUI to FabricUIManager, ReactFabricHostComponent, ReactNativeElement, and type definitions
C++ (shared): Adds measureAsyncOnUI binding in UIManagerBinding.cpp, with delegation through UIManagerDelegate → Scheduler → SchedulerDelegate
iOS: Implements async measurement in RCTMountingManager using RCTExecuteOnMainQueue with native view hierarchy measurement
Android: Implements async measurement through FabricUIManager → MountingManager using MountItem dispatch to UI thread, with native view hierarchy measurement via bounding box computation

Also removes the createPressHandler workaround (which used onPressIn instead of onPress on Android) since this patch properly fixes the root cause.

Fixed Issues

$ #59953

Tests

Open the app on an Android device (ideally a Samsung Galaxy Z Fold 4 or similar affected device)
Sign in to a new account or one that triggers product training tooltips
When a tooltip appears (e.g., near the Concierge chat), tap the X button to dismiss it
Verify the tooltip dismisses on tap (onPress fires correctly)
If action button tooltips appear, verify "Try it out" and "No thanks" buttons work

Verify that no errors appear in the JS console

Offline tests

Same as tests - tooltip dismissal is a local UI interaction and should work identically offline.

QA Steps

On an Android device (preferably Samsung Galaxy Z Fold 4 / Android 14), sign in to an account
Trigger a product training tooltip (new account or cleared tooltip state)
Verify the X button on the tooltip is tappable and dismisses the tooltip
Verify other Pressable components inside tooltips work correctly

Verify that no errors appear in the JS console

PR Author Checklist

Screenshots/Videos

Android: Native

This bug requires a specific Samsung device (e.g., Galaxy Z Fold 4) to reproduce. The patch is based on the upstream react-native fix.

Android: mWeb Chrome

N/A - This is a native-only issue (Fabric/new arch)

iOS: Native

N/A - This is an Android-specific issue

iOS: mWeb Safari

N/A - This is an Android-specific issue

MacOS: Chrome / Safari

N/A - This is an Android-specific issue

Add react-native patch based on upstream PR react/react-native#51835 to fix Android-specific issue where onPress events do not trigger for Pressable components when used inside a Tooltip on certain Samsung devices. Also removes the createPressHandler workaround since this patch properly fixes the root cause. Co-authored-by: Linh Vo <linhvovan29546@users.noreply.github.com>

codecov · 2026-03-24T02:51:01Z

Codecov Report

✅ Changes either increased or maintained existing code coverage, great job!

Files with missing lines	Coverage Δ
src/components/ProductTrainingContext/index.tsx	`91.22% <0.00%> (ø)`
... and 35 files with indirect coverage changes

linhvovan29546 · 2026-03-24T09:29:02Z

@MelvinBot We're seeing the error _NativeDOM.default.measureAsyncOnUI is not a function on iOS.

MelvinBot · 2026-03-24T09:37:14Z

🔍 Analysis: `_NativeDOM.default.measureAsyncOnUI is not a function` on iOS

Root Cause: The patch is missing a critical file — FBReactNativeSpecJSI.h, the pre-generated C++ codegen header that registers TurboModule methods on iOS.

Why it works on Android but not iOS

On iOS, React Native deliberately skips codegen for FBReactNativeSpec when pre-generated files already exist in node_modules (shouldSkipGenerationForFBReactNativeSpec):

function shouldSkipGenerationForFBReactNativeSpec(schemaInfo, platform) {
  if (platform !== 'ios' || ...) return false;
  // If the pre-generated files exist in node_modules → SKIP codegen
  return (path.includes('node_modules') && fs.existsSync(...) && fs.readdirSync(...).length > 0);
}

This means the pre-generated FBReactNativeSpecJSI.h (shipped in the npm package) is used as-is on iOS, even though the JS spec (NativeDOM.js) was patched to include measureAsyncOnUI.

On Android, codegen always re-runs from the patched JS specs at Gradle build time, so measureAsyncOnUI gets properly registered.

Error chain

Pressability.js checks typeof this._responderID.measureAsyncOnUI === 'function' → TRUE (it's a JS class method on ReactNativeElement, added by the patch)
ReactNativeElement.measureAsyncOnUI() calls NativeDOM.measureAsyncOnUI(node, callback) — no guard on the native method
The iOS TurboModule looks up measureAsyncOnUI in its methodMap_ → NOT FOUND (because FBReactNativeSpecJSI.h was not patched and still has only the original 21 methods)
Returns undefined → calling undefined() throws: _NativeDOM.default.measureAsyncOnUI is not a function

Fix

The patch needs to also modify FBReactNativeSpecJSI.h to add:

A measureAsyncOnUI entry in the NativeDOMCxxSpec constructor's methodMap_ (around line 5791-5813)
A corresponding static __hostFunction_NativeDOMCxxSpec_measureAsyncOnUI invoker function that bridges JS to the C++ measureAsyncOnUI implementation using AsyncCallback

Alternatively, as a simpler defensive fix, add a guard in ReactNativeElement.measureAsyncOnUI to fall back to measure() when the native method doesn't exist:

measureAsyncOnUI(callback: MeasureOnSuccessCallback) {
  const node = getNativeElementReference(this);
  if (node != null) {
    if (typeof NativeDOM.measureAsyncOnUI === 'function') {
      NativeDOM.measureAsyncOnUI(node, callback);
    } else {
      NativeDOM.measure(node, callback);
    }
  }
}

However, the proper fix is patching FBReactNativeSpecJSI.h so the native method is actually registered.

Key files

FBReactNativeSpecJSI.h:5791-5813 — Pre-generated NativeDOMCxxSpec constructor with methodMap_ (missing measureAsyncOnUI)
scripts/codegen/generate-artifacts-executor/generateNativeCode.js:80-101 — shouldSkipGenerationForFBReactNativeSpec skip logic
ReactNativeElement.js (patched) — Calls NativeDOM.measureAsyncOnUI without checking existence
TurboModule.h:117-137 — Returns undefined for methods not in methodMap_

linhvovan29546 · 2026-03-24T09:58:54Z

@MelvinBot please apply the fix

… methodMap_ On iOS, codegen for FBReactNativeSpec is skipped when pre-generated files exist in node_modules. The original patch modified NativeDOM.js and the C++ implementation but did not update the pre-generated FBReactNativeSpecJSI.h, causing measureAsyncOnUI to be undefined at runtime on iOS. This commit: 1. Patches FBReactNativeSpecJSI.h to add measureAsyncOnUI to the NativeDOMCxxSpec methodMap_ and adds the static invoker function 2. Adds a defensive typeof guard in ReactNativeElement.measureAsyncOnUI to fall back to regular measure() if the native method is unavailable Co-authored-by: Linh Vo <linhvovan29546@users.noreply.github.com>

MelvinBot · 2026-03-24T10:04:27Z

Fixed the iOS _NativeDOM.default.measureAsyncOnUI is not a function error in db16d63.

Changes:

Patched FBReactNativeSpecJSI.h — Added measureAsyncOnUI to the NativeDOMCxxSpec constructor's methodMap_ and added the corresponding __measureAsyncOnUI static invoker function. This is the critical fix: on iOS, codegen is skipped for FBReactNativeSpec when pre-generated files exist in node_modules, so the original patch's changes to NativeDOM.js (the Flow spec) were never picked up. The pre-generated header needed to be patched directly.
Added defensive guard in ReactNativeElement.measureAsyncOnUI — Now checks typeof NativeDOM.measureAsyncOnUI === 'function' before calling it, falling back to NativeDOM.measure() if unavailable. This provides a safety net in case the native method isn't registered for any reason.

Please rebuild the iOS app and verify the error is resolved.

linhvovan29546 · 2026-03-24T10:21:31Z

@MelvinBot The workflows failing

The second hunk of the FBReactNativeSpecJSI.h section had a line count mismatch in its @@ header (declared 6 old/15 new but only contained 5 old/14 new lines), causing patch-package to fail with a parse error during npm postinstall. Co-authored-by: Linh Vo <linhvovan29546@users.noreply.github.com>

MelvinBot · 2026-03-24T10:22:11Z

Fixed the failing checks: the react-native+0.83.1+034+fix-pressability-new-arch.patch file had a hunk header line count mismatch in the FBReactNativeSpecJSI.h section. The second hunk's @@ header declared 6 old/15 new lines but only contained 5 old/14 new lines, causing patch-package to fail with a parse error during npm postinstall. Corrected the header to @@ -5984,5 +5985,14 @@. This was the root cause of all CI failures (ESLint, Prettier, typecheck, tests, builds, etc.) since they all depend on npm install succeeding.

MelvinBot · 2026-03-24T10:22:49Z

I checked the workflow status. The only failing check is PR Author Checklist / checklist, which is expected and not a real failure — it's an informational check.

All other checks (ESLint, typecheck, tests, builds, etc.) are still pending — they're currently running. There are no actual failures to fix yet.

If any checks fail after they complete, feel free to tag me again and I'll investigate.

MelvinBot · 2026-03-24T10:24:26Z

The previous check failures (TypeScript, ESLint, unused styles) were all caused by the same issue: the patch file react-native+0.83.1+034+fix-pressability-new-arch.patch could not be parsed by patch-package during npm install.

This was already fixed in commit 03df1b7 ("Fix: correct hunk line count in react-native pressability patch"). The latest CI run shows all checks are now passing — ESLint, Changed files ESLint, unused styles, Prettier, validate-patches, and builds are all green. Tests and typecheck are still running but should pass since the underlying patch parsing issue is resolved.

The only failing check is checklist (PR Author Checklist), which is unrelated to the code.

github-actions · 2026-03-24T11:40:10Z

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

linhvovan29546 · 2026-03-25T09:17:45Z

@MelvinBot Please make this PR ready for review!

MelvinBot · 2026-03-25T09:20:32Z

I attempted to mark this PR as ready for review, but the command was blocked by my permission settings. You can mark it ready yourself using the GitHub UI (click "Ready for review" at the bottom of the PR) or by running:

gh pr ready 86160 --repo Expensify/App

Reminder: There is a known iOS issue (_NativeDOM.default.measureAsyncOnUI is not a function) that I analyzed in a previous comment. The patch is missing the FBReactNativeSpecJSI.h codegen header update needed for iOS. This should be addressed before merging.

linhvovan29546 · 2026-03-25T09:28:23Z

@MelvinBot Please mark it as "Ready for review"

melvin-bot · 2026-03-25T09:30:08Z

@linhvovan29546 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]

MelvinBot · 2026-03-25T09:30:17Z

PR has been marked as Ready for review as requested.

melvin-bot · 2026-03-25T09:30:45Z

@Valforte 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]

linhvovan29546 · 2026-03-25T09:35:30Z

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
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 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

2026-03-25.16.32.23.mp4

Android: mWeb Chrome

Screen.Recording.2026-03-25.at.16.34.35.mov

iOS: HybridApp

Screen.Recording.2026-03-25.at.16.31.43.mov

iOS: mWeb Safari

Screen.Recording.2026-03-25.at.16.32.55.mov

MacOS: Chrome / Safari

Screen.Recording.2026-03-25.at.16.35.11.mov

linhvovan29546 · 2026-03-25T09:39:41Z

@MelvinBot Please complete PR Author Checklist

linhvovan29546

NAB: #86160 (comment)

trjExpensify

Patch PR 👍

MelvinBot · 2026-03-26T15:12:42Z

All checks on this PR are currently passing. There are no failing checks to fix — every check shows either pass or skipping (expected for conditional checks). The previously failing checks may have been resolved by a prior push or were transient.

github-actions · 2026-03-26T15:18:18Z

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

github-actions · 2026-03-26T15:24:09Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-95e522a-3063164-d1443296f91b9af0d96cf759e96e3ccf9d4bbb73/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-95e522a-3063164-62fec11c9b2d2531c8dcd405eaf337042fb5edeb/index.html

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

👀 View the workflow run that generated this build 👀

OSBotify · 2026-03-26T15:25:58Z

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

OSBotify · 2026-03-27T12:51:55Z

🚀 Deployed to staging by https://github.com/Valforte in version: 9.3.50-0 🚀

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

Bundle Size Analysis (Sentry):

Android
iOS

MelvinBot · 2026-03-27T12:53:11Z

No help site changes are required for this PR.

This PR is an internal bug fix that patches React Native's native touch measurement system (measureAsyncOnUI) and removes a workaround (createPressHandler). The changes are entirely under-the-hood:

A new react-native patch for native view measurement on the UI thread
Removal of the onPressIn workaround for Android pressability
Simplification of ProductTrainingContext to use onPress directly

There are no changes to user-facing features, workflows, UI labels, settings, or product behavior that would require documentation updates in docs/articles/.

IuliiaHerets · 2026-03-27T18:31:17Z

Hi @MelvinBot. Unfortunately, the QA team doesn’t have a Samsung Galaxy Z Fold 4 or a similar affected device. How can we test this in that case?

cc @Valforte @trjExpensify

linhvovan29546 · 2026-03-27T22:49:04Z

@IuliiaHerets Just a Samsung device

IuliiaHerets · 2026-03-28T13:40:21Z

@linhvovan29546 QA team tried with 2 Samsung devices.
Samsung A31 and Samsung Galaxy A40 - The X option does not appear in the tooltip popup, but the “Try it out” / “No thanks” options do appear, and the tooltip closes when selecting either option.

Please let me know if this result can be considered a pass.

WhatsApp.Video.2026-03-28.at.9.14.46.AM.mp4

MicrosoftTeams-video.34.mp4

linhvovan29546 · 2026-03-28T13:42:57Z

@IuliiaHerets yes

linhvovan29546 · 2026-03-31T04:45:50Z

@MelvinBot The PR was reverted, please open a new PR containing the same changes.

MelvinBot · 2026-03-31T04:54:24Z

🤖 New draft PR created: #86707

This contains the same changes as this PR, re-applied on top of current main. Please mark it as "Ready for review" when ready.

OSBotify · 2026-03-31T21:51:45Z

🚀 Deployed to production by https://github.com/jasperhuangg in version: 9.3.50-8 🚀

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

Re-apply the changes from PR #86160 which was reverted. Adds a react-native patch based on upstream react/react-native#51835 to fix onPress events not triggering for Pressable components inside Tooltips on certain Samsung devices. Also removes the createPressHandler workaround since this patch properly fixes the root cause.

MelvinBot assigned linhvovan29546 Mar 24, 2026

MelvinBot requested a review from a team March 24, 2026 02:43

MonilBhavsar added the Ready To Build label Mar 24, 2026

This comment has been minimized.

Sign in to view

MelvinBot marked this pull request as ready for review March 25, 2026 09:30

MelvinBot requested a review from a team as a code owner March 25, 2026 09:30

melvin-bot Bot requested review from linhvovan29546 and trjExpensify and removed request for a team March 25, 2026 09:30

melvin-bot Bot requested a review from a team March 25, 2026 09:30

melvin-bot Bot requested a review from Valforte March 25, 2026 09:30

melvin-bot Bot removed the request for review from a team March 25, 2026 09:30

linhvovan29546 approved these changes Mar 25, 2026

View reviewed changes

trjExpensify approved these changes Mar 26, 2026

View reviewed changes

Valforte approved these changes Mar 26, 2026

View reviewed changes

Valforte merged commit 95e522a into main Mar 26, 2026
52 of 55 checks passed

Valforte deleted the claude-fixPressabilityNewArch-v3 branch March 26, 2026 15:16

OSBotify mentioned this pull request Mar 27, 2026

Deploy Checklist: New Expensify 2026-03-27 #86530

Closed

86 tasks

jasperhuangg mentioned this pull request Mar 31, 2026

[CP staging] Revert "fix: android pressability issue with measureAsyncOnUI patch" #86701

Merged

MelvinBot mentioned this pull request Mar 31, 2026

fix: android pressability issue with measureAsyncOnUI patch #86707

Closed

52 tasks

MelvinBot mentioned this pull request Mar 31, 2026

[Due for payment 2026-04-14] [Due for payment 2026-04-07] [$375] Android: Investigate and fix onPress not working for Pressable in Tooltip #59953

Closed

linhvovan29546 mentioned this pull request Mar 31, 2026

fix: android pressability issue with measureAsyncOnUI patch (v5) #86708

Merged

52 tasks

Conversation

MelvinBot commented Mar 24, 2026 • edited by Valforte 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!

codecov Bot commented Mar 24, 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!

linhvovan29546 commented Mar 24, 2026

Uh oh!

MelvinBot commented Mar 24, 2026

🔍 Analysis: _NativeDOM.default.measureAsyncOnUI is not a function on iOS

Why it works on Android but not iOS

Error chain

Fix

Uh oh!

linhvovan29546 commented Mar 24, 2026

Uh oh!

MelvinBot commented Mar 24, 2026

Uh oh!

linhvovan29546 commented Mar 24, 2026

Uh oh!

MelvinBot commented Mar 24, 2026

Uh oh!

MelvinBot commented Mar 24, 2026

Uh oh!

MelvinBot commented Mar 24, 2026

Uh oh!

github-actions Bot commented Mar 24, 2026

Uh oh!

This comment has been minimized.

linhvovan29546 commented Mar 25, 2026

Uh oh!

MelvinBot commented Mar 25, 2026

Uh oh!

linhvovan29546 commented Mar 25, 2026

Uh oh!

melvin-bot Bot commented Mar 25, 2026

Uh oh!

MelvinBot commented Mar 25, 2026

Uh oh!

melvin-bot Bot commented Mar 25, 2026

Uh oh!

linhvovan29546 commented Mar 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

linhvovan29546 commented Mar 25, 2026

Uh oh!

linhvovan29546 left a comment

Choose a reason for hiding this comment

Uh oh!

trjExpensify left a comment

Choose a reason for hiding this comment

Uh oh!

MelvinBot commented Mar 26, 2026

Uh oh!

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

github-actions Bot commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 26, 2026

Uh oh!

OSBotify commented Mar 27, 2026

Uh oh!

MelvinBot commented Mar 27, 2026

Uh oh!

IuliiaHerets commented Mar 27, 2026

Uh oh!

linhvovan29546 commented Mar 27, 2026

Uh oh!

MelvinBot commented Mar 24, 2026 •

edited by Valforte

Loading

codecov Bot commented Mar 24, 2026 •

edited by github-actions Bot

Loading

🔍 Analysis: `_NativeDOM.default.measureAsyncOnUI is not a function` on iOS

linhvovan29546 commented Mar 25, 2026 •

edited

Loading