Upload your app
Upload your app
Upload your source code as a .zip — Releasely builds it for you — or a ready-made binary. The rules shared by every framework.
On your project's Upload screen, there are two ways to bring your app into Releasely:
- Source code (
.zip) — you upload your project folder and Releasely builds it for you on its cloud (including the iOS side, which normally requires a Mac). No tooling to install, no CI to configure. - Binary (
.ipaor.aab) — your app is already built elsewhere; Releasely then only takes care of delivering it to the stores.
This section covers what the source-code .zip should contain, framework by framework.
Rules shared by every framework
Whatever your framework, the same principles apply:
- One project per archive,
.zipformat only, 2 GB maximum. - The project's manifest file (e.g.
pubspec.yamlfor Flutter) must sit at the root of the archive: opening the.zipshould show it directly, not buried inside nested folders. - We build only what's in the archive. Dependencies published on public registries (pub.dev,
npm…) are downloaded automatically during the build — but everything else (local packages,
private git repositories) must be included in the
.zip. - No signing secrets in the archive. Keys and keystores are provided on your project's
Credentials screen in Releasely, never inside the
.zip. - The build number is computed automatically (incrementing the last known build). You can override it at upload time if needed.
What's heavy is usually unnecessary
Build folders, caches, and git history account for most of a project's weight — and the cloud build doesn't need any of them. Each framework page lists exactly what to exclude.
Pick your framework
Flutter project
What the .zip must contain, what Releasely downloads for you, and what to leave out.
React Native project
Coming soon — the React Native guide is on its way.