Can someone use the page to skip a build's password?

No. Each build still asks for its own password or access code, and its release notes stay hidden until it is unlocked.

No. It is off for every project until someone turns it on.

How is it different from a channel link?

A channel link always opens the newest build of that channel. The build history page lists the last 20 builds so testers can install an older one.

Which plan do I need?

Pro or Team. White label and a custom domain are on Team.

AppForShare Create a free account

Every recent build of an app on one page, ready to install

Pro and Team

A channel link always opens the newest build. QA often needs an older one too: to check when a bug came in, or to test an update from last week's version. Digging through old emails and chat messages for the right link takes longer than the test.

The build history page puts the last 20 builds of an app on one page, newest first, each with a real Install button. The iOS and Android builds of one version sit side by side.

Start free See plans

Example

Notes app, build history

1.8.0 (61), iOS and AndroidBeta, Install
1.7.2 (58), iOS and AndroidLive, Install
1.7.1 (55), AndroidPassword needed
1.7.0 (52), iOSRetired

Each build keeps its own password, access codes and link controls.

Made for

QA teams that install older builds to find where a bug started
Clients and product owners who want one bookmark for every test build of their app
Teams moving from Codemagic build dashboards or Firebase release lists

What it ends

Searching old emails for the link to build 57
Download links that have stopped working by the time someone needs them
One link per build, and no single place that lists them

How it works

Step 1
Turn it on
On the project's Testing page, turn on the build history page. It is off by default for every project.
Step 2
Share the address
Share the /h/ address, with a page password if you want one. Make a new link at any time; the old one stops working.
Step 3
Testers pick a build
Each row shows the version, date, release notes and channel badges, with an Install button that opens that build's own install page.

No way around a build's own rules

The page adds no way around a build. Each build keeps its own password and access codes, and its release notes stay hidden until it is unlocked. Pause, stop date, install cap, start time, retire and expiry all still apply. A private project on Team still shows its builds to invited testers only.

Turning the page off stops the address. The page itself is not indexed by search engines.

Both platforms, your brand

The page lists the builds of the project and of its paired project on the other platform, so iOS and Android of one version show as one row. It speaks the 13 install page languages, and on Team it can be white labelled and served from your custom domain.

From the CLI

appforshare history on --project <id> turns it on, with --password <text> or --no-password, and --new-link to replace the address. history status prints it, and history off turns it off.

Good to know

It shows the last 20 builds of the app, not every build ever uploaded.
It does not keep a build alive: builds still follow your plan's link rules.
There is no MCP tool for it yet.

Questions

Can someone use the page to skip a build's password?: No. Each build still asks for its own password or access code, and its release notes stay hidden until it is unlocked.
Is it on by default?: No. It is off for every project until someone turns it on.
How is it different from a channel link?: A channel link always opens the newest build of that channel. The build history page lists the last 20 builds so testers can install an older one.
Which plan do I need?: Pro or Team. White label and a custom domain are on Team.