[iOS16] The value of bundle-identifier key can no longer be used as *.

Question

DominicKim OP

Created Sep ’22

Replies 3

Boosts 0

Views 1.4k

Participants 3

Hi team.

I've always used the manifest download link to install my test app like

itms-services://?action=download-manifest&url=https://host.sample/sampleManifest.plist

However, at the iOS 16, it was found that installation errors occurred when the value of the bundle-identifier of the manifest was set to * like

<key>metadata</key>
<dict>
  <key>bundle-identifier</key>
  <string>*</string>
</dict>

and install error logs are : item being installed did not contain an app with bundle ID “*”, but it did contain app(s) with bundle ID ${real bundle id}

I wonder if there is a way to use it instead of real app bundle id like '*'.

thanks.

Answered by Device Management Engineer in 728817022

The bundle-identifier key must be present and accurate in the enterprise app manifest.

https://developer.apple.com/documentation/devicemanagement/manifesturl/itemsitem/metadata

If your scenario makes specifying an accurate bundle-identifier difficult, please describe your use case in detail in Feedback Assistant.

Boost

Answer 1

Device Management Engineer OP

Apple

Sep ’22

Accepted Answer

The bundle-identifier key must be present and accurate in the enterprise app manifest.

https://developer.apple.com/documentation/devicemanagement/manifesturl/itemsitem/metadata

If your scenario makes specifying an accurate bundle-identifier difficult, please describe your use case in detail in Feedback Assistant.

0

Answer 2

DominicKim OP

Sep ’22

What I was curious about was that the '*' that was available up to iOS 15 became unavailable on iOS 16, but it was a good answer.

I think I was using it the wrong way. I eventually modified my scenario, and now it works well. Thank you.

0

Answer 3

Martin@PACE OP

Sep ’22

Just to add to this, because I ran into this problem as well: I think the bundle-identifier property was not verified at all prior to iOS 16. We defined an identifier that was completely different and installation still worked. Good to know that with iOS 16 it has to be exact though.

0