The browser-safari target accepts runtime bundleId values without validating that they are usable reverse-DNS identifiers. Invalid values can be written into dry-run package plans, archive paths, App Store Connect lookup URLs, and dry-run ship metadata instead of failing early. The target should normalize and validate the bundleId before build or ship.
The browser-safari target accepts runtime bundleId values without validating that they are usable reverse-DNS identifiers. Invalid values can be written into dry-run package plans, archive paths, App Store Connect lookup URLs, and dry-run ship metadata instead of failing early. The target should normalize and validate the bundleId before build or ship.