NavigationTabBar: Add dummy component #63242

kacper-mikolajczak · 2025-06-02T10:41:58Z

Explanation of Change

Fixed Issues

$ #63244
PROPOSAL:

Tests

Switch between screens and see how bottom tabs behaves
It should remain interactive
It should remain consistent during transitions

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
- MacOS: Desktop
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 verified there are no new alerts related to the canBeMissing param for useOnyx
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 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

MacOS: Desktop

kacper-mikolajczak · 2025-06-02T11:32:38Z

Problem

NavigationTabBar apart from original its original render target TopLevelTabBar, is used in multiple components to work around existing transitions/animations issues:

SearchSidebar
BaseSidebarScreen
SearchPageNarrow
InitialSettingsPage
WorkspaceInitialPage
WorkspacesListPage

Those components are some of the most commonly used in the app, making NavigationTabBar be re-created at many user interactions and navigations.

Currently the cost of mounting NavigationTabBar on many interactions was measured to be:

~100ms iOS simulator
~20ms Web

Solution

Implement NavigationTabBarDummy which skips heavy parts and exposes only a UI component that resembles actual navigator. It can be done due to the fact that those doppelgangers are not responsible of handling logic and exist solely for fixing animations (source).

Potential cost of mounting NavigationTabBarDummy on many interactions was measured to be:

~25ms iOS simulator -> 25% of original duration
~5ms Web -> 25% of original duration

Platform	Before	After
Web	web-before.mp4	web-after.mp4
iOS	ios-before.mp4	ios-after.mp4

mountiny

This looks promising, @adamgrzybowski @WojtekBoman any concerns with such approach as at least some sort of improvement?

mountiny · 2025-06-02T11:46:47Z

src/components/Navigation/NavigationTabBar/NavigationTabBarDummy.tsx

+        return <NavigationTabBarNarrowDummy selectedTab={selectedTab} />;
+    }
+
+    return <NavigationTabBarWideDummy selectedTab={selectedTab} />;


In which case do we need this in the Wide layout? Could we not render this at all in wide?

Great question! It is there to make dummy counterpart 1:1 match with regular component, but we can investigate it further to see how it behaves on wider screens 👍

If we want to see the navigation bar under the overlay (the one from RHP), we need to render it per screen on the wide layout. The top level is displayed over everything else. It wouldn't be covered by the overlay.

mountiny · 2025-06-02T11:51:21Z

@ishpaul777 will you be able to review?

ishpaul777 · 2025-06-02T12:08:12Z

yes i can review @mountiny

melvin-bot · 2025-06-02T12:33:40Z

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

adamgrzybowski · 2025-06-02T13:24:25Z

src/components/Navigation/NavigationTabBar/NavigationTabBarDummy.tsx

+                <EducationalTooltip
+                    shouldRender={false}
+                    anchorAlignment={{
+                        horizontal: isWebOrDesktop ? CONST.MODAL.ANCHOR_ORIGIN_HORIZONTAL.CENTER : CONST.MODAL.ANCHOR_ORIGIN_HORIZONTAL.LEFT,
+                        vertical: CONST.MODAL.ANCHOR_ORIGIN_VERTICAL.BOTTOM,
+                    }}
+                    shiftHorizontal={isWebOrDesktop ? 0 : variables.navigationTabBarInboxTooltipShiftHorizontal}
+                    renderTooltipContent={noop}
+                    wrapperStyle={styles.productTrainingTooltipWrapper}
+                    shouldHideOnNavigate={false}
+                    onTooltipPress={noop}
+                >


Tooltips are displayed only on the top level so we don't need them for the dummy componenent

Removed, thanks! ✅

WojtekBoman · 2025-06-02T13:33:16Z

I don't know if it's a problem, but I noticed one UI change
When RHP is shown, RBR/GBR disappear from the navigation tab bar

Screen.Recording.2025-06-02.at.15.29.12.mov

kacper-mikolajczak · 2025-06-02T14:01:14Z

When RHP is shown, RBR/GBR disappear from the navigation tab bar

Thanks for spotting this @WojtekBoman! It is unfortunately a tradeoff of not including responsible logic in order to make dummy component as simple as it gets - we'd need to pretty much go back to what full blown navigator consist of - ordered reports, report attributes etc.

With that said, let me know what you think @mountiny @ishpaul777

tl;dr; this part of the UI consistency requires heavy logic to be plugged in

kacper-mikolajczak · 2025-06-02T14:04:53Z

As @mountiny suggested, I am thinking whether we need those duplicates on wide screen at all - @adamgrzybowski do you know if wide screen UI also suffers from transitions?

If not, we might skip the rendering at all in wide screen scenarios.

mountiny · 2025-06-02T14:18:12Z

Its its mainly for he overlay it feels like we do not need it. However, I think the bug @WojtekBoman found is definitely a blocker for this PR as is. We do need to keep the RBR/ GBR, its bad UX if it would be hiding and re-appearing

kacper-mikolajczak · 2025-06-02T14:26:05Z

Agree @mountiny 👍 In this case let's pivot the plan and:

provide as light dummy alternative as possible for narrow screens
remove redundant navigators (and dummies) for wide screens altogether

I will check what are the possibilities and new outcomes. Let me know if new plan sounds good :)

mountiny · 2025-06-02T18:57:59Z

I still struggle to remember why we would need it in Wide view but also we used to have the tabs in the bottom and now they are on the Left in wide view so it might have been something specific to the previous UI. Definitely up for trying to get rid of the extra navigator in wide layout

WojtekBoman · 2025-06-03T06:49:00Z

I still struggle to remember why we would need it in Wide view but also we used to have the tabs in the bottom and now they are on the Left in wide view so it might have been something specific to the previous UI. Definitely up for trying to get rid of the extra navigator in wide layout

On a wide layout we use TopLevelNavigationTabBar to display tooltips and avoid flickering when switching tabs (when NavigationTabBar is re-rendered in each tab, RBR/GBR may flicker)

kacper-mikolajczak · 2025-06-03T07:35:26Z

On a wide layout we use NavigationTabBar to display tooltips and avoid flickering when switching tabs (the component is then re-rendered and e.g. RBR/GBR may flicker)

@WojtekBoman Sorry my knowledge is limited in this case, but I would like to understand it fully.

Wouldn't singular NavigationTabBar inside TopLevelNavigationTabBar be enough to handle tooltips display on wide screen?

Also, it's rendered once on top and stays there and I am not sure what flickering we could experience. The behaviour should also remain the same as in duplicated NavigationTabBar that is included in the screens. Please correct me if I am mistaken.

Could you show what is the regression when using top level navigator only? Thanks ❤️

WojtekBoman · 2025-06-03T07:47:27Z

I updated my answer, I wanted to emphasize why we need TopLevelNavigationTabBar

Wouldn't singular NavigationTabBar inside TopLevelNavigationTabBar be enough to handle tooltips display on wide screen?

Yes TopLevelNavigationTabBar will handle this case.

When I mentioned flickering, I meant that with TopLevelNavigationTabBar we avoid flickering because we don't unmount the bar when switching tabs

WojtekBoman · 2025-06-03T08:00:17Z

Could you show what is the regression when using top level navigator only? Thanks ❤️

We use navigation tab bars on each sidebar screen to display them below RHP.

If we rely only on TopLevelNavigationTabBar, it will be displayed above the RHP overlay

Screen.Recording.2025-06-03.at.09.55.47.mov

kacper-mikolajczak · 2025-06-03T11:47:31Z

I've chedk and it's indeed hard to work around current stacking context (layering) flow on web to display TopLevle without issues when RHP is open. In this case, I can limit current efforts to:

provide as light dummy alternative as possible for narrow screens

Sounds good @mountiny? Based on the results we can use it or not if the improvement is negligible.

mountiny · 2025-06-03T12:16:20Z

@kacper-mikolajczak sounds good, if we can use it there at least that would be handy

mountiny · 2025-06-03T12:16:53Z

If the bottom tabs would have gbr or RBR though, then you slide to close the page using a gesture, the dummy component would not have them and it could cause a flicker, right?

kacper-mikolajczak · 2025-06-03T19:50:08Z

If the bottom tabs would have gbr or RBR though, then you slide to close the page using a gesture, the dummy component would not have them and it could cause a flicker, right?

We will keep all the logic required not to undermine functionality in any way. In practice, mostly FAB is going to be trimmed away. I am curious what's the perf diff in this case, will report you back 🔜

kacper-mikolajczak · 2025-06-03T21:18:18Z

Result of applying RBR indicators logic on web (commit) shows no particular difference in render timings - we should be good to go!

web-after-rbr.mp4

mountiny · 2025-06-04T12:58:10Z

@kacper-mikolajczak what about the GBR?

mountiny · 2025-06-04T12:58:20Z

@ishpaul777 can you proceed with the review and testing please?

mountiny · 2025-06-04T12:59:15Z

@kacper-mikolajczak prettier

ishpaul777 · 2025-06-04T17:30:59Z

catching up!

ishpaul777 · 2025-06-04T18:26:38Z

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
- MacOS: Desktop
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 there are no new alerts related to the canBeMissing param for useOnyx
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

Screen.Recording.2025-06-05.at.12.29.45.AM.mov

Android: mWeb Chrome

Screen.Recording.2025-06-05.at.12.38.28.AM.mov

iOS: HybridApp

Screen.Recording.2025-06-05.at.12.06.41.AM.mov

iOS: mWeb Safari

Screen.Recording.2025-06-05.at.12.02.04.AM.mov

MacOS: Chrome / Safari

Screen.Recording.2025-06-04.at.11.46.19.PM.mov

MacOS: Desktop

ishpaul777

looks good, tests well! please fix prettier

kacper-mikolajczak · 2025-06-05T08:44:56Z

@ishpaul777 Prettier has been fixed ✅

ishpaul777

LGTM!

mountiny

Thanks!

mountiny · 2025-06-05T21:56:43Z

src/components/Navigation/NavigationTabBar/NavigationTabBarDummy.tsx

+    return <NavigationTabBarWideDummy selectedTab={selectedTab} />;
+}
+
+export default memo(NavigationTabBarDummy);


Display name

OSBotify · 2025-06-05T22:06:43Z

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

QichenZhu · 2025-06-09T10:45:49Z

Found an issue while testing #62747, might be related to this PR:

Go to https://staging.new.expensify.com/
As user A, create a workspace and add user B as a member
As user B, click Workspaces, select the workspace created by user A, then navigate back to Inbox
As user A, delete the workspace
As user B, click Workspaces, Reports, or Account

Expected result: Navigation bar works
Actual result: Navigation bar doesn't work

Screen.Recording.2025-06-09.at.22.37.20.mov

github-actions · 2025-06-09T16:55:00Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.1.63-0 🚀

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

ishpaul777 · 2025-06-09T17:49:56Z

@kacper-mikolajczak can you please take a look at reported bug here

mountiny · 2025-06-10T09:04:09Z

Thanks for raising!

github-actions · 2025-06-10T22:41:16Z

🚀 Deployed to production by https://github.com/Julesssss in version: 9.1.63-6 🚀

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

NavigationTabBar: add dummy component

cf201b1

mountiny assigned kacper-mikolajczak Jun 2, 2025

mountiny reviewed Jun 2, 2025

View reviewed changes

NavigationTabBar: use memo for dummy

a0346fa

kacper-mikolajczak marked this pull request as ready for review June 2, 2025 12:33

kacper-mikolajczak requested a review from a team as a code owner June 2, 2025 12:33

melvin-bot bot requested review from ishpaul777 and removed request for a team June 2, 2025 12:33

adamgrzybowski reviewed Jun 2, 2025

View reviewed changes

NavigationTabBarDummy: remove tooltips

13a055a

kacper-mikolajczak force-pushed the perf/navigation-tab-bar-dummy branch from b822093 to 13a055a Compare June 2, 2025 13:42

Merge branch 'main' into perf/navigation-tab-bar-dummy

8af225a

NavigationTabBarDummy: add RBR indicator support

82d4501

ishpaul777 reviewed Jun 4, 2025

View reviewed changes

WorkspacesListPage: fix prettier

c4d5a6a

ishpaul777 approved these changes Jun 5, 2025

View reviewed changes

melvin-bot bot requested a review from mountiny June 5, 2025 16:51

mountiny approved these changes Jun 5, 2025

View reviewed changes

mountiny merged commit 3aca737 into Expensify:main Jun 5, 2025
19 checks passed

QichenZhu mentioned this pull request Jun 9, 2025

fix: WS - Not here page appears when trying to navigate to Workspaces. #62747

Merged

49 tasks

github-actions bot mentioned this pull request Jun 9, 2025

Deploy Checklist: New Expensify 2025-06-09 #63762

Closed

77 tasks

bernhardoj mentioned this pull request Jun 10, 2025

[$250] Tabs on the left navigation bar are not clickable after deleting workspace #63765

Closed

8 tasks

mountiny mentioned this pull request Jun 10, 2025

[CP Staging] Revert "NavigationTabBar: Add dummy component" #63826

Merged

melvin-bot bot mentioned this pull request Jun 10, 2025

[Due for payment 2025-06-17] [$50] Improve performance around the NavigationTabBar #63244

Closed

NavigationTabBar: Add dummy component #63242

NavigationTabBar: Add dummy component #63242

Uh oh!

Conversation

kacper-mikolajczak commented Jun 2, 2025 • edited 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!

kacper-mikolajczak commented Jun 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Problem

Solution

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny Jun 2, 2025

Choose a reason for hiding this comment

Uh oh!

kacper-mikolajczak Jun 2, 2025

Choose a reason for hiding this comment

Uh oh!

adamgrzybowski Jun 2, 2025

Choose a reason for hiding this comment

Uh oh!

mountiny commented Jun 2, 2025

Uh oh!

ishpaul777 commented Jun 2, 2025

Uh oh!

melvin-bot bot commented Jun 2, 2025

Uh oh!

adamgrzybowski Jun 2, 2025

Choose a reason for hiding this comment

Uh oh!

kacper-mikolajczak Jun 2, 2025

Choose a reason for hiding this comment

Uh oh!

WojtekBoman commented Jun 2, 2025

Uh oh!

kacper-mikolajczak commented Jun 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kacper-mikolajczak commented Jun 2, 2025

Uh oh!

mountiny commented Jun 2, 2025

Uh oh!

kacper-mikolajczak commented Jun 2, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

mountiny commented Jun 2, 2025

Uh oh!

WojtekBoman commented Jun 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kacper-mikolajczak commented Jun 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WojtekBoman commented Jun 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

WojtekBoman commented Jun 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kacper-mikolajczak commented Jun 3, 2025

Uh oh!

mountiny commented Jun 3, 2025

Uh oh!

mountiny commented Jun 3, 2025

Uh oh!

kacper-mikolajczak commented Jun 3, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

kacper-mikolajczak commented Jun 3, 2025

Uh oh!

kacper-mikolajczak commented Jun 2, 2025 •

edited

Loading

kacper-mikolajczak commented Jun 2, 2025 •

edited

Loading

kacper-mikolajczak commented Jun 2, 2025 •

edited

Loading

kacper-mikolajczak commented Jun 2, 2025 •

edited

Loading

WojtekBoman commented Jun 3, 2025 •

edited

Loading

kacper-mikolajczak commented Jun 3, 2025 •

edited

Loading

WojtekBoman commented Jun 3, 2025 •

edited

Loading

WojtekBoman commented Jun 3, 2025 •

edited

Loading

kacper-mikolajczak commented Jun 3, 2025 •

edited

Loading

ishpaul777 commented Jun 4, 2025 •

edited

Loading