---
name: ansight-migrate-to-sdk-1-1
description: Migrate an app from Ansight SDK 1.0.x or an older pairing-config integration to the current SDK and CLI-hosted enrollment model. Use when upgrading native Android, native iOS, .NET or MAUI, React Native or Expo, Flutter, or Capacitor apps and removing bundled connection configuration.
---

# Migrate to Ansight SDK 1.1

Move an existing integration to the SDK 1.1 enrollment model without retaining
legacy pairing-config compatibility.

## Select the framework guide

Read and follow exactly one primary guide:

| App framework | Migration skill |
| --- | --- |
| Native Android | `https://www.ansight.ai/skills/android/ansight-migrate-sdk-1-1-android/SKILL.md` |
| Native iOS | `https://www.ansight.ai/skills/ios/ansight-migrate-sdk-1-1-ios/SKILL.md` |
| .NET / MAUI | `https://www.ansight.ai/skills/dotnet/ansight-migrate-sdk-1-1-dotnet/SKILL.md` |
| React Native / Expo development build | `https://www.ansight.ai/skills/react-native/ansight-migrate-sdk-1-1-react-native/SKILL.md` |
| Flutter | `https://www.ansight.ai/skills/flutter/ansight-migrate-sdk-1-1-flutter/SKILL.md` |
| Capacitor | `https://www.ansight.ai/skills/cordova/ansight-migrate-sdk-1-1-capacitor/SKILL.md` |

For a mixed app, use the wrapper guide as primary and consult its native
Android or iOS guide only for platform project details.

## Shared migration contract

1. Upgrade every Ansight package consumed by the app to
   `1.3.0-preview.10`. Do not mix wrapper and native package versions.
2. Remove generated or bundled pairing JSON, pairing-config files, host IPs,
   machine names, Wi-Fi names, signing material, certificate settings, and
   build-time desktop-host probing.
3. Remove code that loads or passes legacy pairing configuration. Do not keep
   a compatibility fallback.
4. Initialize the SDK once from the app's normal local-development startup.
5. Let simulators and emulators enroll automatically with a running CLI host
   on the same development machine.
6. For a physical device, expose the SDK scanner from a developer-only surface.
   Run `ansight pairing issue --qr` and scan the one-use terminal QR. The SDK
   supplies its real App ID; no prior app registration is required.
7. Keep the SDK and privileged remote tools out of distributable builds unless
   their inclusion is an explicit product decision.
8. Add only platform permissions required by the chosen scanner and local
   network path.
9. Build the affected targets, launch them with `ansight host run` active, and
   verify `ansight session list --connected --app-id <app-id> --json` plus
   automatic reconnect on the next launch.

## Removal check

Search the app and build configuration for obsolete concepts:

```text
pairing-config
pairingConfigJson
bundledDeveloperConfigJson
ANSIGHT_PAIRING_CONFIG
ANSIGHT_HOST
ANSIGHT_WIFI
wss://
```

Review each match. Remove enrollment configuration and build plumbing; retain
only unrelated historical documentation or explicit network-policy code.

## Done criteria

- all Ansight dependencies resolve to `1.3.0-preview.10`;
- no pairing payload, host address, Wi-Fi identity, certificate, or desktop-host
  probe is embedded in the app;
- local simulator or emulator startup connects without manual configuration;
- a physical device can scan the CLI's terminal QR once and reconnect later;
- no app is manually registered before enrollment; and
- release builds do not gain unrelated permissions or privileged tools.