[No QA] Set up remote ad hoc builds 2 by LukasMod · Pull Request #76061 · Expensify/App

LukasMod · 2025-11-25T19:14:21Z

This reverts commit 0c2ed1a (which is revert commit of this PR #70396) and change action to point to latest commit (callstackincubator). It allows to use adhoc builds with S3 remote cache, workflow testBuild.yml.

Explanation of Change

Fixed Issues

$ #62296
PROPOSAL:

Tests

First build should result with QR codes/links that allow iOS/android artifacts to be installed.
Second build (using cached artifacts from first build) should result with QR codes/links that allow iOS/android artifacts to be installed.

Verify that no errors appear in the JS console

Offline tests

QA Steps

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

…et-up-remote-ad-hoc-builds" This reverts commit 0c2ed1a.

github-actions · 2025-11-26T12:42:16Z

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

…to set-up-remote-ad-hoc-builds-2

github-actions · 2025-12-01T15:01:20Z

⚠️ 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-12-01T15:53:38Z

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

github-actions · 2025-12-01T16:29:45Z

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

Android 🤖	iOS 🍎
	❌ FAILED ❌
	The QR code can't be generated, because the iOS build failed

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

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-02T11:19:29Z

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

github-actions · 2025-12-02T11:52:12Z

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

Android 🤖	iOS 🍎
	❌ FAILED ❌
	The QR code can't be generated, because the iOS build failed

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

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-02T13:53:03Z

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

github-actions · 2025-12-02T14:01:54Z

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

Android 🤖	iOS 🍎
❌ FAILED ❌	❌ FAILED ❌
The QR code can't be generated, because the Android build failed	The QR code can't be generated, because the iOS build failed

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

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-02T14:04:25Z

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

…to set-up-remote-ad-hoc-builds-2

github-actions · 2025-12-02T14:29:32Z

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

Android 🤖	iOS 🍎
❌ FAILED ❌	❌ FAILED ❌
The QR code can't be generated, because the Android build failed	The QR code can't be generated, because the iOS build failed

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

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-02T14:41:48Z

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

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

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

Android 🤖	iOS 🍎

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

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-19T10:40:58Z

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

github-actions · 2025-12-19T11:12:29Z

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

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

Desktop 💻	Web 🕸️
⏩ SKIPPED ⏩	https://76061.pr-testing.expensify.com
The build for Desktop was skipped

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-19T12:03:28Z

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

github-actions · 2025-12-19T12:25:19Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-5551feb09d69ccfaf4bf2d05844c0e880327b6e6/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-4c9eea5925d285923445f03f328d4678f830b6fb/index.html

Desktop 💻	Web 🕸️
⏩ SKIPPED ⏩	https://76061.pr-testing.expensify.com
The build for Desktop was skipped

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-19T13:18:01Z

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

github-actions · 2025-12-19T13:50:52Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-2d618af8c244911a4181d03c434dc284fbb208c3/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-a1d6ce6094f78a33a09f9bb1b304c8cd5091001b/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/76061/NewExpensify.dmg	https://76061.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

github-actions · 2025-12-19T13:53:19Z

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

github-actions · 2025-12-19T14:08:06Z

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

Android 🤖	iOS 🍎
https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-android-Adhoc-6630d68-2d618af8c244911a4181d03c434dc284fbb208c3/index.html	https://ad-hoc-expensify-cash.s3.us-east-1.amazonaws.com/rock-artifacts/ad-hoc/rock-ios-device-AdHoc-6630d68-a1d6ce6094f78a33a09f9bb1b304c8cd5091001b/index.html

Desktop 💻	Web 🕸️
https://ad-hoc-expensify-cash.s3.amazonaws.com/desktop/76061/NewExpensify.dmg	https://76061.pr-testing.expensify.com

👀 View the workflow run that generated this build 👀

melvin-bot · 2025-12-19T14:12:29Z

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

adhorodyski · 2025-12-23T13:58:32Z

@akinwale any chance you will be able to review this shortly? Thanks!

LukasMod · 2025-12-29T10:06:56Z

@akinwale Please take a look. Thanks!

mountiny · 2025-12-29T13:46:34Z

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

Android: mWeb Chrome

iOS: HybridApp

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

mountiny

Changes look good to me and we have tested this extensively so going to move it ahead

…t-up-remote-ad-hoc-builds-2" This reverts commit 9a54baf, reversing changes made to 6ceced8.

…c-builds-2-revert [NoQA] Revert "Merge pull request #76061

…ote-ad-hoc-builds-2 [No QA] Set up remote ad hoc builds 2

OSBotify · 2025-12-30T15:19:23Z

🚀 Deployed to staging by https://github.com/mountiny in version: 9.2.89-1 🚀

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

OSBotify · 2025-12-31T18:33:19Z

🚀 Deployed to production by https://github.com/thienlnam in version: 9.2.89-6 🚀

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

LukasMod added 2 commits November 25, 2025 20:08

Reapply "Merge pull request Expensify#70396 from callstack-internal/s…

4c25468

…et-up-remote-ad-hoc-builds" This reverts commit 0c2ed1a.

update callstackincubator actions to latest

a47843e

melvin-bot Bot assigned LukasMod Nov 25, 2025

LukasMod added 2 commits November 26, 2025 08:15

Add Configure AWS Credentials step

e03443e

restore missing SENTRY_AUTH_TOKEN

cbaf186

mountiny mentioned this pull request Nov 26, 2025

Vit 76061 #76120

Merged

53 tasks

This comment has been minimized.

Sign in to view

LukasMod added 3 commits December 1, 2025 09:42

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

0ba21f4

…to set-up-remote-ad-hoc-builds-2

add ios testBuild.yaml fix

c3a5f4b

add additional rock logs

a3af759

LukasMod changed the title ~~Set up remote ad hoc builds 2~~ [No QA] Set up remote ad hoc builds 2 Dec 1, 2025

LukasMod mentioned this pull request Dec 1, 2025

[Due for payment 2026-01-07] Remote builds cache: integrate into Adhoc builds #62296

Closed

LukasMod added 2 commits December 2, 2025 09:11

remove ad-hoc flag

dcfc3f4

point to fork gh actions with additional logs

c2d5c5c

LukasMod mentioned this pull request Dec 2, 2025

Migrate from RNEF to Rock #69950

Closed

fix quoting, remove rock logs

ccae09d

Merge branch 'main' of github.com:callstack-internal/Expensify-App in…

28b33aa

…to set-up-remote-ad-hoc-builds-2

remove duplicated android build command

a9b913b

LukasMod added 3 commits December 18, 2025 15:07

use new usePrebuiltRNCore rock config

5cf9351

update rock to 0.11.14

e2c26f6

bump rock to 0.12.0

6630d68

LukasMod marked this pull request as ready for review December 19, 2025 14:12

LukasMod requested a review from a team as a code owner December 19, 2025 14:12

melvin-bot Bot requested review from akinwale and removed request for a team December 19, 2025 14:12

adhorodyski reviewed Dec 22, 2025

View reviewed changes

Comment thread scripts/run-build.sh

mountiny removed the request for review from akinwale December 29, 2025 13:42

mountiny approved these changes Dec 29, 2025

View reviewed changes

mountiny merged commit 9a54baf into Expensify:main Dec 29, 2025
116 of 120 checks passed

LukasMod added a commit to callstack-internal/Expensify-App that referenced this pull request Dec 29, 2025

Revert "Merge pull request Expensify#76061 from callstack-internal/se…

3eece9b

…t-up-remote-ad-hoc-builds-2" This reverts commit 9a54baf, reversing changes made to 6ceced8.

LukasMod mentioned this pull request Dec 29, 2025

[NoQA] Revert "Merge pull request #76061 #78532

Merged

53 tasks

mountiny added a commit that referenced this pull request Dec 29, 2025

Merge pull request #78532 from callstack-internal/set-up-remote-ad-ho…

2b53350

…c-builds-2-revert [NoQA] Revert "Merge pull request #76061

LukasMod pushed a commit to callstack-internal/Expensify-App that referenced this pull request Dec 29, 2025

Merge pull request Expensify#76061 from callstack-internal/set-up-rem…

c1fcd41

…ote-ad-hoc-builds-2 [No QA] Set up remote ad hoc builds 2

OSBotify mentioned this pull request Dec 30, 2025

Deploy Checklist: New Expensify 2025-12-30 #78583

Closed

56 tasks

Conversation

LukasMod commented Nov 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 Nov 26, 2025

Uh oh!

This comment has been minimized.

github-actions Bot commented Dec 1, 2025

Uh oh!

github-actions Bot commented Dec 1, 2025

Uh oh!

github-actions Bot commented Dec 1, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 2, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

github-actions Bot commented Dec 19, 2025

Uh oh!

melvin-bot Bot commented Dec 19, 2025

Uh oh!

Uh oh!

adhorodyski commented Dec 23, 2025

Uh oh!

LukasMod commented Dec 29, 2025

Uh oh!

mountiny commented Dec 29, 2025

Reviewer Checklist

Screenshots/Videos

Uh oh!

mountiny left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

OSBotify commented Dec 30, 2025

Uh oh!

OSBotify commented Dec 31, 2025

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

4 participants

LukasMod commented Nov 25, 2025 •

edited

Loading