Skip to content

[Domain Control] [No QA] Create DomainAdminsSettings RHP with Primary contact - #77515

Merged
mountiny merged 25 commits into
Expensify:mainfrom
software-mansion-labs:war-in/domains/add-admins-settings-page
Dec 17, 2025
Merged

[Domain Control] [No QA] Create DomainAdminsSettings RHP with Primary contact#77515
mountiny merged 25 commits into
Expensify:mainfrom
software-mansion-labs:war-in/domains/add-admins-settings-page

Conversation

@war-in

@war-in war-in commented Dec 12, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

Second part of the Release 1 of the domain-control-in-new-dot project. It adds settings button to the Admins page under domain/<domainAccountID>/admins/settings

I didn't create the API command yet, as it's not ready on the backend side. I'll update the code once the command is ready

Fixed Issues

$ #77585
PROPOSAL:

Tests

  1. Go to /domain//admins
  2. Verify that the settings button is present on the right upper corner
  3. Click on it and observe the RHP opens
  4. Click on the Primary contact row
  5. Verify that the next page with the list of admins shows up
  6. Try searching through the admins
  7. Select an admin and be redirected to the previous page (currently no optimistic onyx data is applied due to lack of API command)

Offline tests

QA Steps

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
Screen.Recording.2025-12-12.at.17.50.46.mov

@melvin-bot

melvin-bot Bot commented Dec 12, 2025

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. For security reasons, translations are not generated automatically for PRs from forks.

If you want to automatically generate translations for other locales, an Expensify employee will have to:

  1. Look at the code and make sure there are no malicious changes.
  2. Run the Generate static translations GitHub workflow. If you have write access and the K2 extension, you can simply click: [this button]

Alternatively, if you are an external contributor, you can run the translation script locally with your own OpenAI API key. To learn more, try running:

npx ts-node ./scripts/generateTranslations.ts --help

Typically, you'd want to translate only what you changed by running npx ts-node ./scripts/generateTranslations.ts --compare-ref main

@war-in war-in changed the title Create DomainAdminsSettings RHP with Primary contact [HOLD] Create DomainAdminsSettings RHP with Primary contact Dec 12, 2025
@codecov

codecov Bot commented Dec 12, 2025

Copy link
Copy Markdown

Codecov Report

❌ Looks like you've decreased code coverage for some files. Please write tests to increase, or at least maintain, the existing level of code coverage. See our documentation here for how to interpret this table.

Files with missing lines Coverage Δ
src/ONYXKEYS.ts 100.00% <ø> (ø)
src/SCREENS.ts 100.00% <ø> (ø)
src/libs/API/types.ts 100.00% <ø> (ø)
...avigation/linkingConfig/RELATIONS/DOMAIN_TO_RHP.ts 100.00% <ø> (ø)
src/libs/Navigation/linkingConfig/config.ts 75.00% <ø> (ø)
src/selectors/Domain.ts 77.77% <100.00%> (+1.30%) ⬆️
src/ROUTES.ts 13.20% <0.00%> (-0.03%) ⬇️
...gation/AppNavigator/ModalStackNavigators/index.tsx 8.37% <0.00%> (-0.03%) ⬇️
src/libs/actions/Domain.ts 10.76% <0.00%> (-1.74%) ⬇️
src/pages/domain/Admins/DomainAdminDetailsPage.tsx 0.00% <0.00%> (ø)
... and 4 more
... and 8 files with indirect coverage changes

…admins-settings-page

# Conflicts:
#	src/ONYXKEYS.ts
#	src/pages/domain/Admins/DomainAdminsPage.tsx
…admins-settings-page

# Conflicts:
#	src/pages/domain/Admins/DomainAdminsPage.tsx
@war-in war-in changed the title [HOLD] Create DomainAdminsSettings RHP with Primary contact [No QA] Create DomainAdminsSettings RHP with Primary contact Dec 12, 2025
Comment thread src/pages/domain/Admins/DomainAdminsPage.tsx Outdated
Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx Outdated
@situchan

Copy link
Copy Markdown
Contributor

Please merge main to reduce diff.

@war-in

war-in commented Dec 14, 2025

Copy link
Copy Markdown
Contributor Author

@situchan main merged!

@mountiny mountiny changed the title [No QA] Create DomainAdminsSettings RHP with Primary contact [Domain Control] [No QA] Create DomainAdminsSettings RHP with Primary contact Dec 14, 2025
Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx Outdated
Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx Outdated
Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx Outdated
const [searchTerm, debouncedSearchTerm, setSearchTerm] = useDebouncedState('');
const [countryCode = CONST.DEFAULT_COUNTRY_CODE] = useOnyx(ONYXKEYS.COUNTRY_CODE, {canBeMissing: false});
const [domainSettings] = useOnyx(`${ONYXKEYS.COLLECTION.SHARED_NVP_PRIVATE_DOMAIN_MEMBER}${domainAccountID}`, {
canBeMissing: false,

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.

Can you add context? I'd like to know when canBeMissing should be false.

As I understand from doc, it's not standard practice.

    /**
     * If the component calling this is the one loading the data by calling an action, then you should set this to `true`.
     *
     * If the component calling this does not load the data then you should set it to `false`, which means that if the data
     * is not there, it will log an alert, as it means we are using data that no one loaded and that's most probably a bug.
     */
    canBeMissing?: boolean;

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

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

I think, based on the comment you sent, that if we don't load the data, we should set it to false
but maybe I misunderstood something 🤔

Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx
Comment thread src/pages/domain/Admins/DomainAdminsSettingsPage.tsx
Comment thread src/libs/actions/Domain.ts Outdated
@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

If we try to use the wrong domainAccountID, for example, we won't show NotFoundView

Снимок экрана 2025-12-15 в 13 23 34

@ZhenjaHorbach

ZhenjaHorbach commented Dec 15, 2025

Copy link
Copy Markdown
Contributor

I suppose it's better to show No results found label after searching without results as in other places

Снимок экрана 2025-12-15 в 13 41 11 Снимок экрана 2025-12-15 в 13 42 09

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

I'm not sure it's a bug
But shouldn't we always have a primary contact?
I mean, if we set it up once
Then we can't remove it(only change)
Right?
Unfortunately, I couldn't find such a case in the docs 😅

2025-12-15.14.02.01.mov

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

@war-in
And could you add Spanish translations?
And then we can trigger a script for other languages

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

I suppose we still need to fix these issues here
#77515 (comment)
#77515 (comment)

or we can fix it separately

@ZhenjaHorbach

ZhenjaHorbach commented Dec 15, 2025

Copy link
Copy Markdown
Contributor

But overall changes look good

JS00001
JS00001 previously approved these changes Dec 16, 2025

@JS00001 JS00001 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.

This is looking good!

@war-in

war-in commented Dec 16, 2025

Copy link
Copy Markdown
Contributor Author

@ZhenjaHorbach both comments addressed! we still need to wait for translations

@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/de.ts b/src/languages/de.ts
index 30f483b7..5d64ccef 100644
--- a/src/languages/de.ts
+++ b/src/languages/de.ts
@@ -7991,7 +7991,7 @@ Hier ist ein *Testbeleg*, um dir zu zeigen, wie es funktioniert:`,
             subtitle: 'Erzwingen Sie für Mitglieder Ihrer Domain die Anmeldung per Single Sign-On, schränken Sie die Erstellung von Workspaces ein und vieles mehr.',
             enable: 'Aktivieren',
         },
-        admins: {title: 'Admins', findAdmin: 'Admin finden'},
+        admins: {title: 'Admins', findAdmin: 'Admin finden', primaryContact: 'Hauptansprechpartner', addPrimaryContact: 'Primären Kontakt hinzufügen', settings: 'Einstellungen'},
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/fr.ts b/src/languages/fr.ts
index ae752206..3ae6f9c1 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -7995,7 +7995,7 @@ Voici un *reçu test* pour vous montrer comment cela fonctionne :`,
             subtitle: "Exiger que les membres de votre domaine se connectent via l'authentification unique, restreindre la création d'espaces de travail, et plus encore.",
             enable: 'Activer',
         },
-        admins: {title: 'Admins', findAdmin: 'Trouver un admin'},
+        admins: {title: 'Admins', findAdmin: 'Trouver un admin', primaryContact: 'Contact principal', addPrimaryContact: 'Ajouter un contact principal', settings: 'Paramètres'},
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/it.ts b/src/languages/it.ts
index f60d9a6e..e9b2d1cf 100644
--- a/src/languages/it.ts
+++ b/src/languages/it.ts
@@ -7971,7 +7971,13 @@ Ecco una *ricevuta di prova* per mostrarti come funziona:`,
             subtitle: 'Richiedi ai membri del tuo dominio di accedere tramite Single Sign-On, limita la creazione di spazi di lavoro e altro ancora.',
             enable: 'Abilita',
         },
-        admins: {title: 'Amministratori', findAdmin: 'Trova amministratore'},
+        admins: {
+            title: 'Amministratori',
+            findAdmin: 'Trova amministratore',
+            primaryContact: 'Contatto principale',
+            addPrimaryContact: 'Aggiungi contatto principale',
+            settings: 'Impostazioni',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index 6bcbcba2..63de94c8 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -7914,7 +7914,7 @@ Expensify の使い方をお見せするための*テストレシート*がこ
             subtitle: 'ドメインのメンバーにシングルサインオンでのログインを必須化し、ワークスペースの作成を制限するなど、さらに多くのことができます。',
             enable: '有効にする',
         },
-        admins: {title: '管理者', findAdmin: '管理者を検索'},
+        admins: {title: '管理者', findAdmin: '管理者を検索', primaryContact: '主要連絡先', addPrimaryContact: '主要連絡先を追加', settings: '設定'},
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 396f75b9..e1e7f45e 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -7956,7 +7956,13 @@ Hier is een *testbon* om je te laten zien hoe het werkt:`,
             subtitle: 'Verplicht leden van je domein om in te loggen via single sign-on, beperk het aanmaken van werkruimten en meer.',
             enable: 'Inschakelen',
         },
-        admins: {title: 'Beheerders', findAdmin: 'Beheerder zoeken'},
+        admins: {
+            title: 'Beheerders',
+            findAdmin: 'Beheerder zoeken',
+            primaryContact: 'Primair contactpersoon',
+            addPrimaryContact: 'Primair contactpersoon toevoegen',
+            settings: 'Instellingen',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 9646789e..e42e818a 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -7942,7 +7942,7 @@ Oto *paragon testowy*, który pokazuje, jak to działa:`,
             subtitle: 'Wymagaj, aby członkowie Twojej domeny logowali się przez Single Sign-On (SSO), ograniczaj tworzenie obszarów roboczych i nie tylko.',
             enable: 'Włącz',
         },
-        admins: {title: 'Administratorzy', findAdmin: 'Znajdź administratora'},
+        admins: {title: 'Administratorzy', findAdmin: 'Znajdź administratora', primaryContact: 'Główny kontakt', addPrimaryContact: 'Dodaj główny kontakt', settings: 'Ustawienia'},
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/pt-BR.ts b/src/languages/pt-BR.ts
index ea50d4c1..e649b4fc 100644
--- a/src/languages/pt-BR.ts
+++ b/src/languages/pt-BR.ts
@@ -7949,7 +7949,13 @@ Aqui está um *recibo de teste* para mostrar como funciona:`,
             subtitle: 'Exija que os membros do seu domínio façam login por meio de logon único (SSO), restrinja a criação de espaços de trabalho e muito mais.',
             enable: 'Ativar',
         },
-        admins: {title: 'Administradores', findAdmin: 'Encontrar administrador'},
+        admins: {
+            title: 'Administradores',
+            findAdmin: 'Encontrar administrador',
+            primaryContact: 'Contato principal',
+            addPrimaryContact: 'Adicionar contato principal',
+            settings: 'Configurações',
+        },
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index 28c1c108..53f214fb 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -7779,7 +7779,7 @@ ${reportName}
         addDomain: {title: '添加域', subtitle: '请输入您想访问的私有域名(例如:expensify.com)。', domainName: '域名', newDomain: '新域名'},
         domainAdded: {title: '已添加域名', description: '接下来,您需要验证域名的所有权并调整您的安全设置。', configure: '配置'},
         enhancedSecurity: {title: '增强的安全性', subtitle: '要求您域内的成员使用单点登录登录、限制工作区创建等。', enable: '启用'},
-        admins: {title: '管理员', findAdmin: '查找管理员'},
+        admins: {title: '管理员', findAdmin: '查找管理员', primaryContact: '主要联系人', addPrimaryContact: '添加主要联系人', settings: '设置'},
     },
 };
 // IMPORTANT: This line is manually replaced in generate translation files by scripts/generateTranslations.ts,

Note

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

Comment on lines +45 to +46
const data: AdminOption[] = [];
for (const accountID of adminAccountIDs ?? []) {

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.

NAB: for is run every time component is rendered. Can we memoize?

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.

As I remember, we decided not to add useMemo to prevent React Compiler issue
But in my opinion, I would put this logic into a separate function

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.

I am not sure but react compiler will memoize this as well? Or only after putting this into separate function?

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.

Currently, I think this code is executed after each render

And by the way,
I just realized this now
This logic is used in two places (DomainAddPrimaryContactPage and DomainAdminsPage)
So, I would create a custom hook for this logic

But I think we can do this in the next PR

@ZhenjaHorbach

Copy link
Copy Markdown
Contributor

Okay
Changes look good!

@melvin-bot
melvin-bot Bot requested a review from JS00001 December 16, 2025 15:45

@situchan situchan 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.

LGTM2

type SetTechnicalContactEmailParams = {
authToken?: string | null;
domainAccountID: number;
technicalContactAccountID: number;

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.

We will update this to email, but since its not used yet, we can do that later

Comment thread src/libs/actions/Domain.ts Outdated
Comment thread src/libs/actions/Domain.ts Outdated
Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx Outdated
Comment thread src/pages/domain/Admins/DomainAdminsPage.tsx Outdated
Comment thread src/pages/domain/Admins/DomainAddPrimaryContactPage.tsx Outdated
Comment thread src/pages/domain/Admins/DomainAdminsSettingsPage.tsx Outdated
# Conflicts:
#	src/ROUTES.ts
#	src/SCREENS.ts
#	src/libs/Navigation/AppNavigator/ModalStackNavigators/index.tsx
#	src/libs/Navigation/linkingConfig/RELATIONS/DOMAIN_TO_RHP.ts
#	src/libs/Navigation/linkingConfig/config.ts
#	src/libs/Navigation/types.ts
#	src/pages/domain/Admins/DomainAdminsPage.tsx

@mountiny mountiny 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.

Thank you

Comment thread src/selectors/Domain.ts
}

export {domainMemberSamlSettingsSelector, domainSamlSettingsStateSelector, domainNameSelector, metaIdentitySelector, adminAccountIDsSelector};
const technicalContactEmailSelector = (domainMemberSharedNVP: OnyxEntry<CardFeeds>) => domainMemberSharedNVP?.settings?.technicalContactEmail;

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.

I know it is trivial but I think we should still add a simple unit tests for such simple selectors to have coverage on these

@mountiny
mountiny merged commit a6baf31 into Expensify:main Dec 17, 2025
32 checks passed
@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/AndrewGable in version: 9.2.84-8 🚀

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants