Hello, My team would like to ask you about a specific situation concerning the identifierForVendor that we have been using on our application deployed on the store since July 2018. It is critical for us that the identifierForVendor does not change because it is used during the initialization of the new version to take over the data from the old version. We therefore need to know precisely the different cases where it changes during a version update knowing that the certificate and the provisioning profiles used for the old version have expired and that in the new one we always use the same Apple developer account , same Application associated with this account and same bundle ID. What are your recommendations to put in place to ensure that the identifierForVendor does not change before going into production. Cordially, mohamed bennis
identifierForVendor changes
Hello @mbennis94.
Please see identifierForVendor, which describes what this value is, and when the value may change.
—Jason.
It is critical for us that the
identifierForVendordoes not change because …
This is a concern. Jason pointed you to the docs that describe when this supposed to change but that list of situations could well change in the future, either as a matter of policy or due to a bug. I encourage you to avoid building systems where a change to identifierForVendor could result in a loss of user data.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
So the only way to know if it works or not is to do the update in store ?
The best way to test how your product will behave when deployed via the App Store is TestFlight.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
and wich type of certificate and provisionning profile should i use for my new version deployed in TestFlight ?
TestFlight is an additional, and optional, step in App Store distribution. You upload your app to the App Store Connect and then can choose to make it available in TestFlight. Given that, it uses the same code signing credentials as App Store distribution.
To learn more, see our Developer > TestFlight page.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"
Hello when you say i need the same code signing credentials as App Store distribution you mean create a new certificate with the same type = App Store distribution or i need to download the one used for my old version and use it for the new one ?
or i need to download the one used for my old version and use it for the new one ?
Not this.
App Store re-signs your app as part of its distribution process. That means that the credentials you use to sign your app when you upload it are only relevant during the upload and ingest process. So, it doesn’t matter which code signing identity you used to sign previous versions of your app. What matters is that the the one that you’re currently using is valid.
Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"