Can I keep building on Codemagic and use AppForShare?

Yes. Add one publishing script that uploads the .ipa, .apk or .aab, or use Connect Codemagic. Codemagic keeps building and signing.

Why not send the Codemagic download link?

You can. Its links in emails, Slack and build dashboards are valid for 24 hours, and files are kept 30 days to a year by plan. AppForShare gives an install page with an Install button and a QR code, links that stay while you subscribe, testers with no account, feedback and a readiness check.

Does AppForShare build my app like Codemagic?

No. It never builds on its own machines. It can set up builds on your own GitHub Actions minutes (Pro and Team).

Do I need a paid Codemagic team to share builds?

Not with AppForShare: a personal Codemagic account plus an AppForShare upload token is enough. Upload tokens are part of Pro and Team.

Does AppForShare register iPhones?

Yes, with an onboarding link and your App Store Connect API key (Pro). Codemagic's xcode-project use-profiles then fetches a profile with the new device on the next build.

Does AppForShare do over the air updates?

No. It shares whole builds; there is no SDK.

Is there an MCP server?

Yes, hosted with OAuth sign in (Pro and Team). Codemagic offers agent skills; no official Codemagic MCP server was found, though third party ones exist.

AppForShare Upload a build

Keep building on Codemagic, share builds and ship releases with AppForShare

Codemagic is a CI/CD service for mobile apps. It builds Flutter, React Native, native iOS and Android, Ionic, .NET MAUI, Kotlin Multiplatform and Unity apps from a codemagic.yaml file (or, for Flutter apps only, from its Workflow Editor with no file), on its own Mac mini M2, Mac mini M4, Mac Studio, Linux and Windows machines. It signs the app and publishes it to App Store Connect, Google Play, Firebase App Distribution, Huawei AppGallery and other stores. As listed on November 5, 2026, a personal account gets 500 free macOS M2 minutes a month with one member; pay as you go costs $0.095 a minute on a Mac mini M2, and Codemagic's docs say free minutes are not available to teams.

AppForShare does not build your app. It is the part after the build: install pages testers open without an account, iPhone device onboarding, feedback, a store readiness check on every build and the App Store and Google Play steps. Keep Codemagic and add one publishing script (or a post-publish script in the Workflow Editor) that uploads the finished .ipa, .apk or .aab, or let Connect Codemagic import finished builds with a Codemagic API token and nothing in codemagic.yaml.

Pick AppForShare if

You want testers to open an install page with an Install button and a QR code, not a file download link that stops working after 24 hours.
You want links that stay live while you subscribe, one channel link that always opens the newest build, with rollback, and an opt in build history page where QA installs any of the last 20 builds (Pro and Team).
You want Codemagic builds to reach testers with nothing in codemagic.yaml: Connect Codemagic reads finished builds with an API token and never starts or changes anything in Codemagic (Pro and Team).
You want to share builds from a personal Codemagic account, without paying for a Codemagic team just so a client or QA person can see builds.
Your testers and clients should install with no account, in their own language (13 install page languages), with no 20 tester cap.
You want iPhone testers to send their device through an onboarding link registered on Apple with your App Store Connect API key (Pro), and on Team a hands free flow that also remakes the profile and starts the build.
You want tester feedback with screenshots from the install page or from inside the test build through a link, with no SDK.
You want every build checked against App Store and Google Play rules before testers get it, with Flutter facts on the build page (build mode, engine or Dart version, an obfuscation hint) and a warning for a debug or profile Flutter build sent to testers.
You want to send the App Store build to TestFlight from the same place testers get their builds, and on Team give it to TestFlight groups and ask for beta review in the same confirm, done once Apple has processed it.
You want the store work after the upload: listing editor with screenshots and AI translation, App Store review checklist, Google Play rollouts and rollout plans, reviews inbox.
You build in more than one place (Codemagic, GitHub Actions, a laptop) and want every build in one dashboard, or you deliver apps to clients and want a client portal.

Pick Codemagic if

You need hosted Macs, including iOS builds without a Mac of your own. AppForShare does not build; at most it sets up builds on your own GitHub Actions.
You want to set up a Flutter app in the Workflow Editor with no YAML file.
You want build, signing and store publishing in one codemagic.yaml, with signing managed in the Codemagic UI.
You publish to Huawei AppGallery, Microsoft Store, Steam or the Snap Store. AppForShare covers the App Store and Google Play only.
You ship over the air updates with Codemagic Patch (CodePush) or Shorebird. AppForShare shares whole builds only.
You need SSO, an SLA, a SOC 2 Type 2 report or dedicated machines.
Your testers are developers who are fine with download links that last 24 hours and installing the file themselves.

Side by side

What it is: AppForShare
Test build sharing and store release steps for builds made by any CI, Codemagic included. Not a CI.; Codemagic
A mobile CI/CD service with its own macOS, Linux and Windows machines: build, sign, test and publish
Price: AppForShare
Free, Pro $12/month with a 7 day free trial, Team $39/month (5 seats). Yearly = 10 months. Lower regional prices in many countries.; Codemagic
Personal: 500 free macOS M2 minutes a month. Pay as you go: Mac mini M2 $0.095/min, Mac mini M4 $0.114/min, Linux and Windows $0.045/min, extra concurrency $49/month. Fixed annual from $3,990/year. Enterprise from $12,000/year
Free tier: AppForShare
Free: 150 MB per build, links live 7 days, 10 GB bandwidth a month, readiness check, feedback, UDID finder; Codemagic
500 macOS M2 minutes a month, 1 parallel build, 120 minute timeout, 1 member (collaborators cannot be invited); free minutes are not available to teams
Builds: AppForShare
Does not build. Takes builds from Codemagic, any CI or a laptop. Can set up iOS and Android builds on your own GitHub Actions minutes; a Flutter preset sets up the Flutter version the repository pins, with flavor, target file and build numbers (Pro up to 2 repositories, Team no limit).; Codemagic
Hosted Mac mini M2 and M4, Mac Studio M4 Max, Linux and Windows machines; Flutter versions preinstalled
Install links: AppForShare
Install page per build with an Install button for ad hoc, development and enterprise iPhone builds, a QR code and install help; Android APK, or .aab turned into an APK; Codemagic
Artifact download links in email, Slack and build dashboards; App Preview runs a simulator build in the browser. An iOS install page was not found in its docs
Link life: AppForShare
3 days without an account, 7 days Free, as long as you subscribe on Pro and Team; Codemagic
Links in emails, Slack and build dashboards are valid for 24 hours; links made in the UI last 24 hours, 3 days, 1 week or have no expiration
Build retention: AppForShare
Builds stay while their link lives (7 days on Free, while you subscribe on Pro and Team), within the plan's storage: 2 GB Free, 25 GB Pro, 150 GB Team; Codemagic
Artifacts kept 30 days on Free, 60 days on pay as you go, 1 year on fixed annual plans
Tester accounts: AppForShare
Never needed. Private projects for invited testers use an emailed link (Team).; Codemagic
Not needed to download from a public link; build dashboards and tester groups are team (paid) features
Tester limit: AppForShare
No tester cap; testers never take a seat. Tester groups, join links, install status and reminders (Team).; Codemagic
Tester groups by email, limited to 20 testers across all applications of a team by default
Link that always opens the newest build: AppForShare
Channel links (Beta, Live) with rollback; iPhone and Android on one link (Pro and Team). Opt in build history page with an Install button per build (Pro and Team); Codemagic
Build dashboard: a public page with the team's builds, release notes and artifacts, download links remade on each refresh
iOS devices: AppForShare
Free UDID finder built in, saves devices to your account, imports UDID lists. Pro adds an onboarding link per app and one click registration on Apple; Team can register, remake the profile and start the build hands free; Codemagic
Device registration link (valid 7 days) with a profile that sends the UDID to Codemagic, which adds the device to the Apple Developer Portal; needs a team and an App Store Connect API key
Install page languages: AppForShare
13 languages picked from the phone; Codemagic
Not found in its docs
Tester feedback: AppForShare
From the install page and from inside the test build through a link, with screenshots, no SDK (every plan with an account). TestFlight feedback in the same inbox (Team). Send to Linear or Jira (Pro and Team).; Codemagic
Not found in its distribution docs
Store readiness check: AppForShare
Every account build checked against App Store and Google Play rules, with a fix per issue. Flutter builds show build mode, engine or Dart version, an obfuscation hint and the Impeller flag, with lines for a debug or profile build sent to testers and an x86_64 only APK (Free and up); Codemagic
Not found in its docs; it runs your tests on emulators and device clouds
TestFlight: AppForShare
An Admin sends an uploaded App Store .ipa to TestFlight with What to Test (Pro); on Team the same confirm can give it to TestFlight groups and submit it for beta review once Apple has processed it; Codemagic
submit_to_testflight with beta_groups and What to Test in codemagic.yaml
App Store review: AppForShare
Checklist before sending, then an Admin sends, cancels, releases and controls the 7 day phased release (Pro and Team); Codemagic
submit_to_app_store with release type, release date and phased release
Google Play rollout: AppForShare
Send an .aab to a testing track with release name and update priority (Pro) or a production draft (Team); every track, release notes, promotion; production rollout set, raise, halt, resume, complete or a rollout plan, with crash and ANR rates shown read only (Team); Codemagic
Upload to any track with a fixed rollout fraction, in-app update priority, release name, draft and promotion to another track
Store listing: AppForShare
App Store and Google Play listing editor with screenshots and AI translation, reviews inbox with AI reply drafts (Pro and Team); Codemagic
App Store localizations through its CLI; a listing editor with screenshots was not found
Other stores: AppForShare
App Store and Google Play only; Codemagic
Huawei AppGallery, Microsoft Store, Steam, Snap Store, Firebase App Distribution, GitHub Releases and more
Over the air updates: AppForShare
No. Whole builds only, no SDK.; Codemagic
Codemagic Patch (CodePush) for React Native: first 100K monthly active users free, then $99/month per 100K
Members: AppForShare
Free and Pro 1 seat, Team 5 seats then $6 a month each; testers never need a seat; Codemagic
Free 1 member; unlimited members on paid plans
AI coding tools: AppForShare
Hosted MCP server with OAuth sign in, and an npm MCP package: uploads, links, readiness, testers, release status (Pro and Team); Codemagic
Official agent skills for setup and CodePush; no official MCP server found (third party ones exist)
CI: AppForShare
CLI with a Codemagic mode (release notes from the commit, --if-success, --pr-comment), GitHub Action, fastlane and Gradle plugins; Connect Codemagic imports finished builds with an API token (Pro and Team); Codemagic
Its own CI, REST API and codemagic-cli-tools

	AppForShare	Codemagic
What it is	Test build sharing and store release steps for builds made by any CI, Codemagic included. Not a CI.	A mobile CI/CD service with its own macOS, Linux and Windows machines: build, sign, test and publish
Price	Free, Pro $12/month with a 7 day free trial, Team $39/month (5 seats). Yearly = 10 months. Lower regional prices in many countries.	Personal: 500 free macOS M2 minutes a month. Pay as you go: Mac mini M2 $0.095/min, Mac mini M4 $0.114/min, Linux and Windows $0.045/min, extra concurrency $49/month. Fixed annual from $3,990/year. Enterprise from $12,000/year
Free tier	Free: 150 MB per build, links live 7 days, 10 GB bandwidth a month, readiness check, feedback, UDID finder	500 macOS M2 minutes a month, 1 parallel build, 120 minute timeout, 1 member (collaborators cannot be invited); free minutes are not available to teams
Builds	Does not build. Takes builds from Codemagic, any CI or a laptop. Can set up iOS and Android builds on your own GitHub Actions minutes; a Flutter preset sets up the Flutter version the repository pins, with flavor, target file and build numbers (Pro up to 2 repositories, Team no limit).	Hosted Mac mini M2 and M4, Mac Studio M4 Max, Linux and Windows machines; Flutter versions preinstalled
Install links	Install page per build with an Install button for ad hoc, development and enterprise iPhone builds, a QR code and install help; Android APK, or .aab turned into an APK	Artifact download links in email, Slack and build dashboards; App Preview runs a simulator build in the browser. An iOS install page was not found in its docs
Link life	3 days without an account, 7 days Free, as long as you subscribe on Pro and Team	Links in emails, Slack and build dashboards are valid for 24 hours; links made in the UI last 24 hours, 3 days, 1 week or have no expiration
Build retention	Builds stay while their link lives (7 days on Free, while you subscribe on Pro and Team), within the plan's storage: 2 GB Free, 25 GB Pro, 150 GB Team	Artifacts kept 30 days on Free, 60 days on pay as you go, 1 year on fixed annual plans
Tester accounts	Never needed. Private projects for invited testers use an emailed link (Team).	Not needed to download from a public link; build dashboards and tester groups are team (paid) features
Tester limit	No tester cap; testers never take a seat. Tester groups, join links, install status and reminders (Team).	Tester groups by email, limited to 20 testers across all applications of a team by default
Link that always opens the newest build	Channel links (Beta, Live) with rollback; iPhone and Android on one link (Pro and Team). Opt in build history page with an Install button per build (Pro and Team)	Build dashboard: a public page with the team's builds, release notes and artifacts, download links remade on each refresh
iOS devices	Free UDID finder built in, saves devices to your account, imports UDID lists. Pro adds an onboarding link per app and one click registration on Apple; Team can register, remake the profile and start the build hands free	Device registration link (valid 7 days) with a profile that sends the UDID to Codemagic, which adds the device to the Apple Developer Portal; needs a team and an App Store Connect API key
Install page languages	13 languages picked from the phone	Not found in its docs
Tester feedback	From the install page and from inside the test build through a link, with screenshots, no SDK (every plan with an account). TestFlight feedback in the same inbox (Team). Send to Linear or Jira (Pro and Team).	Not found in its distribution docs
Store readiness check	Every account build checked against App Store and Google Play rules, with a fix per issue. Flutter builds show build mode, engine or Dart version, an obfuscation hint and the Impeller flag, with lines for a debug or profile build sent to testers and an x86_64 only APK (Free and up)	Not found in its docs; it runs your tests on emulators and device clouds
TestFlight	An Admin sends an uploaded App Store .ipa to TestFlight with What to Test (Pro); on Team the same confirm can give it to TestFlight groups and submit it for beta review once Apple has processed it	submit_to_testflight with beta_groups and What to Test in codemagic.yaml
App Store review	Checklist before sending, then an Admin sends, cancels, releases and controls the 7 day phased release (Pro and Team)	submit_to_app_store with release type, release date and phased release
Google Play rollout	Send an .aab to a testing track with release name and update priority (Pro) or a production draft (Team); every track, release notes, promotion; production rollout set, raise, halt, resume, complete or a rollout plan, with crash and ANR rates shown read only (Team)	Upload to any track with a fixed rollout fraction, in-app update priority, release name, draft and promotion to another track
Store listing	App Store and Google Play listing editor with screenshots and AI translation, reviews inbox with AI reply drafts (Pro and Team)	App Store localizations through its CLI; a listing editor with screenshots was not found
Other stores	App Store and Google Play only	Huawei AppGallery, Microsoft Store, Steam, Snap Store, Firebase App Distribution, GitHub Releases and more
Over the air updates	No. Whole builds only, no SDK.	Codemagic Patch (CodePush) for React Native: first 100K monthly active users free, then $99/month per 100K
Members	Free and Pro 1 seat, Team 5 seats then $6 a month each; testers never need a seat	Free 1 member; unlimited members on paid plans
AI coding tools	Hosted MCP server with OAuth sign in, and an npm MCP package: uploads, links, readiness, testers, release status (Pro and Team)	Official agent skills for setup and CodePush; no official MCP server found (third party ones exist)
CI	CLI with a Codemagic mode (release notes from the commit, --if-success, --pr-comment), GitHub Action, fastlane and Gradle plugins; Connect Codemagic imports finished builds with an API token (Pro and Team)	Its own CI, REST API and codemagic-cli-tools

Codemagic details checked on November 2026 from its public pages (Codemagic pricing, Codemagic billing docs, Build dashboards, Tester groups, Email notifications, iOS device registration, Post-publish scripts, iOS code signing, App Store Connect publishing, Google Play publishing, Codemagic agent skills). Plans change; tell us at contact if something here is out of date.

Use both: Codemagic builds, AppForShare shares

Add APPFORSHARE_TOKEN as a Secure environment variable in a group (for example appforshare) and import the group in the workflow. Codemagic runs publishing scripts even when the build failed, so make touch ~/SUCCESS the last build script and run the upload only when that file exists: if [ -f ~/SUCCESS ]; then npx --yes appforshare upload build/ios/ipa --channel beta; fi. With CLI 1.20.0 or later, npx --yes appforshare@latest upload --if-success --channel beta does the check, picks the newest build file and writes the release notes from the last commit, the branch and the short commit.

For an iPhone install link, sign the build ad hoc: ios_signing with distribution_type: ad_hoc and your bundle_identifier, then xcode-project use-profiles, then flutter build ipa --release --export-options-plist=/Users/builder/export_options.plist. Do not add --export-method to that command. Prefer nothing in YAML? Connect Codemagic (Pro and Team) imports each finished build of the workflows you map, every 5 minutes, with a Codemagic API token stored encrypted. It only reads from Codemagic and never starts or changes builds.

Why not just send the Codemagic artifact link

You can, and for developers who install their own builds it works. As listed on November 5, 2026, Codemagic's docs say the download links in build emails, Slack messages and build dashboards are valid for 24 hours, and artifacts are kept 30 days on the free plan, 60 days on pay as you go and a year on fixed annual plans. A tester who opens last week's email gets an expired link, and an iPhone tester gets an .ipa file to download, not an Install button.

Said plainly, Codemagic is ahead on everything before the file exists: hosted Macs, iOS builds without a Mac, 500 free macOS minutes on a personal account, signing in its UI, the Flutter Workflow Editor, tests on device clouds, publishing to Huawei AppGallery, Microsoft Store and Steam, over the air updates with Codemagic Patch, App Preview in the browser, unlimited members on paid plans and enterprise options such as SSO and an SLA. AppForShare replaces none of that. It is worth adding when people outside the build team test: they get an install page that keeps working, in their language, a way to send their iPhone, and a feedback button, and you get the readiness check and the store steps.

Switching guides

Questions

Can I keep building on Codemagic and use AppForShare?: Yes. Add one publishing script that uploads the .ipa, .apk or .aab, or use Connect Codemagic. Codemagic keeps building and signing.
Why not send the Codemagic download link?: You can. Its links in emails, Slack and build dashboards are valid for 24 hours, and files are kept 30 days to a year by plan. AppForShare gives an install page with an Install button and a QR code, links that stay while you subscribe, testers with no account, feedback and a readiness check.
Does AppForShare build my app like Codemagic?: No. It never builds on its own machines. It can set up builds on your own GitHub Actions minutes (Pro and Team).
Do I need a paid Codemagic team to share builds?: Not with AppForShare: a personal Codemagic account plus an AppForShare upload token is enough. Upload tokens are part of Pro and Team.
Does AppForShare register iPhones?: Yes, with an onboarding link and your App Store Connect API key (Pro). Codemagic's xcode-project use-profiles then fetches a profile with the new device on the next build.
Does AppForShare do over the air updates?: No. It shares whole builds; there is no SDK.
Is there an MCP server?: Yes, hosted with OAuth sign in (Pro and Team). Codemagic offers agent skills; no official Codemagic MCP server was found, though third party ones exist.

Try it with your next build

No account needed for a first upload. Free accounts keep links for longer.

Upload a build Pricing