Installing Signum on iPhone: App Store, TestFlight and Xcode Sideload

Getting an app onto an iPhone is usually a two-tap affair — until it isn't. I went through the Signum install paths recently and the interesting part wasn't the download, it was proving that what landed on the phone is actually the build I expected. Below is the order I'd do it in, with the checks that saved me from a dead-end install.

Budget roughly 15 minutes for the App Store or TestFlight route, and around 35 minutes if you sideload a build through Xcode. The first is basic; the second is intermediate and assumes a Mac.

One honesty note up front: the sources I worked from do not state Signum's App Store listing, bundle identifier, minimum iOS version, download size, build number, or price. I'm not going to guess any of those. Treat every one of them as "read the vendor documentation" before you tap Install.

What you need before you tap anything

• An iPhone or iPad with headroom. Check Settings → General → iPhone Storage. The App Store lists the download size in the same spot it does for any app — for reference, the Microsoft Windows App Mobile listing shows 208.3 MB, which is where that number lives.
• An Apple ID signed in at Settings → [your name] → Media & Purchases with two-factor authentication enabled. Without 2FA, TestFlight invitations and App Store purchases simply fail.
• Wi-Fi for the first download. Cellular can work, but carriers sometimes block large builds.
• Sideload path only: macOS with Xcode, a free Apple ID for signing, and the Signum source archive or .ipa.

My prep checklist before starting:

• [ ] iOS version recorded (Settings → General → About)
• [ ] Free storage greater than the listed app size plus 1 GB
• [ ] Apple ID signed in and 2FA active
• [ ] Official distribution channel confirmed — App Store, TestFlight, or source
• [ ] Developer name in the listing matches the vendor documentation

On a fresh iPhone the About screen shows entries like "iOS Version 18.x", "Model Name iPhone", "Capacity 128 GB". Write down that iOS Version line — it decides whether the build will install at all.

Step 1: Confirm the channel and your device baseline

Open Settings → General → About and note the iOS version. Then open the App Store, search for Signum, and read three fields on the listing: Developer, size, and the "Requires iOS" line. If the vendor documentation points at TestFlight instead, use the invitation link they provide and skip the search entirely.

Why bother? Almost every "it won't install" case I've seen comes down to one of three things: the build's minimum iOS version, the App Store region tied to the Apple ID, or the publisher identity. Reading three fields takes a minute and removes the guesswork.

For comparison, a legitimate Microsoft listing shows "Microsoft Corporation" as the developer and "4+" as the age rating. If the Signum listing shows an unrelated publisher, stop and re-read the vendor docs. Scroll to Information and check "Seller" and "Size" — if the Seller field is empty or shows a personal name, you're on the wrong listing.

Step 2: Install using the channel that matches the docs

App Store. Tap Get → Install → confirm with Face ID or your Apple ID password. The icon appears on the Home Screen and fills a progress ring.

TestFlight. Install TestFlight from the App Store, open the vendor's invitation link, tap Accept, then Install. TestFlight shows builds in version (build) form — for example, a public build of Cortiq Mobile was labelled 1.3.0 (47).

Xcode sideload. With the Signum project or .app bundle on the Mac, run these checks first:

xcodebuild -version
security find-identity -v -p codesigning
plutil -p ./Signum.app/Info.plist | grep -E 'MinimumOSVersion|CFBundleIdentifier|CFBundleShortVersionString'

You should get an Xcode version line, at least one valid signing identity, and three plist keys printed with their values. Then open the project in Xcode, pick your personal team under Signing & Capabilities, set a unique bundle identifier (something like com.<yourname>.signum), connect the iPhone by cable, select it as the run destination and press Run. Finish by trusting the certificate: Settings → General → VPN & Device Management → Developer App → Trust.

The reason for the extra ceremony is that iOS only launches an app whose signature matches a certificate the device trusts. App Store and TestFlight hand you a pre-signed build; Xcode signs it locally, which is why the bundle identifier has to be unique and the certificate has to be trusted by hand.

Before pressing Run, confirm the phone is actually visible to the toolchain:

xcrun devicectl list devices

Expect a table with your iPhone's name, its identifier (UDID), and a connected state. If the list is empty, suspect the cable, the "Trust This Computer" prompt, or Developer Mode (Settings → Privacy & Security → Developer Mode).

Step 3: Verify the install and the first launch

A finished download is not a working app. Tap the Signum icon once, let it reach its first screen, close it, then check three things: the version number, the storage footprint, and the running process.

1. Settings → General → iPhone Storage → Signum. That entry shows an app size and a version number.
2. If it came through TestFlight, the TestFlight app lists the installed build (e.g. 1.3.0 (47)) next to an expiry date.
3. Stream the device log from the Mac while the app starts:

log stream --predicate 'process == "Signum"' --level info

You want a stream of lines containing the process name and no crash or Code Signature Invalid entries. Ctrl+C stops it.

Success looks like this: the icon launches with no dialog, the version in step 1 matches the vendor documentation, and the log shows the process starting. That last check is the one that catches an untrusted signature or an expired beta — problems that a clean download never reveals.

Troubleshooting the usual failures

Cannot Connect to App Store. Usually a drifted device clock or a stale App Store session after switching networks. Fix: Settings → General → Date & Time → enable Set Automatically, then Settings → [your name] → Media & Purchases → Sign Out, sign back in, and retry the search.

This app is not available in your region. The Install button is missing or greyed out because the App Store region attached to your Apple ID doesn't match the storefront carrying the app. Fix: Settings → [your name] → Media & Purchases → View Account → Country/Region. Switching region needs a matching payment method, so on a fresh account add one first, switch, then reopen the listing.

Signing for "Signum" requires a development team. The Xcode build stops before it ever reaches the phone. Fix: open Signing & Capabilities in the project and select a development team, then run again.

This article was originally published on AI Release — https://ai-release.org. If you'd rather follow along in a feed, the channel is at https://t.me/ai_release1.

Takeaway

The install itself is the easy half. What actually protects you is the minute you spend reading the Developer and "Requires iOS" fields, and the thirty seconds you spend streaming the log on first launch. And where the sources are silent — listing, bundle ID, minimum iOS version, size, build number, price — the vendor's own page is the only answer worth trusting.