Which plan do I need?

None. The notes and the help list are on every install page, also for builds uploaded without an account.

Can my AI assistant tell me why a tester cannot install?

Yes, on Pro and Team through the MCP server: build_install_issues lists the issues for a build, and with the tester's UDID it says whether the device is in the profile.

Does it fix the build?

No. It says what is wrong. Fixes such as a new profile or a lower minimum iOS need a new build from you.

AppForShare Create a free account

Install pages that say why a build will not install

Every plan

Most failed installs from a link have one of a handful of causes: the wrong browser, an iOS version older than the build needs, an expired profile, a build signed for the App Store, Developer Mode turned off, an Android setting. Testers do not know which, so they write to the developer.

AppForShare reads what it already knows about the build and the phone that opened the page, and says it in the tester's language before they tap Install.

Start free See plans

Example

Install help

This phoneiOS 16.7, build needs iOS 17.0
Developer ModeTurn on, then restart
BrowserOpen in Safari
Unable to install?Check your iPhone first

Shown in the tester's language.

Made for

Testers who are not developers: clients, managers, friends
Developers who answer the same install questions every week
Teams that send iPad only, enterprise or development builds

What it ends

A tester on iOS 16 trying to install a build that needs iOS 17
"Unable to install" with no reason given
An app that installs but will not open until Developer Mode is on

How it works

Step 1
Blocking notes above Install
When the build cannot work on this phone the page says so: iOS too old for the build, an iPad only build on an iPhone, the profile has ended, signed for the App Store, not signed, or Android too old.
Step 2
Install help per platform
On iPhone: open the page in Safari, watch the home screen, Developer Mode for ad hoc and development builds on iOS 16 and later, enterprise trust, and what "integrity could not be verified" means. On Android: allow unknown apps, Play Protect, "App not installed" from a signature conflict, and storage.
Step 3
Owners see it too
appforshare info prints the install issues of a build, the CI API returns them as installIssues, and the MCP tool build_install_issues answers "why can't my tester install", with an optional UDID check.

Facts from the build and the phone

The notes come from what AppForShare reads at upload (signing type, profile end date, minimum iOS or Android version, iPhone or iPad) and from what the tester's browser reports (iOS or Android version, iPhone or iPad). Nothing is added to the app.

For owners there are a few more checks: a profile that ends within 14 days, a profile with no devices, a debuggable APK, and an APK made from an .aab with the test key, which needs the Play Store version uninstalled first.

Good to know

It cannot see inside the phone. Developer Mode, trust and Android settings are shown as steps to check, not as detected problems.
Whether the iPhone is in the profile needs the device check (Remember my iPhone) or a UDID.
App name and release notes are not translated; the help text is, in 13 languages.

Questions

Which plan do I need?: None. The notes and the help list are on every install page, also for builds uploaded without an account.
Can my AI assistant tell me why a tester cannot install?: Yes, on Pro and Team through the MCP server: build_install_issues lists the issues for a build, and with the tester's UDID it says whether the device is in the profile.
Does it fix the build?: No. It says what is wrong. Fixes such as a new profile or a lower minimum iOS need a new build from you.