We have an app which creates a custom keychain to store some data. We were using “3rd Party Mac Developer Application” certificate to sign our app.
The cert got expired in March, 2015. We generated a new cert from the same account and signed the updated version on the app. But, now the system prompts for keychain password whenever the updated app tries to read the keychain content created by the older version of the app, even though both the app versions are signed using the certs from the same account.
We are using the following command to sign the app from command line :
codesign --sign "3rd Party Mac Developer Application: ******” --force --keychain <keychain-name> --verbose <appname>
The designated requirement for the app is "identifier "<app bundle id>" and anchor apple generic and certificate leaf[subject.CN] = "3rd Party Mac Developer Application: ****** (*********)" and certificate 1[field.<some numbers>] / exists */
Please suggest some solution to avoid the UI-prompt asking the keychain password.
