[CP Staging] Revert "Merge pull request #83899 from software-mansion-labs/collecti…

[srikarparsi]

…oneur/transition-tracker-v2"

This reverts commit c4d00e1

Explanation of Change

Fixed Issues

$ #85687
$ #85696
PROPOSAL:

Tests

• 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

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover 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 tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I followed proper code patterns (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
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • 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 followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• 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
• I verified that if a function's arguments changed that all usages have also been updated correctly
• 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 new assets were added or existing ones were modified, I verified that:
  • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
  • The assets load correctly across all supported platforms.
• 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.
• I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user 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.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

[melvin-bot]

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

[Pujan92]

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 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 the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
  • 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.js 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.
• 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: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

Screen.Recording.2026-03-19.at.01.27.57.mov

[Pujan92]

@srikarparsi can you plz run adhoc build here so I can verify android issue are fixed on physical device

[srikarparsi]

Yes

[github-actions]

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

[srikarparsi]

@MelvinBot can you please review this PR. It intends to revert c4d00e1 without causing regressions

[Pujan92]

LGTM!

Record_2026-03-19-01-39-51.mp4

[melvin-bot]

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

[srikarparsi]

And could you check if this bug is fixed too with the physical device?

[MelvinBot]

PR Review: Revert of TransitionTracker V2

I've reviewed the full diff against the original commit (c4d00e1) and the linked regression issues (#85687, #85696). Here's my analysis.

What this PR does

This is not a naive git revert. The TransitionTracker PR (#83899) introduced new APIs (afterTransition, waitForTransition) that were adopted by several callers. A pure revert would break those callers, so this PR provides equivalent alternatives:

Original (TransitionTracker)	Replacement in this PR
dismissModal({afterTransition: cb})	dismissModal({callback: cb}) via DeviceEventEmitter
KeyboardUtils.dismiss({afterTransition: cb})	Keyboard.dismiss() + InteractionManager.runAfterInteractions(cb) or direct navigation
navigate(route, {waitForTransition: true})	Direct navigate(route) (synchronous)
goBack(route, {waitForTransition, afterTransition})	Direct goBack(route)

Completeness check

All files referencing TransitionTracker, afterTransition, and waitForTransition on main are covered by this PR:

• TransitionTracker.ts — deleted
• ScreenLayout.tsx — deleted
• INTERACTION_MANAGER.md — deleted
• Navigation.ts — fully reverted with DeviceEventEmitter-based callback
• ReanimatedModal/index.tsx — TransitionTracker calls removed
• All three keyboard platform files — reverted to simple signatures
• All page-level callers (NewChatPage, WorkspaceCategoriesSettingsPage, WorkspaceCreateTagPage, WorkspaceInviteMessageComponent, TransactionReceiptModalContent, Report/index.ts) — updated
• Tests — removed TransitionTracker tests, updated keyboard tests
• LinkToOptions type — cleaned up (removed afterTransition/waitForTransition)

No orphaned references remain. CI confirms: typecheck passes, all tests pass, lint passes.

Assessment of the replacement patterns

1. dismissModal callback via DeviceEventEmitter — Good approach

BaseModal.tsx and RightModalNavigator.tsx emit CONST.MODAL_EVENTS.CLOSED on unmount. dismissModal registers a one-time listener that fires the callback and self-removes. This is simpler than TransitionTracker and still correctly waits for the modal to close.

Minor note: if dismissModal({callback}) is called but the modal doesn't actually unmount (edge case), the listener would leak. In practice this shouldn't happen since the dismiss action is dispatched immediately after.

2. dismissModalWithReport using InteractionManager.runAfterInteractions — Acceptable

This reintroduces the deprecated InteractionManager API, but since this revert is specifically undoing the migration away from it, that's the expected trade-off. It's marked with the deprecation eslint-disable comment.

3. TransactionReceiptModalContent native-specific branch — Worth verifying

This introduces a new platform-specific path for native that uses goBack() + setNavigationActionToMicrotaskQueue() instead of dismissModal({callback}). This is a new pattern that wasn't in the original pre-TransitionTracker code. I'd recommend verifying the receipt replace flow works on both iOS and Android with this change.

4. WorkspaceCreateTagPage keyboard + immediate navigation — Low risk

Keyboard.dismiss() followed by immediate Navigation.goBack() without waiting for the keyboard to hide. This should be fine since the navigation transition will naturally handle the keyboard, but it's a behavioral change from the TransitionTracker version which waited.

Verdict

This PR looks good to merge. It cleanly reverts the TransitionTracker infrastructure while providing working alternatives for all callers. The linked regressions (Android chat not opening after FAB, Android receipt replace broken) are serious enough to justify the revert.

The only check failure is PR Author Checklist / checklist, which is ignorable.

[Pujan92]

And could you check if this bug is fixed too with the physical device?

Done..

Record_2026-03-19-01-48-21.mp4

[srikarparsi]

Awesome, thanks @Pujan92

[codecov]

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 Δ
src/CONST/index.ts	93.60% <ø> (ø)
src/components/Modal/BaseModal.tsx	86.50% <100.00%> (+0.10%)	⬆️
src/components/Modal/ReanimatedModal/index.tsx	53.39% <ø> (+0.62%)	⬆️
...tePlatformStackNavigatorComponent/index.native.tsx	100.00% <ø> (ø)
...on/createPlatformStackNavigatorComponent/index.tsx	0.00% <ø> (ø)
src/pages/NewChatPage.tsx	73.40% <ø> (ø)
...ace/categories/WorkspaceCategoriesSettingsPage.tsx	0.00% <ø> (ø)
src/utils/keyboard/index.android.ts	96.77% <100.00%> (+2.32%)	⬆️
src/utils/keyboard/index.ts	95.23% <100.00%> (-0.92%)	⬇️
src/components/EmojiPicker/EmojiPicker.tsx	45.26% <0.00%> (ø)
... and 7 more
... and 9 files with indirect coverage changes

[github-actions]

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

[github-actions]

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-b46f4b6-d361e22-8e2e8dbbe73f9e784eb6a358ed2f2728a2cd8211/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-b46f4b6-d361e22-d5d8691387aa9578f1a417418f8e0e7747084c07/index.html

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

---

👀 View the workflow run that generated this build 👀

[OSBotify]

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

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 9.3.40-3 🚀

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

[OSBotify]

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 9.3.40-10 🚀

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

[OSBotify]

🚀 Cherry-picked to staging by https://github.com/francoisl in version: 9.3.41-0 🚀

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

Bundle Size Analysis (Sentry):

• Android
• iOS

[OSBotify]

🚀 Deployed to production by https://github.com/cristipaval in version: 9.3.41-4 🚀

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