Ansight.Pairing 0.1.0-preview.19

Ansight.Pairing

Ansight.Pairing adds package-owned native pairing acquisition to Ansight.Core.

It provides:

• native QR scanning for HostConnectionRequest.QrCode(...)
• Android scanner acquisition via the current Activity and native Apple modal presentation
• a default IHostConnectionConfigReader wired into the existing runtime-owned host connection flow

Developer pairing is generated by Ansight.Core. Enable AnsightDeveloperPairingEnabled in the app project, then configure WithBundledHostConnection(...); Ansight.Pairing only adds the native QR acquisition path used by explicit overrides.

The Ansight and Ansight.Maui all-in-one packages include this package where supported.

License

The Ansight SDK is source-available software under the Ansight SDK Source-Available License. It is not open-source software. Production use is licensed only for use with Ansight Services.

Usage

using Ansight;
#if ANDROID
using Microsoft.Maui.ApplicationModel;
#endif

var optionsBuilder = Options.CreateBuilder()
    .WithBundledHostConnection(typeof(AppBootstrap).Assembly);

#if ANDROID
optionsBuilder = optionsBuilder.WithPlatformPairing(() => Platform.CurrentActivity);
#else
optionsBuilder = optionsBuilder.WithPlatformPairing();
#endif

var options = optionsBuilder.Build();

Runtime.InitializeAndActivate(options);

On Android, Ansight.Pairing requires the app to provide the current Activity so the package can launch the native scanner UI.

Once enabled, the app can keep using the existing host connection requests:

await Runtime.HostConnection.ConnectAsync(HostConnectionRequest.Auto());
await Runtime.HostConnection.ConnectAsync(HostConnectionRequest.QrCode());
await Runtime.HostConnection.ConnectAsync(HostConnectionRequest.PayloadText(payload));

Auto() still follows the normal Ansight default order: embedded developer pairing, remembered connection profiles, saved config, then plain bundled config. Remembered profiles are created after successful host sessions, keyed by the Wi-Fi network name reported by the host, and store the latest host/LAN address and discovery metadata for that network. The SDK cycles each valid profile newest-first during automatic reconnect attempts. Profiles expire after 14 days by default, and a successful reconnect refreshes the matching Wi-Fi profile. Explicit QR and payload requests always override the current connection attempt and update the remembered profile after a successful connection.

Configure profile retention through the core options builder:

var options = Options.CreateBuilder()
    .WithHostConnectionProfileRetention(TimeSpan.FromDays(30))
    .Build();