Provisioning doesn't do case-insensitive match

According to the thread at https://developer.apple.com/forums/thread/787500?answerId=863361022#863361022, we should now be able to set VMs provisioning identifiers to run developer builds. However, the identifier check seems to be case-sensitive.

I have an identifier from an old VM that was input (automatically via Xcode) to the portal as all-caps. However, now it's showing up as all lower-case (on the device). When I try to launch my application, the system logs report that the provisioning identifer doesn't match, so my application will not launch:

# Error log
error	13:41:36.173151-0600	taskgated-helper	embedded provisioning profile not valid: file:///Applications/my-app.app/Contents/embedded.provisionprofile error: Error Domain=CPProfileManager Code=-212 "Provisioning profile does not allow this device." UserInfo={NSLocalizedDescription=Provisioning profile does not allow this device.}

# Device's identifier
$ system_profiler SPHardwareDataType
Hardware:
      ...
      Provisioning UDID: 9d136dc4ae3ce80124756cc5bcb40cd1117c04b6

# Embedded provision (from developer portal)
$ security cms -D -i /Applications/my-app.app/Contents/embedded.provisionprofile 
	<key>ProvisionedDevices</key>
	<array>
		<string>9D136DC4AE3CE80124756CC5BCB40CD1117C04B6</string>
	</array>

I have tried disabling the previous record and adding it again (with lower-case) on the developer portal - but all that does is reenable the previous (all-caps) record.

Either the check needs to be case-insensitive, or there needs to be a way to change the registration on the developer portal to properly match.

Answered by DTS Engineer in 863737022

You post reads like a bug report, and it would be perfectly reasonable for you to file a bug requesting either of these changes. If you do, please post any bug numbers, just for the record.

In terms of workaround, the simplest option would be to create a new VM. That’ll get a new provisioning UDID, which will be registered with the correct case.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

You post reads like a bug report, and it would be perfectly reasonable for you to file a bug requesting either of these changes. If you do, please post any bug numbers, just for the record.

In terms of workaround, the simplest option would be to create a new VM. That’ll get a new provisioning UDID, which will be registered with the correct case.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Provisioning doesn't do case-insensitive match
 
 
Q