Skip to content

New Feature: Add Make splits even functionality#73474

Merged
youssef-lr merged 20 commits into
Expensify:mainfrom
ikevin127:ikevin127-splitEvenly
Nov 4, 2025
Merged

New Feature: Add Make splits even functionality#73474
youssef-lr merged 20 commits into
Expensify:mainfrom
ikevin127:ikevin127-splitEvenly

Conversation

@ikevin127

@ikevin127 ikevin127 commented Oct 25, 2025

Copy link
Copy Markdown
Contributor

Explanation of Change

Add a Make splits even button into the split edit table that will set the amounts (or percentages in the Split by percentage view) to equal proportions of the original expense amount.

  • The ‘Make splits even’ button will only be available during the initial split
  • The 'Make splits even' button will not be available when editing splits to avoid adding more logic to start
  • When an amount cannot be split evenly, we'll add the remainder to one of the expenses. Ex. a $1 expense, split 3 ways + Make splits even will result in two .33 splits and one .34 split

Fixed Issues

$ #72207
PROPOSAL:

Tests

Even splits

  1. Create an expense for $10.
  2. Select 'Split' from the 'More' menu for the expense.
  3. Tap 'Add split' to create a 3rd split.
  4. Tap 'Add split' to create a 4th split.
  5. Tap 'Make splits even'.
  6. Verify the amounts of the split expenses are all $2.50.

Uneven splits

Case 1

  1. Create an expense for $10.
  2. Select 'Split' from the 'More' menu for the expense.
  3. Tap 'Add split' to create a 3rd split.
  4. Tap 'Make splits even'.
  5. Verify the amounts of the split expenses are $3.33, $3.33, $3.34.

Case 2

  1. Create an expense for $1.01.
  2. Select 'Split' from the 'More' menu for the expense.
  3. Tap 'Add split' to create a 3rd split.
  4. Tap 'Make splits even'.
  5. Verify the amounts of the split expenses are $0.33, $0.33, $0.35.

Case 3

  1. Create an expense for $1001.
  2. Select 'Split' from the 'More' menu for the expense.
  3. Tap 'Add split' to create a 3rd split.
  4. Tap 'Make splits even'.
  5. Verify the amounts of the split expenses are $333.66, $333.66, $333.68.

Editing splits

  1. Create an expense for $10.
  2. Select 'Split' from the 'More' menu for the expense.
  3. Click 'Save'.
  4. Open one of the splits and select 'Edit Split' from the 'More' menu for the expense.
  5. Verify the 'Make splits even' button does not show.
  • Verify that no errors appear in the JS console

Offline tests

  1. Open a new split flow, add splits, tap “Make splits even” and verify amounts update immediately.
  2. Tap Save; verify optimistic UI (pending indicators: splits grayed out).
  3. Reconnect; verify splits persist and pending clears without errors.

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
    • 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
    • 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: HybridApp
android-hybrid.mp4
Android: mWeb Chrome
android-mweb.mp4
iOS: HybridApp
ios.mov
iOS: mWeb Safari
ios-mweb.MP4
MacOS: Chrome / Safari
web.mov
MacOS: Desktop
desktop.mov

@ikevin127 ikevin127 requested a review from a team as a code owner October 25, 2025 01:06
@melvin-bot melvin-bot Bot requested review from parasharrajat and removed request for a team October 25, 2025 01:06
@melvin-bot

melvin-bot Bot commented Oct 25, 2025

Copy link
Copy Markdown

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

@ikevin127

This comment was marked as outdated.

@codecov

codecov Bot commented Oct 25, 2025

Copy link
Copy Markdown

Codecov Report

❌ Patch coverage is 60.00000% with 12 lines in your changes missing coverage. Please review.

Files with missing lines Patch % Lines
src/pages/iou/SplitExpensePage.tsx 0.00% 10 Missing ⚠️
src/libs/actions/IOU.ts 84.61% 2 Missing ⚠️
Files with missing lines Coverage Δ
src/libs/IOUUtils.ts 62.85% <100.00%> (+62.85%) ⬆️
src/libs/actions/IOU.ts 63.51% <84.61%> (+59.23%) ⬆️
src/pages/iou/SplitExpensePage.tsx 0.00% <0.00%> (ø)

... and 366 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@ikevin127

Copy link
Copy Markdown
Contributor Author

@parasharrajat Please hold on reviewing until we get answers to this comment.

@parasharrajat

Copy link
Copy Markdown
Member

Better to clarify on issue @ikevin127

@garrettmknight

Copy link
Copy Markdown
Contributor

the issue title mentions + move 'Add split' below which I wasn't sure about so I just added the 'Split evenly' next to the 'Add split' until we clear this up with the design team because the design mock also mentions the button name as Make splits even whereas the issue title + description mentions 'Split evenly'. Current vs post 'Split evenly' addition splits design looks like this compared to the issue OP design:

Let's update to the OP design. We're going to be working on some changes in quick follow ups that require it:

when splits page opens and we have default (2-way split), the 'Split evenly' button does nothing since 2-way split is already even by default when page opens

That's correct. This button shouldn't appear/disappear based on the split amounts, it should always be there, even if it doesn't do anything when the splits are already even.

@ikevin127 ikevin127 changed the title New Feature: Add Split evenly functionality New Feature: Add Make splits even functionality Oct 28, 2025
@melvin-bot

melvin-bot Bot commented Oct 28, 2025

Copy link
Copy Markdown

Hey, I noticed you changed src/languages/en.ts in a PR from a fork. If you want to automatically generate translations for other locales, you can run the Generate static translations GitHub workflow.

Please look at the code and make sure there are no malicious changes before running the workflow.

If you have the K2 extension, you can simply click: [this button]

@ikevin127

Copy link
Copy Markdown
Contributor Author

@Expensify/design PR was updated to match design UI / functionality. Please review the updated videos and let me know if there are any spacing concerns / changes needed - so otherwise @parasharrajat can start reviewing! 🙌

@dubielzyk-expensify

Copy link
Copy Markdown
Contributor

Looks mostly good to me. Is the height of the page header/app bar the same as the others? I looks like it has more padding on the bottom and cuts off differently to the one underneath:
CleanShot 2025-10-29 at 15 54 38@2x

sections[0].data.filter((item) => {
if (isSelected) {
return isSelected(item);
((sections?.[0]?.data ?? []) as unknown[]).filter((item): item is TItem => {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Please don't infer type to unknown correct the type instead.

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.

Reverted the changes as I went with using listFooterContent (thanks for that), so this type mess is not needed anymore 😅

// Filter out enhanced sections (those whose items contain a `component` prop)
const baseSections = useMemo(() => {
const secs = Array.isArray(sections) ? sections : [];
return (secs as Array<SectionListDataType<TItem> | {data?: unknown[]}>).filter((section): section is SectionListDataType<TItem> => {

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

same

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.

Reverted the changes as I went with using listFooterContent (thanks for that), so this type mess is not needed anymore 😅

Comment thread src/pages/iou/SplitExpensePage.tsx Outdated
Comment on lines +316 to +328
const enhancedSections = useMemo(
() => [
...sections,
{
data: [
{
key: CONST.ENHANCED_SECTIONS.SPLIT_EXPENSE_ACTIONS,
component: ActionButtons,
},
],
},
],
[sections, ActionButtons],

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

We don't need these. Can we just use listFooterContent prop on SelectionList

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.

Yes, that's a way better option 👍 💯

@dannymcclain

Copy link
Copy Markdown
Contributor

Looking pretty good to me too! @dubielzyk-expensify Do we want the option rows to be 8px away from the expenses like they are currently? Or should they be 20px away? I don't hate how it is now honestly.

Is there a reason why when you go into Edit splits there's no Make splits even button?

Also, it looks like we have some extra padding above the Save button (apologies for how hard it is to see in these screenshots):
CleanShot 2025-10-29 at 09 05 19@2x
CleanShot 2025-10-29 at 09 05 52@2x

@ikevin127

Copy link
Copy Markdown
Contributor Author

Is the height of the page header/app bar the same as the others? I looks like it has more padding on the bottom and cuts off differently to the one underneath

@dubielzyk-expensify removed that as it was leftover from previously having the buttons up there

Do we want the option rows to be 8px away from the expenses like they are currently? Or should they be 20px away? I don't hate how it is now honestly.

@dannymcclain I kept that space as it is between the expenses (4px coming from the top expense bottom / 4px from the top of the Add split / Make splits even buttons container) - but if we want to increase the space, it can be arranged.

Is there a reason why when you go into Edit splits there's no Make splits even button?

Yes, this was done on purpose as the issue's OP instructed in the Feature description section point 2:

  • The 'Split evenly' button will not be available when editing splits to avoid adding more logic to start

☝️ It will be probably added eventually, we just skipped it here in the first PR.

Also, it looks like we have some extra padding above the Save button

That was always there (can check current production), but I removed it now, here's how things look with all changes applied:

Screen.Recording.2025-10-29.at.13.33.26.mov

@Expensify/design Are we good with how this looks - any other changes / adjustments required ?

By the way, at the bottom of the Add split / Make splits even buttons container we have 12px margin bottom, this was there before as well, but thought I should mention it in case we want to adjust that as well:

Screenshot 2025-10-29 at 13 50 36

@melvin-bot

melvin-bot Bot commented Oct 29, 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

@ikevin127

ikevin127 commented Nov 1, 2025

Copy link
Copy Markdown
Contributor Author

Yeah, let's update to keep expected similar result all the time.

@parasharrajat 🟢 Logic updated, now the remainder is always on the last split which will always be the largest. Just note that in the case of $1.01 which when pressed Split, initial split is 51¢ / 50¢, now when pressed Make splits even it changes the splits to 50¢ / 51¢ according to the new logic.

435yyrtghgmht.mov

Removed the additional tests for uneven splits ✅

Comment thread src/libs/actions/IOU.ts Outdated
Comment thread src/libs/actions/IOU.ts Outdated

@parasharrajat parasharrajat left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

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 tests pass on all platforms & I tested again on:
    • Android: Native
    • Android: mWeb Chrome
    • iOS: Native
    • iOS: mWeb Safari
    • MacOS: Chrome / Safari
    • MacOS: Desktop
  • If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
  • I verified proper code patterns were followed (see Reviewing the code)
    • I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
    • I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
    • 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 approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
    • 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.js 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 form input styles:
    • I verified that all the inputs inside a form are aligned with each other.
    • I added Design label 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.
  • 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

🔲 iOS / native

01.11.2025_19.12.00_REC.mp4

🔲 iOS / Safari

01.11.2025_19.14.17_REC.mp4

🔲 MacOS / Desktop

01.11.2025_19.21.15_REC.mp4

🔲 MacOS / Chrome

01.11.2025_18.55.31_REC.mp4

🔲 Android / Chrome

01.11.2025_19.22.48_REC.mp4

🔲 Android / native

01.11.2025_19.18.48_REC.mp4

🎀 👀 🎀 C+ reviewed

@melvin-bot

melvin-bot Bot commented Nov 1, 2025

Copy link
Copy Markdown

We did not find an internal engineer to review this PR, trying to assign a random engineer to #72207 as well as to this PR... Please reach out for help on Slack if no one gets assigned!

@melvin-bot melvin-bot Bot requested a review from youssef-lr November 1, 2025 21:56
Comment thread src/libs/actions/IOU.ts Outdated
@ikevin127

Copy link
Copy Markdown
Contributor Author

Note: The ❌ eslint / typecheck / prettier are not directly related to this PR, they come from the MoneyRequestParticipantsSelector because I merged main, I'm awaiting for the offending PR author to resolve the issue after which I will merge main again ✅ Asked on Slack about it.

@ikevin127

Copy link
Copy Markdown
Contributor Author

🟢 Ready for review! Merged main again to resolve the☝️ failing workflows coming from main.

@youssef-lr youssef-lr 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

@youssef-lr youssef-lr merged commit 1c4a867 into Expensify:main Nov 4, 2025
26 checks passed
@OSBotify

OSBotify commented Nov 4, 2025

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

OSBotify commented Nov 5, 2025

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.2.45-0 🚀

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

francoisl added a commit that referenced this pull request Nov 5, 2025
luacmartins added a commit that referenced this pull request Nov 5, 2025
Revert #73474 – "New Feature: Add Make splits even functionality"
OSBotify pushed a commit that referenced this pull request Nov 5, 2025
Revert #73474 – "New Feature: Add Make splits even functionality"

(cherry picked from commit 3c43ccb)

(cherry-picked to staging by luacmartins)
@OSBotify

OSBotify commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.45-6 🚀

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

@OSBotify

OSBotify commented Nov 6, 2025

Copy link
Copy Markdown
Contributor

🚀 Deployed to staging by https://github.com/youssef-lr in version: 9.2.46-0 🚀

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

@OSBotify

OSBotify commented Nov 7, 2025

Copy link
Copy Markdown
Contributor

🚀 Deployed to production by https://github.com/luacmartins in version: 9.2.46-3 🚀

platform result
🖥 desktop 🖥 success ✅
🕸 web 🕸 success ✅
🤖 android 🤖 success ✅
🍎 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.

7 participants