iOS setup

Add your iOS app in the dashboardCopy Anchor Link

Open Build > Platforms and fill in the iOS app card:

Save. Lander now serves this file on your link domain:

{
  "applinks": {
    "details": [{ "appIDs": ["ABCDE12345.com.acme.shop"], "components": [{ "/": "/*" }] }]
  }
}

Every path on the domain opens your app. Check it is live:

curl -i https://acme.golander.link/.well-known/apple-app-site-association

You should get 200 with Content-Type: application/json. A 404 means no iOS app is saved for this domain yet. More detail on this card is in Dashboard: Apps.

Add the Associated Domains capabilityCopy Anchor Link

In Xcode, open ios/Runner.xcworkspace, select the Runner target, then Signing & Capabilities. Click + Capability, add Associated Domains, and add an entry with the applinks: prefix and no https://:

applinks:acme.golander.link

Xcode creates (or updates) ios/Runner/Runner.entitlements:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>com.apple.developer.associated-domains</key>
	<array>
		<string>applinks:acme.golander.link</string>
	</array>
</dict>
</plist>

If you also use a custom domain, add one applinks: entry per domain. Lander serves the file on every verified domain of the project.

Turn off Flutter's built in deep linkingCopy Anchor Link

Flutter has its own deep link handler that pushes the URL's path onto your router. With Lander delivering links too, every link would navigate twice. Turn Flutter's off in Info.plist:

<key>FlutterDeepLinkingEnabled</key>
<false/>

Check your app lifecycle (nothing to change)Copy Anchor Link

Both iOS app lifecycles work with no code changes:

• Apps with a FlutterSceneDelegate (the default for new Flutter projects).
• Older apps that only have a FlutterAppDelegate.

The plugin registers for scene and app delegate callbacks and handles Universal Links (NSUserActivity) and URL opens on cold start (scene(_:willConnectTo:options:)) and warm start. Leave your AppDelegate.swift and SceneDelegate.swift as Flutter generated them.

Every callback returns false, so other plugins (sign in redirects, for example) still receive their URLs. Those URLs also reach Lander.onDeepLink, so ignore routes you do not handle.

If you use multiple scenes with a custom root view controller, register your engine with the scene lifecycle as described in Flutter's FlutterSceneLifeCycleEngineRegistration docs.

Add a custom URL scheme (optional, recommended)Copy Anchor Link

A custom scheme such as acmeshop:// is a fallback that always opens the app. It matters most if you use Lander's Continue in app page: iOS keeps a Universal Link tapped on a page of the same domain inside Safari, so that page's "open it" button uses your scheme when you have one.

<key>CFBundleURLTypes</key>
<array>
	<dict>
		<key>CFBundleURLName</key>
		<string>com.acme.shop</string>
		<key>CFBundleURLSchemes</key>
		<array>
			<string>acmeshop</string>
		</array>
	</dict>
</array>

Then enter the same scheme (acmeshop) as the URI scheme of your iOS app in Build > Platforms. Lowercase letters, digits, +, . and - only, starting with a letter.

Custom scheme URLs reach your app without a network call. acmeshop://product/123 routes to /product/123 (the host counts as the first path segment).