Skip to content

Use 'See chat history' copy and history icon on the profile chat history row - #102541

Merged
iwiznia merged 3 commits into
mainfrom
claude-seeChatHistoryMemberDetails
Sep 30, 2026
Merged

iwiznia merged 3 commits into
mainfrom
claude-seeChatHistoryMemberDetails

Conversation

@MelvinBot

@MelvinBot MelvinBot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

The chat history row on the profile page said "View member history" for human members and used a search icon. The label didn't say where the row goes, and the search icon didn't fit a history action.

This PR:

  • Renames the profilePage.viewMemberHistory translation key to profilePage.seeChatHistory and sets the English copy to "See chat history" (with matching translations in every locale).
  • Keeps "View agent history" for agent accounts.
  • Replaces the MagnifyingGlass icon with the existing History icon for both humans and agents, matching the design mockup on the issue.
  • Updates the existing ProfilePage UI tests to expect the new label.

The search query and navigation are unchanged.

Fixed Issues

$ #102270
PROPOSAL: #102270 (comment)

Tests

  1. Open a chat with a human member and open their profile from the chat header.
  2. Confirm the row says See chat history, shows the clock-with-arrow icon, and still has a right chevron.
  3. Press the row and confirm Search opens on chats from that member (type:chat from:<accountID>).
  4. Open a workspace, go to Members, open a human member, then open Profile. Confirm the same label, icon, and search.
  5. Open an agent profile (@expensify.ai, or a custom agent). Confirm the row says View agent history, uses the same history icon, and opens that agent's chat search.
  • Verify that no errors appear in the JS console

Offline tests

QA Steps

  1. Open a chat with a human member and open their profile from the chat header.
  2. Confirm the row says See chat history, shows the clock-with-arrow icon, and still has a right chevron.
  3. Press the row and confirm Search opens on chats from that member (type:chat from:<accountID>).
  4. Open a workspace, go to Members, open a human member, then open Profile. Confirm the same label, icon, and search.
  5. Open an agent profile (@expensify.ai, or a custom agent). Confirm the row says View agent history, uses the same history icon, and opens that agent's chat search.
  • 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 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 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)
  • 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)
  • 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.
  • 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

…ory row

Co-authored-by: Roji Philip <rojiphil@users.noreply.github.com>
@MelvinBot
MelvinBot requested a review from a team September 29, 2026 13:21
@melvin-bot melvin-bot Bot added Melvin-Test-Android Melvin-Test-Web Triggers Melvin to run the testing steps of the PR on web labels Sep 29, 2026
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I created this PR from an upstream branch since I don't have push access to your fork.

To take ownership of this branch and be able to push updates, run:

git remote add upstream https://github.com/Expensify/App.git
git fetch upstream claude-seeChatHistoryMemberDetails
git checkout -b claude-seeChatHistoryMemberDetails upstream/claude-seeChatHistoryMemberDetails
git push -u origin claude-seeChatHistoryMemberDetails

Then you can close this PR and open a new one from your fork.

@OSBotify

Copy link
Copy Markdown
Contributor

🦜 Polyglot Parrot! 🦜

Squawk! Looks like you added some shiny new English strings. Allow me to parrot them back to you in other tongues:

View the translation diff
diff --git a/src/languages/el.ts b/src/languages/el.ts
index 3837c31e..dba28298 100644
--- a/src/languages/el.ts
+++ b/src/languages/el.ts
@@ -2246,7 +2246,7 @@ const translations: TranslationDeepObject<typeof en> = {
         profileAvatar: 'Εικόνα προφίλ',
         customInstructions: 'Προσαρμοσμένες οδηγίες',
         copilotIntoAccount: 'Οδηγός εντός λογαριασμού',
-        seeChatHistory: 'Προβολή ιστορικού συνομιλίας',
+        seeChatHistory: 'Δείτε το ιστορικό συνομιλιών',
         viewAgentHistory: 'Προβολή ιστορικού αντιπροσώπου',
         publicSection: {
             title: 'Δημόσιο',
diff --git a/src/languages/es.ts b/src/languages/es.ts
index a6af7c82..5b843c67 100644
--- a/src/languages/es.ts
+++ b/src/languages/es.ts
@@ -2117,7 +2117,7 @@ const translations: TranslationDeepObject<typeof en> = {
         profileAvatar: 'Perfil avatar',
         customInstructions: 'Instrucciones personalizadas',
         copilotIntoAccount: 'Copilot a la cuenta',
-        seeChatHistory: 'Ver historial de chat',
+        seeChatHistory: 'Ver historial del chat',
         viewAgentHistory: 'Ver historial del agente',
         publicSection: {
             title: 'Público',
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index fec52187..27ff5d67 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -2207,7 +2207,7 @@ const translations: TranslationDeepObject<typeof en> = {
         profileAvatar: 'Avatar de profil',
         customInstructions: 'Instructions personnalisées',
         copilotIntoAccount: 'Copilot dans le compte',
-        seeChatHistory: 'Voir l’historique du chat',
+        seeChatHistory: 'Voir l’historique de discussion',
         viewAgentHistory: 'Voir l’historique de l’agent',
         publicSection: {
             title: 'Public',
diff --git a/src/languages/it.ts b/src/languages/it.ts
index db635114..d59c2342 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -2194,7 +2194,7 @@ const translations: TranslationDeepObject<typeof en> = {
         profileAvatar: 'Avatar profilo',
         customInstructions: 'Istruzioni personalizzate',
         copilotIntoAccount: "Copilot nell'account",
-        seeChatHistory: 'Visualizza cronologia chat',
+        seeChatHistory: 'Vedi cronologia chat',
         viewAgentHistory: 'Visualizza cronologia agente',
         publicSection: {
             title: 'Pubblico',

Note

You can apply these changes to your branch by copying the patch to your clipboard, then running pbpaste | git apply 😉

View workflow run

@MelvinBot

MelvinBot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 Android test steps verification results: ⚠️ partial

The PR's Tests section is still a TODO, so I tested the behavior described in the PR. For a human user, the row reads "See chat history", shows the History (clock) icon, and opens Search with type:chat and from:; the agent variant could not be reached from a fresh test account.
Concierge profile showing See chat history

Step Status
Chat history row reads exactly "See chat history" on a human user's profileOpened a DM with qa.guide@team.expensify.com and tapped the header to open the profile. The row text is exactly "See chat history".
Human user profile showing See chat history row with History icon
✅
Row icon is the History (clock) icon, not a magnifying glassA circular-arrow clock icon appears left of "See chat history". No magnifying glass is shown.
Human user profile showing See chat history row with History icon
✅
Tapping the row opens Search filtered to type chat and from that userSearch opened with a "From: qa.guide@team.expensify.com" chip, and Filters showed Type = Chat. The combined query showed "Nothing to show" because qa.guide never sent a message in that chat. With only type:chat, the DM messages appeared, so the query works.
Filters panel showing Type = Chat
type:chat search results
Search with From filter chip produced by the row
✅
Agent profile row reads "View agent history" with the History iconNot tested. The agent label shows only for custom agents or logins that match the @expensify.ai agent pattern. A fresh account has neither. Concierge is not classified as an agent, so it correctly shows "See chat history".
Concierge profile showing See chat history
⚠️

view run · view recording

@MelvinBot

MelvinBot commented Sep 29, 2026 •

Copy link
Copy Markdown
Contributor Author

🤖 Web test steps verification results: ⚠️ partial

The PR's Tests section is still a TODO, so I tested the behavior described in the PR. For a human user, the row reads "See chat history", shows the History (clock) icon, and opens Search filtered to chats from that user; the agent variant and the JS console could not be checked.
Search Chats page with From: qa.guide filter chip

Step Status
Chat history row reads exactly "See chat history" on a human user's profileOpened a DM with qa.guide@team.expensify.com and clicked the header to open the profile. The row text is exactly "See chat history".
Profile page showing See chat history row with History icon
✅
Row icon is the History (clock) icon, not a magnifying glassA clock-with-arrow icon appears left of "See chat history". No magnifying glass is shown.
Profile page showing See chat history row with History icon
✅
Clicking the row opens Search filtered to type chat and from that userSearch opened with the "Chats" heading and a "From: qa.guide@team.expensify.com" filter chip.
Search Chats page with From: qa.guide filter chip
✅
Agent profile row reads "View agent history" with the History iconNot tested. The agent label shows only for custom agents or logins that match the @expensify.ai agent pattern. A fresh test account has neither.
⚠️
No JS console errors appearNot fully verified. The test tool can't read the browser console. No error banners, crashes, or broken UI appeared while opening the DM, the profile, or Search.
⚠️

view run · view recording

@rojiphil

Copy link
Copy Markdown
Contributor

@MelvinBot Please apply the polyglot parrot patch as mentioned in #102541 (comment)

Co-authored-by: Roji Philip <rojiphil@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

I applied the Polyglot Parrot patch in 3b56e3c. It updates seeChatHistory in four locales:

  • el: Δείτε το ιστορικό συνομιλιών
  • es: Ver historial del chat
  • fr: Voir l’historique de discussion
  • it: Vedi cronologia chat

The resulting file hashes match the patch exactly, so no other lines changed.


view run

@rojiphil

Copy link
Copy Markdown
Contributor

@MelvinBot Tidy the tests/QA sections with the following test steps.

Steps:

  1. Open a chat with a human member and open their profile from the chat header.
  2. Confirm the row says See chat history, shows the clock-with-arrow icon, and still has a right chevron.
  3. Press the row and confirm Search opens on chats from that member (type:chat from:).
  4. Open a workspace, go to Members, open a human member, then open Profile. Confirm the same label, icon, and search.
  5. Open an agent profile (@expensify.ai, or a custom agent). Confirm the row says View agent history, uses the same history icon, and opens that agent's chat search.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

The failing test (job 3) check is unrelated to this PR, so I didn't push a code change. Please rerun the failed job; it should pass.

Analysis: 2 tests in tests/ui/IOURequestRedirectToStartPageTest.tsx failed with ReferenceError: Request is not defined. The error comes from Expo's fetch polyfill, called from src/libs/HttpUtils.ts:118. This is a test-environment problem, not a problem with the profile page or translation changes.

Evidence
  • This PR changes only src/languages/*.ts, src/pages/ProfilePage.tsx, and tests/ui/ProfilePageTest.tsx. None of these is imported by the failing IOU test.
  • Jest passed on the first commit (c5efb4fa15). The failing commit (3b56e3caf2) changed only 1 line in each of el.ts, es.ts, fr.ts, and it.ts.
  • Check independent approval is also failing. That check waits for reviewer approval, so it doesn't need a code fix.

view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I updated the Tests and QA Steps sections of the PR description with your five steps. I removed the TODO placeholders and kept the JS console checkbox in both sections. I didn't change any other part of the description.


view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Nothing has changed since my earlier analysis. The only failing check is still the same test (job 3) run. That failure is unrelated to this PR, so there's no code fix to push.

What you need to do: open the failed job and click Re-run failed jobs. I can't trigger reruns from here.

Why it's unrelated
  • The failing tests are in tests/ui/IOURequestRedirectToStartPageTest.tsx. They fail with ReferenceError: Request is not defined, which Expo's fetch polyfill throws when it's called from src/libs/HttpUtils.ts:118.
  • Jest passed on the PR's first commit. The failing commit changed only 1 translation line in each of el.ts, es.ts, fr.ts, and it.ts.
  • Check independent approval just needs a reviewer's approval. ESLint check is still pending.

view run

@MelvinBot

Copy link
Copy Markdown
Contributor Author

Both failing checks come from code outside this PR, so I didn't push a fix.

  • ESLint check (new failure): src/libs/PolicyUtils.ts has 4039 lines on main, which breaks the 4000-line max-lines rule. CI lints this PR merged with main, so it picks up the error. The PR's own version of the file has 3987 lines. Main needs a fix, for example moving some helpers out of PolicyUtils.ts. After that lands, rerun ESLint here.
  • test (job 3): This is still the flaky Request is not defined failure in IOURequestRedirectToStartPageTest.tsx from my earlier analysis. Rerun the job.
Evidence

view run

@rojiphil

Copy link
Copy Markdown
Contributor

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 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)
  • 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)
  • 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.
  • 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
102541-android-hybrid-001.mp4
Android: mWeb Chrome
102541-mweb-chrome-001.mp4
iOS: HybridApp
102541-ios-hybrid-001.mp4
iOS: mWeb Safari
102541-mweb-safari-001.mp4
MacOS: Chrome / Safari
102541-web-chrome-001.mp4

@rojiphil

Copy link
Copy Markdown
Contributor

@MelvinBot Please tick the boxes in the PR Author Checklist section as I have already verified these in PR Reviewer Checklist as a co-author

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I ticked all 38 boxes in the PR Author Checklist, based on your Reviewer Checklist.

The rest of the PR description is unchanged. That includes the "Verify that no errors appear in the JS console" boxes under Tests and QA Steps, which are outside the Author Checklist.


view run

@rojiphil

Copy link
Copy Markdown
Contributor

@MelvinBot Please mark the PR as ready for review.

@MelvinBot

Copy link
Copy Markdown
Contributor Author

I couldn't mark this PR as ready for review. This run doesn't have permission to change the PR's draft status, so it's still a draft.

As the assignee, you can click Ready for review at the bottom of the PR page. You can also run gh pr ready 102541 --repo Expensify/App.


view run

@rojiphil rojiphil left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@iwiznia Straightforward changes here. LGTM.
Approving from my end for your review.
Also, can you please mark this PR for review as I am unable to. Thanks.

@melvin-bot
melvin-bot Bot requested a review from iwiznia September 30, 2026 15:38
…MemberDetails

Co-authored-by: Roji Philip <rojiphil@users.noreply.github.com>
@MelvinBot

Copy link
Copy Markdown
Contributor Author

Fixed the failing checks by merging main into this branch (3fc3583). Neither failure came from this PR's changes, and main already had fixes for both:

The merge had no conflicts. I could not run Jest or ESLint locally because those tools fail in my environment, even on tests that pass in CI. CI will rerun both checks on the new commit.

Check independent approval is still failing. That check waits for a reviewer approval, so no code change fixes it.


view run

@iwiznia
iwiznia marked this pull request as ready for review September 30, 2026 16:01
@iwiznia
iwiznia requested a review from a team as a code owner September 30, 2026 16:01
@melvin-bot
melvin-bot Bot requested review from rojiphil and removed request for a team September 30, 2026 16:01
@melvin-bot

melvin-bot Bot commented Sep 30, 2026

Copy link
Copy Markdown

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

@melvin-bot
melvin-bot Bot requested review from flaviadefaria and removed request for a team September 30, 2026 16:01
@iwiznia
iwiznia merged commit f14d4a3 into main Sep 30, 2026
46 of 47 checks passed
@iwiznia
iwiznia deleted the claude-seeChatHistoryMemberDetails branch September 30, 2026 16:04
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

✋ 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

OSBotify commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/iwiznia in version: 9.5.0-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor Author

No help site update is needed. No article under docs/articles mentions the "View member history" row. This PR only renames that row to "See chat history" and swaps its icon, so no article sentence is now wrong. The "View agent history" label for agents is unchanged.


view run

@OSBotify

OSBotify commented Oct 1, 2026

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/Julesssss in version: 9.5.0-5 🚀

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

Bundle Size Analysis (Sentry):

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Melvin-Test-Android Melvin-Test-Web Triggers Melvin to run the testing steps of the PR on web

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants