[HybridApp] Add HybridApp turbomodule by war-in · Pull Request #57406 · Expensify/App

war-in · 2025-02-25T14:58:39Z

Explanation of Change

This PR adds hybrid-app module, which provides functionality required to communicate with the OldDot part (HybridAppModule previously)

Fixed Issues

$ #57510
PROPOSAL:
MOBILE-EXPENSIFY: https://github.com/Expensify/Mobile-Expensify/pull/13442

Tests

Open app
Switch between NewDot and OldDot
Change account in copilot (ND side) and check if it changed in OD

Offline tests

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Open app
Switch between NewDot and OldDot
Change account in copilot (ND side) and check if it changed in OD

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

# Conflicts: # Mobile-Expensify # package-lock.json # src/libs/Environment/getEnvironment/index.native.ts # src/pages/OnboardingEmployees/BaseOnboardingEmployees.tsx

github-actions · 2025-02-25T14:58:52Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-02-25T15:18:58Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-02-25T15:29:30Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-02-25T15:36:57Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

WoLewicki

Some comments here too 😅

modules/hybrid-app/src/NativeReactNativeHybridApp.ts

modules/hybrid-app/package.json

modules/hybrid-app/android/src/main/AndroidManifest.xml

modules/hybrid-app/android/build.gradle

src/components/ScreenWrapper.tsx

src/hooks/useOnboardingFlow.ts

# Conflicts: # Mobile-Expensify # package-lock.json

github-actions · 2025-02-26T12:07:57Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-02-26T12:56:19Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

# Conflicts: # Mobile-Expensify

github-actions · 2025-02-28T13:33:52Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-02-28T13:36:21Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-02-28T13:39:08Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

github-actions · 2025-03-06T15:18:54Z

⚠️ This PR is possibly changing native code, it may cause problems with HybridApp. Please run an AdHoc build to verify that HybridApp will not break. ⚠️

# Conflicts: # package-lock.json # src/components/BookTravelButton.tsx # src/components/ScreenWrapper.tsx # src/pages/Travel/MyTripsPage.tsx # src/pages/Travel/TripSummaryPage.tsx # src/pages/settings/InitialSettingsPage.tsx

github-actions · 2025-03-10T16:04:57Z

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

github-actions · 2025-03-10T17:19:14Z

🚧 @Julesssss has triggered a test app build. You can view the workflow run here.

github-actions · 2025-03-10T17:37:28Z

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

github-actions · 2025-03-10T17:48:44Z

🧪🧪 Use the links below to test this adhoc build on Android, iOS, Desktop, and Web. Happy testing! 🧪🧪

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.amazonaws.com/android/57406/index.html	https://ad-hoc-expensify-cash.s3.amazonaws.com/ios/57406/index.html

Android Hybrid 🤖🔄	iOS Hybrid 🍎🔄
N/A	N/A
N/A	N/A
Desktop 💻	Web 🕸️
N/A	N/A
N/A	N/A

👀 View the workflow run that generated this build 👀

Julesssss

Understood very little, but it's testing well!

Julesssss · 2025-03-10T21:57:02Z

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: Native
- Android: mWeb Chrome
- iOS: Native
- 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 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: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

github-actions · 2025-03-11T11:12:30Z

⚠️ This PR is possibly changing native code and/or updating libraries, it may cause problems with HybridApp. Please check if any patch updates are required in the HybridApp repo and run an AdHoc build to verify that HybridApp will not break. Ask Contributor Plus for help if you are not sure how to handle this. ⚠️

mountiny

Gonna merge this and that should unblock the kotlin action in the oldApp pr

mountiny · 2025-03-12T14:31:35Z

modules/hybrid-app/ios/ReactNativeHybridApp.mm

+
+- (void)completeOnboarding:(BOOL)status {
+    NSLog(@"[ReactNativeHybridApp] `completeOnboarding` should never be called in standalone `New Expensify` app");
+


Suggested change

OSBotify · 2025-03-12T14:44:52Z

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

…p-turbomodule (cherry picked from commit 931dcd3) (CP triggered by mountiny)

github-actions · 2025-03-12T15:37:08Z

🚀 Cherry-picked to staging by https://github.com/mountiny in version: 9.1.12-1 🚀

platform	result
🤖 android 🤖	success ✅
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	cancelled 🔪
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	success ✅
🍎🔄 iOS HybridApp 🍎🔄	cancelled 🔪

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

github-actions · 2025-03-14T01:06:38Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.1.12-7 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌

github-actions · 2025-03-14T02:17:28Z

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

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

github-actions · 2025-03-17T11:39:56Z

🚀 Deployed to production by https://github.com/mountiny in version: 9.1.13-5 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌

github-actions · 2025-03-17T12:01:22Z

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

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

@Expensify/applauseleads please QA this PR and check it off on the deploy checklist if it passes.

izarutskaya · 2025-03-17T16:27:27Z

@war-in QA facing with issue #58357
but seems it's not a bug #58357 (comment)

https://utest-dl.s3-accelerate.amazonaws.com/testRunStepMinAttachmentsResult/52221606/1742217316522%21bandicam_2025-03-17_15-10-20-989.mp4?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Date=20250317T162618Z&X-Amz-SignedHeaders=host&X-Amz-Credential=AKIAJ2UIWMJ2OMC3UCQQ%2F20250317%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Expires=86400&X-Amz-Signature=57c74eeed220f6bcf1b0f1a5d5f03d2ce0f5207a3b1fabb7a6dc60fd47d38867

war-in · 2025-03-18T09:54:51Z

@izarutskaya Yes, as Daniel said this is not implemented on web

github-actions · 2025-03-18T21:28:25Z

🚀 Deployed to production by https://github.com/luacmartins in version: 9.1.14-5 🚀

platform	result
🤖 android 🤖	true ❌
🖥 desktop 🖥	success ✅
🍎 iOS 🍎	success ✅
🕸 web 🕸	success ✅
🤖🔄 android HybridApp 🤖🔄	failure ❌
🍎🔄 iOS HybridApp 🍎🔄	failure ❌

war-in added 7 commits February 19, 2025 15:00

wip

6406e0d

native part

c128b40

remove HybridAppModules

9e744e5

refactor ts part

56b171b

simplify HybridAppModule

c19b951

Merge branch 'main' into war-in/hybrid-app-turbomodule

73d1b3a

# Conflicts: # Mobile-Expensify # package-lock.json # src/libs/Environment/getEnvironment/index.native.ts # src/pages/OnboardingEmployees/BaseOnboardingEmployees.tsx

post-merge fixes

ef370cc

war-in added 3 commits February 25, 2025 16:04

fix prettier

91a78a2

fix lint

70223f9

fix lint

ad70f0c

fix tests

2860064

fix rest of the tests

4b8151d

WoLewicki reviewed Feb 25, 2025

View reviewed changes

mateuuszzzzz reviewed Feb 26, 2025

View reviewed changes

src/components/ScreenWrapper.tsx Show resolved Hide resolved

mateuuszzzzz reviewed Feb 26, 2025

View reviewed changes

src/hooks/useOnboardingFlow.ts Outdated Show resolved Hide resolved

war-in added 2 commits February 26, 2025 11:56

Merge branch 'main' into war-in/hybrid-app-turbomodule

7aebfe4

# Conflicts: # Mobile-Expensify # package-lock.json

apply review comments

f3dbfdf

add IS_HYBRID_APP to config

4803b5f

Merge branch 'main' into war-in/hybrid-app-turbomodule

093d286

# Conflicts: # Mobile-Expensify

revert submodule update

9759090

move setRootStatusBarEnabled to correct place

75c6411

Merge branch 'main' into war-in/hybrid-app-turbomodule

6054969

# Conflicts: # package-lock.json # src/components/BookTravelButton.tsx # src/components/ScreenWrapper.tsx # src/pages/Travel/MyTripsPage.tsx # src/pages/Travel/TripSummaryPage.tsx # src/pages/settings/InitialSettingsPage.tsx

fix prettier

3a996ad

Julesssss approved these changes Mar 10, 2025

View reviewed changes

Julesssss removed the request for review from abdulrahuman5196 March 10, 2025 21:57

Merge branch 'main' into war-in/hybrid-app-turbomodule

d293e80

mountiny approved these changes Mar 12, 2025

View reviewed changes

mountiny merged commit 931dcd3 into Expensify:main Mar 12, 2025
25 checks passed

OSBotify pushed a commit that referenced this pull request Mar 12, 2025

Merge pull request #57406 from software-mansion-labs/war-in/hybrid-ap…

cea4a94

…p-turbomodule (cherry picked from commit 931dcd3) (CP triggered by mountiny)

github-actions bot added the CP Staging marks PRs that have been CP'd to staging label Mar 12, 2025

github-actions bot mentioned this pull request Mar 12, 2025

Deploy Checklist: New Expensify 2025-03-12 #58283

Closed

71 tasks

AndrewGable mentioned this pull request Mar 12, 2025

[CP Staging] Revert "[HybridApp] Add HybridApp turbomodule" #58293

Merged

melvin-bot bot mentioned this pull request Mar 14, 2025

[$250] [Due for payment 2025-03-24] [Due for payment 2025-03-21] Update the HybridAppModule to use TurboModules #57510

Closed

github-actions bot mentioned this pull request Mar 14, 2025

Deploy Checklist: New Expensify 2025-03-14 #58424

Closed

90 tasks

github-actions bot mentioned this pull request Mar 17, 2025

Deploy Checklist: New Expensify 2025-03-17 #58550

Closed

72 tasks


		- (void)completeOnboarding:(BOOL)status {
		NSLog(@"[ReactNativeHybridApp] `completeOnboarding` should never be called in standalone `New Expensify` app");

Conversation

war-in commented Feb 25, 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!

github-actions bot commented Feb 25, 2025

Uh oh!

github-actions bot commented Feb 25, 2025

Uh oh!

github-actions bot commented Feb 25, 2025

Uh oh!

github-actions bot commented Feb 25, 2025

Uh oh!

WoLewicki left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

github-actions bot commented Feb 26, 2025

Uh oh!

github-actions bot commented Feb 26, 2025

Uh oh!

github-actions bot commented Feb 28, 2025

Uh oh!

github-actions bot commented Feb 28, 2025

Uh oh!

github-actions bot commented Feb 28, 2025

Uh oh!

github-actions bot commented Mar 6, 2025

Uh oh!

github-actions bot commented Mar 10, 2025

Uh oh!

github-actions bot commented Mar 10, 2025

Uh oh!

github-actions bot commented Mar 10, 2025

Uh oh!

github-actions bot commented Mar 10, 2025

Uh oh!

Julesssss left a comment

Choose a reason for hiding this comment

Uh oh!

Julesssss commented Mar 10, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer Checklist

Screenshots/Videos

Uh oh!

github-actions bot commented Mar 11, 2025

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

mountiny Mar 12, 2025

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Mar 12, 2025

Uh oh!

github-actions bot commented Mar 12, 2025

Uh oh!

github-actions bot commented Mar 14, 2025

Uh oh!

github-actions bot commented Mar 14, 2025

Uh oh!

github-actions bot commented Mar 17, 2025

Uh oh!

github-actions bot commented Mar 17, 2025

Uh oh!

izarutskaya commented Mar 17, 2025

war-in commented Feb 25, 2025 •

edited

Loading

Julesssss commented Mar 10, 2025 •

edited

Loading