Skip to content

Rename "Download as PDF" to "Download report" with singular/plural support - #101181

Merged
twisterdotcom merged 3 commits into
Expensify:mainfrom
ahmdshrif:sherif/fix-101055-download-report-plural
Sep 16, 2026
Merged

twisterdotcom merged 3 commits into
Expensify:mainfrom
ahmdshrif:sherif/fix-101055-download-report-plural

Conversation

@ahmdshrif

@ahmdshrif ahmdshrif commented Sep 15, 2026 •

Copy link
Copy Markdown
Contributor

Explanation of Change

The PDF download action read "Download as PDF" everywhere. Per the naming spec it must read "Download report" on the individual report page (always one report) and, on the Reports page bulk-action menu, "Download report" for one selected report and "Download reports" for more than one.

Both call sites used common.downloadAsPDF, a plain string leaf, so there was nowhere for a count to enter. A label can only vary by count when the English entry is a function returning a PluralForm, which translate(key, {count}) resolves.

This PR:

  • Replaces common.downloadAsPDF with a single plural key common.downloadReport (one: 'Download report', other: 'Download reports'), in the same shape as the existing search.bulkActions.duplicateReport. A single plural key (rather than two flat keys picked with a ternary) lets each locale supply the plural categories it needs, e.g. pl.ts gets one/few/many/other exactly like duplicateReport already does.
  • src/hooks/useExportActions.ts: the DOWNLOAD_PDF secondary action now uses translate('common.downloadReport', {count: 1}), since the report page only ever acts on one report.
  • src/hooks/useSearchBulkActions.ts: the DOWNLOAD_PDF bulk option now uses translate('common.downloadReport', {count: selectedReportIDs.length}), the same value onSelected already branches on to pick the single- vs multi-report export, so the label and the behaviour cannot drift.
  • Adds the key to all locale files. TranslationDeepObject<typeof en> requires every English key in every locale, and the generateTranslations workflow does not run for fork PRs, so the translations are provided here (each mirrors the locale's own downloadReceipts verb and duplicateReport noun). This is the one departure from the proposal, which assumed en.ts alone would be enough. The generated translations from the Polyglot Parrot run have since been applied on top.
  • As requested by the assigning engineer, the same treatment is applied to Download receipts: common.downloadReceipts becomes the plural key common.downloadReceipt (one: 'Download receipt', other: 'Download receipts'). The count is the number of receipts the action will export: on the report page the number of report expenses that carry a receipt (the same set that gates the action), on the Reports page the number of receipt-bearing expenses across the selected reports, and on the Expenses page the number of selected expenses with a receipt.
  • common.downloadAsPDF and common.downloadReceipts have no other consumers, so they are removed. The DOWNLOAD_PDF / DOWNLOAD_RECEIPTS constants, visibility gates and every onSelected path are untouched. The Expensify Card statement action keeps its own search.expensifyCardStatementPDF.title.
  • Unit tests: tests/unit/hooks/useExportActionsTest.ts asserts the report page asks for the singular "Download report" and that "Download receipt(s)" follows the number of receipts on the report; tests/unit/hooks/useSearchBulkActionsDownloadPDFTest.ts asserts the singular form for one selected report and the plural form for two; tests/unit/hooks/useSearchBulkActionsDownloadReceiptsTest.ts asserts the receipts label counts receipts (not reports) on the Reports page and expenses with receipts on the Expenses page. All of them fail against the previous call sites.
  • Help-centre articles How-to-Export-Reports.md, Search-and-Download-Expenses.md and Expense-and-Report-Actions.md are updated so the steps and FAQ name Download report / Download reports instead of the removed "Download as PDF".

Fixed Issues

$ #101055
PROPOSAL: #101055 (comment)

Tests

  1. Sign in with an account that has at least two expense reports on a workspace.
  2. Open one of the expense reports and tap the More (⋯) menu in the report header.
  3. Verify the PDF action reads Download report (not "Download as PDF") and that tapping it still downloads the PDF.
  4. Go to Reports and select exactly one report using its checkbox (on mobile: long-press the report row, then tap Select).
  5. Open the 1 selected dropdown and verify the option reads Download report.
  6. Select a second report so two are selected, open the 2 selected dropdown and verify the option now reads Download reports.
  7. Tap Download reports and verify the multi-report PDF export still starts as before.
  8. Deselect down to one report again and verify the label switches back to Download report.
  9. Switch the app language to Spanish (Account → Preferences → Language) and repeat steps 2 and 4–6; verify the label reads "Descargar informe" / "Descargar informes".
  10. Regression: on the Expenses page, select a few expenses and verify there is no download-report option (it only applies to report searches).
  11. Open a report that has exactly one expense with a receipt → More menu and verify the action reads Download receipt; on a report with two or more receipts verify it reads Download receipts.
  12. Go to Reports, select one report that has a single receipt and verify the bulk option reads Download receipt; add a report that has receipts and verify it reads Download receipts.
  13. Go to Expenses, select one expense with a receipt and verify the bulk option reads Download receipt; select a second expense with a receipt and verify it reads Download receipts.
  • Verify that no errors appear in the JS console

Offline tests

  1. Go offline.
  2. Open an expense report → More menu and verify the action still reads Download report; tap it and verify the "You appear to be offline" modal is shown.
  3. Go to Reports, select two reports and verify the bulk option reads Download reports; tap it and verify the offline modal is shown.
  4. Go back online and verify both downloads work again.

QA Steps

Same as tests.

  • Verify that no errors appear in the JS console

PR Author Checklist

  • I linked the correct issue in the ### Fixed Issues section above
  • I wrote clear testing steps that cover the changes made in this PR
    • I added steps for local testing in the Tests section
    • I added steps for the expected offline behavior in the Offline steps section
    • I added steps for Staging and/or Production testing in the QA steps section
    • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
    • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
  • I included screenshots or videos for tests on all platforms
  • I ran the tests on all platforms & verified they passed on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
  • I followed proper code patterns (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I followed the guidelines as stated in the Review Guidelines
  • I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
  • If a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
  • If new assets were added or existing ones were modified, I verified that:
    • The assets are optimized and compressed (for SVG files, run npm run compress-svg)
    • The assets load correctly across all supported platforms.
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • I added unit tests for any new feature or bug fix in this PR to help automatically prevent regressions in this user flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Notes on the checklist above:

  • The copy ("Download report" / "Download reports") comes verbatim from the issue's naming spec (Expensify/Expensify#653740).
  • Only menu labels change: no styles, assets, layout, Storybook stories, deeplinks or message-editing code are touched, so those items have nothing to verify.
  • The change is platform-agnostic: neither hook has a .native variant, and SearchBulkActionsButton passes the same options array to the narrow and wide renderers.

Screenshots/Videos

Android: Native
android-native-101055.mp4
Android: mWeb Chrome
android-mweb-101055.mp4
iOS: Native
ios-native-101055.mp4
iOS: mWeb Safari
ios-mweb-101055.mp4
MacOS: Chrome / Safari
web-101055.mp4

@melvin-bot

melvin-bot Bot commented Sep 15, 2026

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 bun ./scripts/generateTranslations.ts --help

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

@ahmdshrif
ahmdshrif marked this pull request as ready for review September 15, 2026 13:46
@ahmdshrif
ahmdshrif requested review from a team and stephanieelliott as code owners September 15, 2026 13:46
@melvin-bot
melvin-bot Bot requested review from flaviadefaria and removed request for a team September 15, 2026 13:46
@melvin-bot

melvin-bot Bot commented Sep 15, 2026 •

Copy link
Copy Markdown

Concierge reviewer checklist:

  • I have verified the accuracy of the article
    • The article is within a hub that makes sense, and the navigation is correct
    • All processes, screenshots, and examples align with current product behavior.
    • All links within the doc have been verified for correct destination and functionality.
  • I have verified the readability of the article
    • The article's language is clear, concise, and free of jargon.
    • The grammar, spelling, and punctuation are correct.
    • The article contains at least one image, or that an image is not necessary
  • I have verified the formatting of the article
    • The article has consistent formatting (headings, bullet points, etc.) with other HelpDot articles and that aligns with the HelpDot formatting standards.
    • The article has proper text spacing and breaks for readability.
  • I have verified the article has the appropriate tone and style
    • The article's tone is professional, friendly, and suitable for the target audience.
    • The article's tone, terminology, and voice are consistent throughout.
  • I have verified the overall quality of the article
    • The article is not missing any information, nor does it contain redundant information.
    • The article fully addresses user needs.
  • I have verified that all requested improvements have been addressed

For more detailed instructions on completing this checklist, see How do I review a HelpDot PR as a Concierge Team member?

cc @twisterdotcom

@melvin-bot

melvin-bot Bot commented Sep 15, 2026

Copy link
Copy Markdown

@abdulrahuman5196 @mollfpr @twisterdotcom One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

@melvin-bot
melvin-bot Bot removed the request for review from a team September 15, 2026 13:46
@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/fr.ts b/src/languages/fr.ts
index 61d320d1..cd69676e 100644
--- a/src/languages/fr.ts
+++ b/src/languages/fr.ts
@@ -418,7 +418,7 @@ const translations: TranslationDeepObject<typeof en> = {
         validate: 'Valider',
         downloadReport: () => ({
             one: 'Télécharger la note de frais',
-            other: 'Télécharger les notes de frais',
+            other: 'Télécharger des notes de frais',
         }),
         downloadReceipt: () => ({
             one: 'Télécharger le reçu',
diff --git a/src/languages/ja.ts b/src/languages/ja.ts
index b20e5712..3a2ac909 100644
--- a/src/languages/ja.ts
+++ b/src/languages/ja.ts
@@ -420,7 +420,7 @@ const translations: TranslationDeepObject<typeof en> = {
             other: 'レポートをダウンロード',
         }),
         downloadReceipt: () => ({
-            one: '領収書をダウンロード',
+            one: 'レシートをダウンロード',
             other: '領収書をダウンロード',
         }),
         downloadAsCSV: 'CSVとしてダウンロード',
diff --git a/src/languages/nl.ts b/src/languages/nl.ts
index 97f58697..5ae9030a 100644
--- a/src/languages/nl.ts
+++ b/src/languages/nl.ts
@@ -420,8 +420,8 @@ const translations: TranslationDeepObject<typeof en> = {
             other: 'Rapporten downloaden',
         }),
         downloadReceipt: () => ({
-            one: 'Bonnetje downloaden',
-            other: 'Bonnetjes downloaden',
+            one: 'Bon downloaden',
+            other: 'Bonnen downloaden',
         }),
         downloadAsCSV: 'Downloaden als CSV',
         submitViaPDF: 'Indienen via pdf',
diff --git a/src/languages/pl.ts b/src/languages/pl.ts
index 2c838895..d4652501 100644
--- a/src/languages/pl.ts
+++ b/src/languages/pl.ts
@@ -421,14 +421,10 @@ const translations: TranslationDeepObject<typeof en> = {
         validate: 'Zatwierdź',
         downloadReport: () => ({
             one: 'Pobierz raport',
-            few: 'Pobierz raporty',
-            many: 'Pobierz raporty',
             other: 'Pobierz raporty',
         }),
         downloadReceipt: () => ({
             one: 'Pobierz paragon',
-            few: 'Pobierz paragony',
-            many: 'Pobierz paragony',
             other: 'Pobierz paragony',
         }),
         downloadAsCSV: 'Pobierz jako CSV',
diff --git a/src/languages/zh-hans.ts b/src/languages/zh-hans.ts
index d048e877..fa4cc245 100644
--- a/src/languages/zh-hans.ts
+++ b/src/languages/zh-hans.ts
@@ -417,7 +417,7 @@ const translations: TranslationDeepObject<typeof en> = {
         validate: '验证',
         downloadReport: () => ({
             one: '下载报表',
-            other: '下载报表',
+            other: '下载报告',
         }),
         downloadReceipt: () => ({
             one: '下载收据',

Note

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

View workflow run

@github-actions

Copy link
Copy Markdown
Contributor

HelpDot Documentation Review

Overall Assessment

This PR updates three help articles to align documentation with a product UI change: the button label formerly shown as Download as PDF is now Download report (singular) or Download reports (plural), matching the new pluralized translation keys added in the code. All documentation edits are targeted UI-label replacements. No structural, heading, metadata, or workflow changes were introduced. The changes correctly follow the Core UI Referencing Rule of using the exact text shown in the product UI.

Scores Summary

  • Readability: 9/10 - The edits are minimal, in-place label swaps that preserve existing sentence flow and step formatting. Surrounding prose reads cleanly with the new terms.
  • AI Readiness: 9/10 - Replacing the generic as-PDF phrasing with the exact feature label Download report / Download reports improves retrieval precision and matches real UI terminology. No headings or metadata were affected by the diff.
  • Style Compliance: 9/10 - Button labels remain bolded and in Sentence case per Button Naming Standards, and now match the exact UI text. Singular/plural usage is correctly matched to context (single vs. multiple reports).

Key Findings

  • Consistent, correct application of the new label across all three files (single-report flows use Download report; multi-report flows use Download reports).
  • The Expense-and-Report-Actions.md list and both reference tables were updated in lockstep, keeping the reference tables accurate.
  • In How-to-Export-Reports.md, the explanatory paragraph and the does-not-apply-to list were both updated, avoiding stale terminology. Good thoroughness.
  • No violations introduced: bolding, casing, and exact-UI-text rules are all respected.
  • Minor: single-report steps correctly use the singular and bulk flows use the plural; confirm this matches actual runtime label behavior.

Recommendations

  • No blocking issues. The documentation changes are accurate and compliant.
  • Optional follow-up (outside this diff): review other articles referencing PDF export for terminology consistency; not required for this PR.

Files Reviewed

  • docs/articles/new-expensify/reports-and-expenses/Expense-and-Report-Actions.md - Label updated in list and both reference tables. Compliant.
  • docs/articles/new-expensify/reports-and-expenses/How-to-Export-Reports.md - Single/multi steps plus explanatory paragraph and exclusion list updated. Compliant.
  • docs/articles/new-expensify/reports-and-expenses/Search-and-Download-Expenses.md - Single/multi download steps and FAQ answer updated. Compliant.

Note: Detailed line-by-line feedback has been provided as inline comments.

@twisterdotcom

twisterdotcom commented Sep 16, 2026 •

Copy link
Copy Markdown
Contributor

Reviewer Checklist

  • I have verified the author checklist is complete (all boxes are checked off).
  • I verified the correct issue is linked in the ### Fixed Issues section above
  • I verified testing steps are clear and they cover the changes made in this PR
    • I verified the steps for local testing are in the Tests section
    • I verified the steps for Staging and/or Production testing are in the QA steps section
    • I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
    • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I checked that screenshots or videos are included for tests on all platforms
  • I included screenshots or videos for tests on all platforms
  • I verified that the composer does not automatically focus or open the keyboard on mobile unless explicitly intended. This includes checking that returning the app from the background does not unexpectedly open the keyboard.
  • I verified tests pass on all platforms & I tested again on:
    • Android: HybridApp
    • Android: mWeb Chrome
    • iOS: HybridApp
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that comments were added to code that is not self explanatory
    • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
    • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
  • I verified that this PR follows the guidelines as stated in the Review Guidelines
  • I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
  • If a new component is created I verified that:
    • A similar component doesn't exist in the codebase
    • All props are defined accurately
    • 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
    • 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 a new CSS style is added I verified that:
    • A similar style doesn't already exist
    • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)
  • If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
  • If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
  • If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
  • If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
  • If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label and/or tagged @Expensify/design so the design team can review the changes.
  • For any bug fix or new feature in this PR, I verified that sufficient unit tests are included to prevent regressions in this flow.
  • If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
  • I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: HybridApp
Android: mWeb Chrome
iOS: HybridApp
iOS: mWeb Safari
MacOS: Chrome / Safari

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

LGTM!

@twisterdotcom
twisterdotcom merged commit aefa80e into Expensify:main Sep 16, 2026
38 of 39 checks passed
@github-actions

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

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

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/twisterdotcom in version: 9.4.81-0 🚀

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

@MelvinBot

Copy link
Copy Markdown
Contributor

Yes — help site changes are required. Draft PR: Docs updates for E/A#101181 name singular Download receipt label

This PR renamed two labels, but only documented one.

Already handled here — common.downloadAsPDF → common.downloadReport. The three articles you touched now read Download report / Download reports correctly. Nothing left to do.

Missed — common.downloadReceipts → common.downloadReceipt (src/languages/en.ts:471-474). Every help site article still names only the plural Download receipts, so the docs are now wrong whenever the download includes exactly one receipt.

The singular really does surface, at all three call sites:

Call site Count driving the label
Report More menu useExportActions.ts:295 — expenses on the report with a receipt
Reports page bulk menu useSearchBulkActions.ts:2535 — receipts across the selected reports, not reports
Expenses page bulk menu useSearchBulkActions.ts:2565 — selected expenses with a receipt

The docs PR names both forms wherever the action appears and states the rule that picks one, across 12 spots in two articles:

Expense-and-Report-Actions.md needs nothing: it already reads Download report, and it has no receipt-download row.

Verification and one thing I could not finish

Labels. Checked against en.ts on main (downloadReport, downloadReceipt), then confirmed in the running web app off your branch: the report More menu and the Reports page 1 selected menu both read exactly Download report. The 2 selected menu and the receipts action were not reached — the test account had no receipts, and the run ended when a stray click on Download report navigated the tab to a secure?secureType=pdfreport URL that does not resolve in the sandbox. Those two labels rest on the en.ts strings and the count arguments above, not on a screenshot.

Guidelines applied. Both new ## headings start with "Why" and sit under # FAQ per HELP_AUTHORING_GUIDELINES.md §2; every label is bolded, Sentence case, unquoted per HELPSITE_NAMING_CONVENTIONS.md. npm run spell-changed passes on both files.

Not done: GitHub refused to assign you to the docs PR — repos/Expensify/App/assignees/ahmdshrif returns 404, so ahmdshrif is not assignable on this repo. The HelpDot label is applied, the PR is a draft, PullerBear is requested, and you are @-mentioned in the body. Someone with write access needs to add you as assignee if you want that too.

@ahmdshrif, please review the linked help site PR and confirm it reflects the current behavior. Then mark the linked help site PR Ready for review

@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.81-1 🚀

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

1 similar comment
@OSBotify

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.4.81-1 🚀

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

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.

5 participants