Skip to content

Conversation

@ssestak
Copy link
Contributor

@ssestak ssestak commented Nov 5, 2025

This PR introduces ios_root_path and custom_build_path inputs to the iOS Fastlane actions.
These inputs provide greater flexibility in specifying the working directories for bundle install and fastlane execution.
The KMP workflows are updated to utilize these new parameters.

Key Features

  • ios_root_path input: Allows specifying the path to the iOS project root directory containing the Gemfile for bundle install.
  • custom_build_path input: Allows specifying the path to the directory containing the Fastfile for fastlane execution.
  • Improved flexibility: Enables Fastlane actions to be used in projects with non-standard directory structures.
  • KMP workflow updates: ios-kmp-selfhosted-release and ios-kmp-selfhosted-test workflows now use the new `ios-fast

Šimon Šesták and others added 5 commits November 5, 2025 10:57
The beta.sh and test.sh scripts were running bundle install before
changing to the CUSTOM_BUILD_PATH directory. This caused them to install
gems from the wrong Gemfile (root directory instead of the iOS directory).

Now the scripts:
1. Change to CUSTOM_BUILD_PATH first (if specified)
2. Install bundler
3. Run bundle install (which now uses the correct Gemfile)
4. Run fastlane commands

This ensures fastlane and other iOS-specific gems are installed from
the correct Gemfile location.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
…tructures

This change supports iOS projects with multiple apps under a single iosApp directory,
where the Gemfile is at the root (iosApp/) but Fastfiles are in subdirectories
(e.g., iosApp/appA/, iosApp/appB/).

Changes:
- Added ios_root_path input: Path to iOS project root with Gemfile
- custom_build_path now means: Path to directory with Fastfile
- Scripts install gems from ios_root_path, run fastlane from custom_build_path
- Updated ios-kmp-build to always use iosApp as ios_root_path

Use cases supported:
1. Single app in iosApp: only set custom_build_path=iosApp
2. Multiple apps: ios_root_path=iosApp, custom_build_path=iosApp/appA
3. Backwards compatible: only custom_build_path works as before

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Update the input description to reflect the new behavior where
custom_build_path expects the full path to the Fastfile directory
(e.g., iosApp/appA) rather than a relative path.

This aligns with the changes made to ios-kmp-build action.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
…-release

Apply the same path separation pattern to ios-fastlane-release action
that was implemented for beta and test actions.

This ensures consistent behavior across all iOS fastlane actions and
supports multi-app iOS project structures.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
Replace inline fastlane commands with ios-fastlane-test and
ios-fastlane-release composite actions for consistency and
maintainability.

Benefits:
- Consistent behavior across all workflows
- Single source of truth for fastlane execution
- Easier to maintain and update
- Supports future path customization if needed

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <[email protected]>
@ssestak ssestak requested a review from matejsemancik November 5, 2025 10:25
@ssestak ssestak merged commit a11d642 into main Nov 5, 2025
1 check passed
@ssestak ssestak deleted the fix/ios-kmp-build-working-directory branch November 5, 2025 11:41
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.

3 participants