Does the tester need an account?

No. The UDID finder and the device check work without one, on every plan.

What does AppForShare store?

Nothing new. The device lives in a signed cookie in the tester's browser. UDID finder lookups are deleted after 1 day as before; a device sent to the developer is kept like an onboarding link request.

Which languages does it show in?

The same 7 languages as the install page: English, Hindi, Urdu, Bengali, Indonesian, Spanish and Arabic.

How is this different from Diawi's warning?

Diawi warns a device identified in its web app. Here the tester checks the iPhone once with the UDID finder, and when the device is missing they can send it to the developer from the same page, who gets it in their devices list.

AppForShare Create a free account

Testers know if their iPhone is in the build before they tap Install

Every plan. Sending the iPhone from the page needs the project's device onboarding link (Pro and Team)

An ad hoc build only installs on iPhones whose UDID is in its profile. When the tester's phone is missing, iOS starts the install and then fails with "Unable to install" or "integrity could not be verified", and the tester has no idea why.

With Remember my iPhone the tester finds out first. They run the free UDID finder once and tap Remember this device. From then on, each iOS install page on appforshare.io says "Your iPhone is in this build" or "not in this build yet" above the Install button.

Start free See plans

Example

Shop app 2.5 (121)

Sara's iPhone 15Not in this build yet
Send my iPhoneSent to the developer
Next build with itWe email you
Not your iPhone?Forget it

The device is kept in the tester's browser only.

Made for

Testers who get ad hoc builds from several developers or projects
Developers tired of "it says unable to install" messages
Agencies whose clients add a new iPhone halfway through a project

What it ends

A tester taps Install, waits, and gets an error with no reason
Asking a tester for their UDID again for every new project
Guessing whether a failed install is the device, the profile or the phone settings

How it works

Step 1
Check the iPhone once
On the iPhone, the tester opens the UDID finder from an install page or at /udid and installs the small profile. The result page shows the UDID and a Remember this device button.
Step 2
Open any iOS install link
The page reads the remembered device and says whether the build's profile includes it, before the Install button. Enterprise builds install on any device.
Step 3
Not in the build? Send it
When the project's device onboarding link is on, the tester sends the iPhone to the developer from the page with an email. Otherwise they copy the UDID and send it themselves.

Kept in the tester's browser, not on our servers

Remember this device keeps a signed cookie in the tester's own browser for up to 400 days. The signature only proves the UDID came from a real profile answer. Nothing new is stored on our side, and every install page has a "Not your iPhone? Forget it" link that removes the cookie.

The check runs after the link password and, on private projects, after tester access, so a remembered device never opens a page the tester could not open anyway.

Sending the iPhone to the developer

When the project's device onboarding link is on (Pro and Team), the not in this build message has a Send my iPhone form. It works like the onboarding link: the device goes into the developer's devices, the developer gets an email, and the tester gets one email when a build that includes the iPhone is uploaded. With Hands free on (Team), the device is registered on Apple and the build starts on its own.

Without the onboarding link, the page offers Copy my UDID so the tester can send it in a chat or email.

Good to know

iOS install pages on appforshare.io only, not on custom domains.
The cookie lives in one browser. A tester who uses another browser or clears cookies checks the iPhone again.
It tells whether the UDID is in the profile. It cannot fix a profile: the developer adds the device and builds again.

Questions

Does the tester need an account?: No. The UDID finder and the device check work without one, on every plan.
What does AppForShare store?: Nothing new. The device lives in a signed cookie in the tester's browser. UDID finder lookups are deleted after 1 day as before; a device sent to the developer is kept like an onboarding link request.
Which languages does it show in?: The same 7 languages as the install page: English, Hindi, Urdu, Bengali, Indonesian, Spanish and Arabic.
How is this different from Diawi's warning?: Diawi warns a device identified in its web app. Here the tester checks the iPhone once with the UDID finder, and when the device is missing they can send it to the developer from the same page, who gets it in their devices list.