Yes that is correct DTS Engineer. Have you any ideas? :D.

Hi DTS Engineer, We've been relying and using the vendor id in an Enterprise environment for about 10 years now without issue :(. For a test I have done as you suggested. I installed the app1 .ipa that was built a while back on a newly wiped device and also installed app2 .ipa that was built recently. The vendor id's don't match even though the bundle name is on the same dns of com.companyname.xxxx. Its almost like something else is affecting it... Is there anything else within your knowledge that can also affect Vendor ID's matching? Certificates or signing or anything?

I normally use automatic code signing so my understanding of some of the elements in the code signing process is limited, but looking in the mobileprovision the only differences I can see from App1 and App2 are: They have a different DER-Encoded-Profile App2 has an array of provisionedDevices where as App1 has the following key: ProvisionsAllDevices Looking at an older version of App2's mobileprovision it also doesn't have a set list of provisioned devices. I don't know how this automatically would have changed though or if it affects the vendor id or how to change it back. I don't suppose you are available for hire or if you can recommend anyone official to assist in this matter via screen share?

Hi DTS Engineer, Thank you for taking the time to reply and for providing that information. For the signing process, I have always ticked "Automatically manage signing". I then select the "Team" and manually type the "Bundle Identifier". I tried rebuilding app1 and app2 and the vendor ids are in sync. The problem is we have about 1200 devices and they all have app1 installed which is basically an app that logs the vendor id and registers a device. The other 5 or 6 apps we have including app2 then use the same shared vendor id. If possible we need a way so new builds still produce the same vendor id as app1. We haven't confirmed it yet, but someone has stated that it doesn't seem to have affected iPad 8th Gens. (We are still in the process of confirming this). I also noticed that just now I received a Command Line Tools 16.4 update (not sure if this could have been some sort of hot fix) but in my XCode settings - Version 16.3 (16E140) the command line tools is still set to 16.3... it doesn't give me an option to select 16.4. I tried a new build of app2 anyway just to see if the update had fixed it but its still the same.

Hi DTS Engineer, I tried a few more tests and can also confirm that 8th gen iPads are not immune to the issue. If I create new versions of App1 and App2 the vendor Id's are in sync when they are installed on a fresh device. I also tried: On an affected device, (with old app1 and new app2 builds) I tried updating app1 with a new app1 but the vendor ids are still different. What do you make of all this?