Question 1

What kinds of repos work with Corenna?

Accepted Answer

Three stacks. Web apps wrapped with Capacitor (what Lovable, Bolt, v0 and Replit produce), Flutter projects with a pubspec.yaml, and React Native projects with committed android/ and ios/ folders. Paste your repo into the free check at /check and it tells you which one you have, and whether it is ready, before you create an account.

Question 2

Does Corenna build Flutter apps?

Accepted Answer

Yes. It runs flutter build appbundle and flutter build ipa on hosted runners and signs the result with your own keystore and Apple certificate. Your android/ and ios/ folders need to be committed — Corenna builds the native projects in your repo rather than generating them.

Question 3

Does Corenna work with Expo?

Accepted Answer

With a prebuilt Expo app, yes. Run npx expo prebuild and commit the android/ and ios/ folders, then Corenna builds them like any React Native project. A managed Expo app with no native folders is refused up front, with that instruction, rather than failing part-way through a build.

Question 4

What is not supported?

Accepted Answer

Repos that are already plain native Android or iOS projects with no web, Dart or React Native layer are not built yet. Neither is anything that needs custom Swift or Kotlin you have not written — Corenna builds what is in the repo, it does not write native code for you. If you lost your original signing key and are not on Play App Signing, that listing cannot be updated by anyone, us included.

Question 5

What do I get out of a build?

Accepted Answer

For Android: a signed .apk for testing and a signed .aab for the Play Store, which Corenna can send straight to Google Play for you. For iOS: a signed .ipa ready for TestFlight or App Store Connect.

Question 6

Can Corenna publish updates to Google Play for me?

Accepted Answer

Yes. Connect a Google Play service account once, and every signed .aab can go straight to your internal testing, closed testing, open testing or production track, with release notes. No Android Studio build and no manual upload in the Play Console, and you can do it from your phone. Updates are signed with the key your app already uses and keep the package ID from your repo, so they land on your existing listing with its reviews and installs. Every build gets a higher version code; if your app is already on Play, set the project's next build number above your latest release once and Corenna counts up from there. One thing Google does not allow: a brand-new app's very first release has to be created by hand in the Play Console. Every update after that can come from Corenna. For iOS, Corenna builds the signed .ipa without a Mac, and you upload it to App Store Connect.

Question 7

Can I test the app before I submit it to the stores?

Accepted Answer

Yes, on Android. Every build produces an .apk, which is an installable app rather than a store upload — put it on your own phone, and send the file to anyone else you want trying it. They allow installs from whichever app delivered it, the same prompt any sideloaded app shows. Nothing goes near Google Play, so there is no review to wait on and no test track to set up. Test builds are signed with the same key as your release, so a later update installs over the top. iPhone works differently: Apple only installs on a device it already knows, so sharing an .ipa means TestFlight or a provisioning profile listing that device.

Question 8

Do you store my source code?

Accepted Answer

No. We only orchestrate builds on GitHub Actions runners inside your own repo. Corenna never clones your source to its own servers.

Question 9

Do I still need an Apple Developer account, or do you create the certificate?

Accepted Answer

You need your own Apple Developer account, and Apple is the only party that can issue a distribution certificate — so you make one trip to the developer portal for a certificate and a provisioning profile matching your bundle ID, then upload both here once. Everything after that is ours: the build keychain, importing the .p12 with the right partition list, keeping the keychain unlocked through the archive, reading the UUID out of your profile for manual signing, and the ExportOptions.plist that -exportArchive needs. Corenna also parses the profile before any build runs and tells you if the Team ID, bundle ID or expiry do not match what you are building, which is the failure most people hit. Android is different: there Corenna generates the keystore on your first build and shows you the password to save.

Question 10

How are keystores and certificates stored?

Accepted Answer

Encrypted at rest using authenticated encryption. Passwords are never logged. You can revoke or delete signing materials at any time. See the Security page for full details.

Question 11

Is there a free build?

Accepted Answer

Yes — one. Your first successful Android build is free and needs no card, so you can install the signed .apk on your own phone and hand it to someone before deciding. Failed builds never count, so you can retry as often as you need to get there. After that, and for every iOS build, it is $2.99/month. Sandbox builds on Android and iOS, which verify your setup without publishing an artifact, stay free either way.

Question 12

What happens when a build fails?

Accepted Answer

We capture the GitHub Actions log, parse the error, and present a human-readable summary plus the raw stderr. You can retry directly from the project view.

Question 13

Do I need my own Apple Developer account for iOS?

Accepted Answer

Yes. iOS code-signing requires an Apple Developer Program membership ($99/year, paid to Apple). Corenna does not resell Apple memberships.

Question 14

Do iOS builds cost extra per run?

Accepted Answer

iOS builds consume your GitHub Actions macOS minutes. Public repos get generous free minutes; private repos are billed by GitHub. Corenna itself does not charge per build.

Question 15

Can I cancel and keep my work?

Accepted Answer

Yes. Export your project metadata, signing config, and a self-host workflow bundle anytime. Cancelling stops billing but doesn't touch your GitHub repo.

Question 16

How do refunds work?

Accepted Answer

We offer a 30-day money-back guarantee. Refunds are processed by Paddle — see the Refund Policy for details.