capacitor-uiscene-migrator

Run npx cap migrate with @capacitor/cli 8.5 or newer if your project still matches the Capacitor templates. For partial or customized projects, audit the iOS sources first, then merge the scene manifest, SceneDelegate forwarders, and AppDelegate hook without overwriting existing code.

The CLI migrator only handles projects matching the template shape and skips when one or two of the three migration signals already exist: the UIApplicationSceneManifest key, a SceneDelegate.swift file, or the configurationForConnecting hook. Partial states require surgical merges of only the missing pieces.

References to tmpWindow and TmpViewController become build errors since both were removed. Once the scene manifest exists, iOS stops calling application(_:open:), application(_:continue:), and the four foreground/background AppDelegate methods, so custom code there silently stops running.

Yes, if the plugin consumes the legacy capacitorOpenURL notification names, avoids removed APIs like tmpWindow, avoids 8.5-only APIs like SceneDelegateProxy and the .capacitorScene* constants, and keeps lifecycle handling on UIApplication notifications rather than AppDelegate methods.

The SceneDelegate neither creates a window nor lets a storyboard provide one. In Capacitor 8.5 the window is created in code inside scene(_:willConnectTo:) with a CAPBridgeViewController as root, so add that window setup from the template.

Do not use it for Cordova-to-Capacitor plugin migration, generating new Capacitor plugins, Capacitor 9 or later migrations, or Android lifecycle work, since UIScene is iOS-only and this procedure covers only the 8.4 to 8.5 transition.