chore: unblock CI (iOS cocoapods install + pre-existing lint) - #972
Open
shahidrogers wants to merge 1 commit into
Open
chore: unblock CI (iOS cocoapods install + pre-existing lint)#972shahidrogers wants to merge 1 commit into
shahidrogers wants to merge 1 commit into
Conversation
The iOS build fails at the 'setup-cocoapods' step: it runs a global `gem install cocoapods -v 1.11.3` on the pinned Ruby 2.7.5, but the current `ffi` gem requires Ruby >= 3.0, so the install aborts before any build runs. That global CocoaPods is unused — `yarn pods` runs `bundle exec pod install`, which uses the Gemfile-locked CocoaPods (1.12.1 with ffi 1.15.5, both compatible with Ruby 2.7.5). Remove the redundant step so the workflow relies solely on the bundled CocoaPods. Also apply the auto-fixable prettier formatting in src/DatePickerIOS.js that was already failing the Lint check on master.
shahidrogers
had a problem deploying
to
e2e Android
July 3, 2026 02:29 — with 
GitHub Actions
Failure
GitHub Actions
Failure
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Unblocks the currently-red CI. Both fixes are correct for
masterbut, due to how CI is wired, can only take effect once merged — see the note at the bottom for why this PR's own checks stay red.1.
Build / iOS— CocoaPods install aborts before buildingThe
setup-cocoapodsstep runs a globalgem install cocoapods -v 1.11.3on the pinned Ruby 2.7.5, which now fails:That global CocoaPods is unused —
yarn podsrunsbundle exec pod install, which uses the Gemfile-locked CocoaPods (1.12.1, withffi 1.15.5— both compatible with Ruby 2.7.5). The precedingSetup Rubystep already runsbundle installviabundler-cache: true.Fix: remove the redundant
setup-cocoapodsstep so the workflow relies solely on the bundled CocoaPods. This removes the known blocker; a fully green iOS run can only be observed onmasterafter merge (or via a push/dispatch run of this branch's workflow on a fork).2.
Check / Lint— pre-existing prettier errorssrc/DatePickerIOS.jshas two auto-fixableprettier/prettiererrors that fail Lint onmaster. Appliedeslint --fix.Why this PR's own
Check / LintandBuild / iOSstay redpr.ymltriggers onpull_request_target, so both the reusable-workflow definitions and the defaultactions/checkoutare taken from the base branch (master), not from this PR:Check / Lintlintsmaster's code (this PR'sDatePickerIOS.jsfix is never checked out), so it keeps reporting the two pre-existing errors.Build / iOSrunsmaster'sbuild-ios.yml(still containingsetup-cocoapods), so it fails identically regardless of this PR's contents.Once merged,
push-main.ymlbuilds iOS with the corrected workflow, and every subsequent PR's Lint (which lintsmaster) goes green. Only CI config + formatting changes here — no library code.