Handle iOS app launch failures after install

[mdub1na]

Summary

• Parse the bundle id from idb install output before launching an iOS app
• Avoid unhandled promise rejections when the best-effort launch fails
• Send integer install progress values

Problem

After an iOS IPA was installed successfully, the install plugin attempted to auto-launch the app. The bundle id was parsed with a broad regular expression that could match the status word from idb install output instead of the actual bundle id.

For example, with install output like:

Installed: com.testing.app A13F6EBD-88D6-3254-8678-B5B61FD31120

the old parser could try to launch Installed instead of com.testing.app, leading to an error like:

Unhandled rejection Error: Command failed: idb launch Installed --udid=00008110-001454941A46801E

The same flow also sent fractional progress values, producing noisy warnings such as:

Somebody is sending non integer as progress: installing_app

Fix

Parse the bundle id explicitly from Installed: <bundleId> / Installed <bundleId> output, skip the launch if the bundle id cannot be detected, and catch launch failures so a failed post-install launch does not become an unhandled rejection. Progress updates are rounded before being sent.

Testing

• npm run build