[No QA] Clarify how to add from Expensify app

[sakluger]

Explanation of Change

Sometimes, users are unable to add Expensify Cards directly in Google Wallet or Apple Wallet. This update to the help page explains how to add a card to a mobile wallet in that scenario.

Fixed Issues

https://github.com/Expensify/Expensify/issues/556666

Tests

No tests

• Verify that no errors appear in the JS console

Offline tests

None

QA Steps

Only manual QA required

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

• Verify that no errors appear in the JS console

PR Author Checklist

• I linked the correct issue in the ### Fixed Issues section above
• I wrote clear testing steps that cover the changes made in this PR
  • I added steps for local testing in the Tests section
  • I added steps for the expected offline behavior in the Offline steps section
  • I added steps for Staging and/or Production testing in the QA steps section
  • I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
  • I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
  • I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).
• I included screenshots or videos for tests on all platforms
• I ran the tests on all platforms & verified they passed on:
  • Android: Native
  • Android: mWeb Chrome
  • iOS: Native
  • iOS: mWeb Safari
  • MacOS: Chrome / Safari
  • MacOS: Desktop
• I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
• I verified there are no new alerts related to the canBeMissing param for useOnyx
• I followed proper code patterns (see Reviewing the code)
  • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
  • I verified that comments were added to code that is not self explanatory
  • I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
  • I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
    • If any non-english text was added/modified, I used JaimeGPT to get English > Spanish translation. I then posted it in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:
  • I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
  • I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
  • I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
  • I verified the JSDocs style guidelines (in STYLE.md) were followed
• If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
• I followed the guidelines as stated in the Review Guidelines
• I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
• I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
• I verified any variables that can be defined as constants (ie. in CONST.ts or at the top of the file that uses the constant) are defined as such
• I verified that if a function's arguments changed that all usages have also been updated correctly
• If any new file was added I verified that:
  • The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory
• If a new CSS style is added I verified that:
  • A similar style doesn't already exist
  • The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))
• If 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.

[melvin-bot]

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 @brianlee-expensify

[melvin-bot]

@brianlee-expensify 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]

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds valuable troubleshooting guidance to the Expensify Card wallet integration documentation. The changes provide users with an alternative method for adding their cards when the primary approach fails, addressing a known pain point mentioned in issue #556666.

Scores Summary

• Readability: 8/10 - Clear, concise language with proper grammar and logical flow. The instructions are easy to follow and well-integrated into the existing content structure.
• AI Readiness: 9/10 - Excellent metadata structure, descriptive headings, and proper context. The content maintains consistent heading hierarchy and provides clear navigation paths.
• Style Compliance: 9/10 - Strong adherence to Expensify voice and tone standards. Uses correct UI terminology and button labels consistently. Formatting follows established HelpDot patterns.

Key Findings

Positive Aspects:

• Addresses a real user pain point with practical solution
• Maintains consistency across both Apple Pay and Google Pay sections
• Uses proper formatting with bold Note: labels
• Integrates seamlessly with existing content flow
• Provides clear navigation paths (Account > Wallet)

Areas for Consideration:

• The notes are nearly identical - this repetition is appropriate given the parallel nature of the two processes
• Content follows established patterns from other HelpDot articles

Recommendations

• Approve for merge - The changes are well-crafted and add genuine value
• Consider monitoring user feedback to see if additional troubleshooting scenarios emerge
• The addition enhances the completeness of the documentation without disrupting existing structure

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md - Approved - Clean addition of helpful troubleshooting content that maintains high quality standards

Overall Recommendation: Approve - This is a high-quality documentation improvement that enhances user experience with practical troubleshooting guidance.

[OSBotify]

A preview of your ExpensifyHelp changes have been deployed to https://92bcfc8e.helpdot.pages.dev ⚡️

Updated articles:

• articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay

[github-actions]

AI Readiness violation: Use of vague pronoun "that" without clear context. Consider revising to: "If adding your Expensify Card directly in the Apple Wallet app doesn't work, you can add your card from within the Expensify app instead." This makes the reference clearer for AI systems and improves readability.

[brianlee-expensify]

@sakluger thoughts on making this simplification?

[brianlee-expensify]

resolving this because i mentioned the same suggestion in the comments above:

• [No QA] Clarify how to add from Expensify app #72595 (comment)
• [No QA] Clarify how to add from Expensify app #72595 (comment)

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a focused, valuable improvement to the Expensify Card documentation by adding fallback instructions for users who encounter issues adding their card directly through Apple Wallet or Google Pay. The changes address a real user pain point identified in issue #556666.

Scores Summary

• Readability: 9/10 - Clear, concise instructions with consistent tone and structure
• AI Readiness: 8/10 - Well-structured content with proper headings and navigation paths
• Style Compliance: 9/10 - Follows Expensify documentation standards and maintains consistency

Key Findings

• Excellent consistency: Both Apple Pay and Google Pay sections receive identical treatment with parallel note structures
• User-centric approach: Addresses real-world failure scenarios that users encounter
• Clear navigation paths: Provides specific UI paths (Account > Wallet) for users to follow
• Proper formatting: Uses bold formatting for UI elements and maintains existing document structure
• Contextual placement: Notes are strategically placed immediately after the primary instructions

Recommendations

• Approved for merge: These changes enhance user experience without introducing any quality issues
• Consider future enhancement: While not required for this PR, future iterations could potentially include troubleshooting for when the Expensify app method also fails

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md - Excellent improvement with clear fallback instructions that maintain consistency with existing content

Note: This PR demonstrates strong attention to user experience and documentation quality standards.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds helpful clarification to the Expensify Card mobile wallet setup documentation by providing alternative methods when direct wallet app integration fails. The changes are minimal but valuable, addressing a real user pain point identified in issue #556666.

Scores Summary

• Readability: 9/10 - Clear, well-structured instructions with proper formatting and consistent tone
• AI Readiness: 8/10 - Good context and navigation paths, though could benefit from more descriptive section headings
• Style Compliance: 9/10 - Excellent adherence to Expensify documentation standards and formatting conventions

Key Findings

• Positive aspects: The added notes are well-written, properly formatted with bold Note: labels, and provide clear step-by-step navigation paths using the standard Expensify format (Account > Wallet)
• Good consistency: Both iOS and Android sections received parallel updates, maintaining document symmetry
• Proper formatting: Correct use of bold text for UI elements and consistent markdown structure
• User-focused: Addresses a specific user workflow issue with practical solutions

Recommendations

• Minor enhancement opportunity: Consider making section headings more descriptive (e.g. "Add Expensify Card to Apple Pay (iOS)" could be "Add Expensify Card to Apple Pay on iPhone/iPad")
• SEO consideration: The current keywords array is comprehensive and appropriate
• Structure: The document follows the established HelpDot template well with clear step-by-step instructions

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md - Excellent - Clean additions that enhance user experience without disrupting existing content flow

Technical Quality

• Proper YAML frontmatter with appropriate metadata
• Consistent heading hierarchy using # and ## tags
• Correct navigation path formatting matching Expensify standards
• Appropriate use of bold formatting for UI elements

This is a high-quality documentation update that effectively addresses user needs while maintaining excellent standards for readability and style compliance.

Note: This review covers the overall documentation quality and standards compliance for the PR changes.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds helpful troubleshooting guidance to the Expensify Card mobile wallet documentation. The changes address a common user pain point by providing an alternative path when the direct wallet app method fails. The additions are well-integrated and maintain consistency with the existing document structure.

Scores Summary

• Readability: 9/10 - Clear, concise language with excellent readability. The note format makes the information easy to scan and understand.
• AI Readiness: 9/10 - Good context preservation with clear navigation paths and specific UI references that maintain searchability.
• Style Compliance: 8/10 - Consistent with Expensify documentation standards, proper formatting, and appropriate tone.

Key Findings

• Excellent User Experience: The addition directly addresses a common user frustration with a clear alternative solution
• Consistent Integration: Both iOS and Android sections receive parallel treatment, maintaining document symmetry
• Clear Navigation: Specific UI navigation paths (Account > Wallet) provide users with actionable steps
• Appropriate Formatting: Proper use of bold text for UI elements and consistent note structure

Recommendations

• Consider Enhancement: The current notes could benefit from a brief explanation of why the direct method might fail (e.g., "due to verification requirements" or "depending on your bank settings")
• Maintain Consistency: Excellent job maintaining parallel structure between iOS and Android sections
• Future Consideration: Consider if this pattern should be applied to other wallet-related documentation

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md - Excellent: Well-executed improvement that enhances user experience with clear, actionable guidance

This is a high-quality documentation update that improves user experience by addressing a common pain point. The changes are minimal but impactful, maintaining consistency while providing valuable troubleshooting information.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a focused improvement to the Expensify Card mobile wallet documentation by adding helpful fallback instructions for users who encounter issues adding their card directly through Apple Wallet or Google Wallet apps. The changes are small but address a real user pain point identified in issue #556666.

Scores Summary

• Readability: 9/10 - Clear, concise language that's easy to understand. The note format makes the alternative method immediately apparent to users.
• AI Readiness: 8/10 - Good contextual information with clear section headings and step-by-step instructions. Could benefit from slightly more descriptive headings.
• Style Compliance: 9/10 - Excellent adherence to Expensify documentation standards with proper formatting, consistent terminology, and appropriate tone.

Key Findings

Positive Aspects:

• User-Centric Approach: Addresses a genuine user experience issue with practical fallback solutions
• Consistent Implementation: Both Apple Pay and Google Pay sections receive parallel updates, maintaining documentation consistency
• Clear Instructions: The alternative path through the Expensify app is explained with specific navigation steps
• Proper Formatting: Uses appropriate Note: callouts to highlight important information
• Accurate Terminology: Correctly uses "Apple Wallet" and "Google Wallet" (current branding)

Areas for Improvement:

• Minor Redundancy: The phrase "In some cases" appears in both notes - could be slightly varied for better readability
• Context Specificity: Could benefit from mentioning what types of issues users might encounter (e.g., "verification issues" or "compatibility problems")

Recommendations

Priority Actions (Optional Enhancements):

1. Vary Language Slightly: Consider rephrasing one of the "In some cases" openings to avoid repetition
2. Add Context: Briefly mention what might cause the direct method to fail (e.g., "due to verification requirements" or "compatibility issues")

Suggestions for Future Consideration:

• Consider adding troubleshooting tips for common wallet addition issues
• Could include screenshots of the Expensify app wallet section for visual guidance

Files Reviewed

• /docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md - Excellent quality update with clear, helpful additions that improve user experience

Overall Recommendation: ✅ Approve - This is a high-quality documentation improvement that addresses a real user need with clear, actionable guidance.

Note: This summary represents the comprehensive assessment of all documentation changes in the PR.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds helpful troubleshooting information to the Expensify Card mobile wallet documentation. The change addresses a real user issue where direct wallet app integration may fail, providing an alternative method through the Expensify app. The additions are concise, practical, and maintain consistency with the existing documentation structure.

Scores Summary

• Readability: 9/10 - Clear, concise language with proper formatting and logical flow
• AI Readiness: 8/10 - Good context and structure, though could benefit from more descriptive troubleshooting headings
• Style Compliance: 9/10 - Follows Expensify voice standards and maintains consistent formatting with existing content

Key Findings

• Positive aspects: The additions provide valuable troubleshooting information that directly addresses user pain points. The note format is appropriate and the instructions are clear and actionable.
• Good consistency: Both iOS and Android sections receive parallel treatment with identical note structures, maintaining documentation balance.
• Practical value: The fallback method using the Expensify app provides users with a reliable alternative when direct wallet integration fails.

Recommendations

• Minor enhancement: Consider adding a troubleshooting subsection header if this type of fallback information becomes common across card documentation.
• Future consideration: Monitor if additional troubleshooting scenarios emerge that might warrant a more comprehensive troubleshooting section.

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md: ✅ High quality addition with clear troubleshooting guidance

Note: The changes are minimal but highly effective, addressing a specific user issue with appropriate documentation enhancement.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a focused improvement to the Expensify Card documentation by adding crucial fallback instructions for users who cannot add their cards directly through Apple Wallet or Google Pay apps. The addition addresses a real user pain point identified in issue #556666 and provides clear alternative pathways.

Scores Summary

• Readability: 9/10 - Clear, concise language that's easy to understand at an 8th-grade reading level
• AI Readiness: 8/10 - Good context and clear instructions, though could benefit from more structured metadata
• Style Compliance: 9/10 - Excellent adherence to Expensify voice, proper terminology, and consistent formatting

Key Findings

Strengths:

• User-Centric Approach: Addresses a documented user frustration with a practical solution
• Consistent Implementation: Identical note structure for both iOS and Google Pay sections maintains documentation consistency
• Clear Navigation: Specific menu paths ("Account > Wallet") provide unambiguous directions
• Proper Formatting: Excellent use of bold formatting for UI elements and consistent markdown structure

Areas for Improvement:

• Proactive Guidance: Could mention upfront that users have multiple options for adding cards
• Troubleshooting Context: Brief explanation of why direct wallet addition might fail would be helpful

Recommendations

1. Consider Enhanced Introduction: Add a brief mention in the opening paragraph that multiple methods exist for adding cards
2. Maintain Current Quality: The writing style, tone, and formatting are excellent - continue this standard
3. Monitor User Feedback: Track if this resolves the reported issue and consider expanding troubleshooting if needed

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md: ✅ High quality addition that significantly improves user experience

Impact Assessment: This small but important change will likely reduce user frustration and support tickets by providing clear alternative steps when the primary method fails.

Note: This review covers all changes in the PR. The additions represent a valuable improvement to the documentation's practical utility.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR makes a focused improvement to the Expensify Card documentation by adding helpful fallback instructions for users who experience issues adding their card directly through Apple Wallet or Google Wallet apps. The changes address a real user pain point identified in issue #556666 and provide clear alternative steps.

Scores Summary

• Readability: 9/10 - Excellent clarity and user-friendly language with proper formatting
• AI Readiness: 8/10 - Good structure with clear headings, though could benefit from slightly more descriptive context
• Style Compliance: 9/10 - Follows established HelpDot patterns and maintains consistent voice

Key Findings

• Positive aspects: The added notes are well-placed, use consistent formatting with existing content, and provide actionable solutions
• Content quality: Clear, concise instructions that follow the established step-by-step format
• User experience: Addresses a real gap where users might get stuck without alternative options
• Consistency: Maintains the same note format and tone for both iOS and Android sections

Recommendations

• Consider enhancement: Add a brief explanation of why direct wallet addition might fail (e.g. due to security settings or device configuration) to give users more context
• Structure suggestion: The current placement at the end of each section is perfect - users try the primary method first, then see the alternative
• Terminology: All UI references are correctly formatted and consistent with HelpDot standards

Files Reviewed

• Add-Expensify-Card-to-Apple-or-Google-Pay.md - High quality addition with excellent user guidance

Note: This is a summary review. The changes demonstrate strong adherence to HelpDot documentation standards and provide genuine value to users who may encounter technical issues with direct wallet integration.

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR adds essential troubleshooting guidance for users who encounter issues adding their Expensify Card to mobile wallets. The change addresses a common user friction point by providing an alternative solution when the standard wallet app approach fails.

Scores Summary

• Readability: 9/10 - Clear, concise language with excellent user-friendly guidance
• AI Readiness: 8/10 - Well-structured content with proper context and navigation paths
• Style Compliance: 9/10 - Consistent with Expensify documentation standards and voice

Key Findings

Strengths:

• User-Centric Approach: Addresses a real user pain point with practical alternative solution
• Consistent Formatting: Proper use of bold formatting for UI elements (Account > Wallet, Add to Apple Wallet)
• Platform-Specific Guidance: Provides tailored instructions for both iOS and Android users
• Clear Alternative Path: Gives users a specific fallback when the primary method fails
• Maintains Document Flow: Notes are appropriately placed and don't disrupt the main instructions

Areas for Enhancement:

• Context Specificity: Could benefit from mentioning specific scenarios when direct wallet addition might fail
• Troubleshooting Depth: Minor opportunity to provide more detailed troubleshooting context

Recommendations

1. Maintain Current Quality: The addition demonstrates excellent documentation practices - clear, actionable, and user-focused
2. Consider Future Enhancements: Future iterations could potentially include:
   • Common error messages users might encounter
   • Visual indicators of when to use the alternative method
3. Documentation Pattern: This approach of providing fallback instructions should be considered as a template for other similar procedures

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md: Excellent - High-quality enhancement that improves user experience while maintaining documentation standards

Impact Analysis

Positive Impact:

• Reduces user frustration by providing clear alternative path
• Maintains consistency with existing documentation style
• Improves completeness of the card setup flow
• Enhances overall user success rate for mobile wallet setup

Strategic Value:

• Demonstrates proactive approach to user experience issues
• Follows best practices for comprehensive documentation
• Aligns with Expensify's commitment to user-friendly guidance

Recommendation: Approve - This is a well-crafted documentation improvement that enhances user experience while maintaining high quality standards.

[brianlee-expensify]

@sakluger is something wrong with github-actions?

[github-actions]

HelpDot Documentation Review

Overall Assessment

This PR addresses a practical user experience issue by adding helpful notes to the Expensify Card mobile wallet integration guide. The changes provide alternative instructions when the primary method fails, addressing a real-world scenario users encounter when adding cards directly through Apple Wallet or Google Wallet apps doesn't work.

Scores Summary

• Readability: 8/10 - Clear, concise language with proper grammar and structure
• AI Readability: 9/10 - Excellent context and descriptive navigation paths that are easily discoverable
• Style Compliance: 9/10 - Consistent with HelpDot standards and terminology

Key Findings

• Positive aspects: The additions directly address user pain points with practical solutions, maintain consistent formatting with existing content, and use proper Expensify terminology
• Content accuracy: Navigation paths are correctly specified and match the New Expensify app structure
• Formatting consistency: Proper use of Note prefixes and consistent markdown formatting with existing content
• User experience impact: Significantly improves the user experience by providing fallback instructions

Recommendations

• Minor enhancement suggestion: Consider adding a brief explanation of why this alternative method works
• Documentation completeness: The changes are complete and address the identified issue comprehensively

Files Reviewed

• docs/articles/new-expensify/expensify-card/Add-Expensify-Card-to-Apple-or-Google-Pay.md - Excellent improvement that enhances user experience with practical fallback instructions

Overall Recommendation: Approve - This is a valuable documentation enhancement that addresses real user needs with clear, consistent, and helpful content.

Note: The changes maintain high documentation quality standards and provide immediate value to users experiencing wallet integration issues.

[melvin-bot]

@brianlee-expensify looks like this was merged without a test passing. Please add a note explaining why this was done and remove the Emergency label if this is not an emergency.

[OSBotify]

🚀 Deployed to staging by https://github.com/brianlee-expensify in version: 9.2.32-0 🚀

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

[OSBotify]

🚀 Deployed to production by https://github.com/mountiny in version: 9.2.32-6 🚀

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