Official Bitrise Step
Thesetup-asc Bitrise step provides seamless integration for App Store Connect automation:
- Install mode - Set up
ascfor subsequent steps - Run mode - Install and execute commands in one step
- Environment variable support - Automatic authentication via Bitrise secrets
Quick Start
Basic Workflow
bitrise.yml
Step Configuration
Inputs
| Input | Description | Required | Default |
|---|---|---|---|
mode | Operation mode: install or run | Yes | install |
version | Version to install (latest, 1.0.0, etc.) | No | latest |
command | Command to run (only for run mode) | No* | - |
mode: run
Install Mode
Installsasc and makes it available for subsequent steps:
Run Mode
Installs and executes a command in one step:Complete Workflows
TestFlight Distribution
bitrise.yml
App Store Submission
bitrise.yml
Metadata Sync
bitrise.yml
Crash and Feedback Monitoring
bitrise.yml
Authentication Setup
Bitrise Secrets
- Navigate to your app’s Workflow Editor
- Select the Secrets tab
- Add the following secrets:
| Secret Key | Description | Example |
|---|---|---|
ASC_KEY_ID | App Store Connect Key ID | ABC12345 |
ASC_ISSUER_ID | App Store Connect Issuer ID | 12345678-1234-1234-1234-123456789012 |
ASC_PRIVATE_KEY_B64 | Base64-encoded private key | LS0tLS1CRUdJTi... |
APP_ID | Your app’s ID (optional) | 123456789 |
Base64 Encoding Private Key
Environment Variables in Workflow
Secrets are automatically exposed as environment variables:Advanced Patterns
Conditional Workflows
Multiple App Deployment
Retry Logic
Stack Configuration
Required Stack
Use the Xcode stack for iOS/macOS builds:Linux Stack for Metadata Only
For metadata-only operations, Linux stacks work:Debugging
Enable Debug Logging
Test Authentication
Troubleshooting
Step not found
Step not found
- Verify the step URL:
git::https://github.com/rudrankriyam/steps-setup-asc.git@main - Check your Bitrise stack supports Git-based steps
- Ensure you have network connectivity to GitHub
Authentication failed
Authentication failed
- Verify secrets are set in Bitrise Secrets tab
- Check “Expose for Pull Requests” if testing PRs
- Ensure private key is properly base64-encoded without newlines
- Test credentials locally with the same key
Command not found
Command not found
- Verify
mode: installwas run before usingasc - Check step order in workflow
- Use
mode: runto combine install and execution
Upload timeout
Upload timeout
- Increase timeout in workflow:
- Check IPA file size and network speed
- Consider splitting large uploads
Best Practices
Use install mode for multiple commands
Install once, run many commands:
Set timeouts
Configure appropriate timeouts:
Use Bitrise secrets
Never hardcode credentials. Always use secrets.
Enable retry for uploads
Implement retry logic for network-dependent operations.
Bitrise-Specific Features
Expose for Pull Requests
Allow PR builds to use secrets (use with caution):- Go to Secrets tab
- Enable Expose for Pull Requests for required secrets
- Consider using separate staging credentials for PRs
Stack Selector
Choose appropriate stack based on operation:- Xcode stack: iOS/macOS builds and uploads
- Linux stack: Metadata, monitoring, API-only operations
Build Artifacts
Store outputs usingdeploy-to-bitrise-io:
