Deutsch
Publishing to stores from Forge
Upload a finished Forge build to itch.io, Google Play, App Store Connect or Forge's own web hosting with one button, and what each store needs first.
Auf dieser Seite
Forge can upload a finished build to a store. It never does so on its own: a green build is not a release, so publishing is a button you press on the build, and it asks you to confirm.
Set up a store
A store's login is an account, and it is yours rather than one project's. On Stores, add one for the store: it takes the store's name, holds the API key or key file, and every project of yours can use it. Add a second for the same store if you publish as more than one.
Then open the project from Projects, go to its Stores tab, pick the account for each store, and fill in what is the game's own: its itch.io page, or its Play package and track. Web hosting needs no account.
| Store | Takes | Guide |
|---|---|---|
| itch.io | every target except ios; the APK for android |
itch.io |
| Google Play | android, as an APK or an App Bundle |
Google Play |
| App Store Connect | ios |
App Store |
| Web hosting | web, served by Forge at an address you claim |
Web hosting |
Credentials here are kept like signing keys: encrypted when saved, never shown again, and handed only to the upload for that store.
Publish
On a build's page, every succeeded target that a configured store takes has a Publish to … button. Press it, confirm, and the upload runs on a builder and reports back on the same card — the store, whether it worked, and what the store said if it did not.
Stores check signatures, so sign first: Google Play and the App Store refuse
an unsigned android or ios build. See Signing.