Your mobile app is ready. Manus packages it for testing: an iOS build goes to App Store Connect for TestFlight, while an Android AAB is ready for you to upload to Google Play Console.
Choose the path for your phone, then invite people to try the result.
To publish an app on the App Store, start with TestFlight beta testing. Manus creates the iOS app in your Apple Developer account and uploads the build to App Store Connect; you invite testers after Apple processes it.
To publish an Android app to Google Play, Manus first packages an AAB file. In your Google Play Console, start with Google Play internal testing for a small team, then use Google Play closed testing or open testing to reach more people.
Turn on Develop apps in Manus. You need an Apple Developer account to share on TestFlight or a Google Play Developer account to upload an Android build, plus an Expo account for the access token Manus asks for.
Wondering how to get your app on the App Store after testing? Gather screenshots, a description, and a privacy policy, and check Apple’s App Store Review Guidelines. Then make your App Store submission in App Store Connect, or submit the release in Google Play Console.
After changing your app, prepare another test build. TestFlight can deliver an updated iOS build; for Android, package and upload a new AAB to your Play Console testing track.
Here is how to put an app on the App Store or Google Play once testing is done: you finish the public submission in your own store account.
Not directly to a public listing. For an app made in Manus, the iOS publishing flow creates the app in your Apple Developer account and uploads the build to App Store Connect for TestFlight testing. You submit it for public App Store review yourself in App Store Connect.
Manus packages a mobile app made there as an Android App Bundle (AAB). You upload the AAB to your Google Play Console, select a testing track, and manage any public release there. Manus does not publish it live for you.
Yes. You need an Apple Developer account for TestFlight sharing or a Google Play Developer account to upload an Android app in Google Play Console. You also need an Expo account for the access token, and the Develop apps capability must be enabled in Manus.
Manus uses Expo’s services to build your app and, for iOS, to submit the build to App Store Connect. Create a personal access token in your Expo account, not a robot-user token, and paste it when Manus asks; if it expires, Manus asks for a new one. You don’t run Expo EAS Submit or other commands yourself. For Android, you upload the AAB in Google Play Console.
TestFlight is Apple’s service for testing an iOS app before it is live on the App Store. Here is how to use TestFlight with Manus: after Apple processes the uploaded build, your developer email receives an invitation. On iPhone, install the TestFlight app and accept the invitation to install the test build. Invite other internal or external testers in App Store Connect; external testing needs Apple’s review.
An AAB file, or Android App Bundle, is the file you upload to Google Play Console for an Android app. You don’t package it yourself: in Manus, open Publish to Google Play and choose Build for publish. Manus builds the AAB with Expo; you download it and upload it to your testing track.
This publishing flow is for mobile apps made with Manus using Develop apps. Manus works as an Expo app builder: you preview the app on your phone in Expo Go, and Manus packages it with Expo into an iOS build for TestFlight or an Android AAB for Google Play Console.
Prepare your listing materials, including screenshots, a description, and a privacy policy. In your own App Store Connect account, submit the app for public review. Sending a build to TestFlight does not make it live on the App Store.
No. Apple decides during review, so Manus cannot guarantee approval. To prepare, test with TestFlight first, read Apple’s App Store Review Guidelines, and get your screenshots, description, and privacy policy ready. In the same task, you can ask Manus to check the app against the guidelines, fix what it finds, and draft listing text. If Apple rejects the app, read the reason in App Store Connect, ask Manus to make the changes, and prepare a new build.
Upload the AAB from Manus to your Google Play Console, choose an internal, closed, or open testing track, and collect feedback. For a public release, finish your listing materials and release steps in Play Console.
Yes. After updating your mobile app, prepare another test build. TestFlight testers can update to a newer iOS build. For Android, package another AAB and upload it to your Play Console testing track.
No. This workflow is for test distribution. The iOS build goes to App Store Connect and TestFlight; for Android, Manus prepares an AAB for you to upload to Play Console. You handle any public store submission separately.