Reset to default
Trending sort is based off of the default sorting method — by highest score — but it boosts votes that have happened recently, helping to surface more up-to-date answers.
It falls back to sorting by highest score if no posts are trending.
I got two options for you:
1) open KeyChain and find the signing certificate that shown in the error message then delete it.
2) you specified the signing certificate in the Build Setting->Signing, so go to the Build Setting->Signing and click the Code Signing Identity. Do not select Automatic (iOS Developer or iOS Distribution), select the one of the signing certificates in the Identities in Keychain which is valid and have associated with the Provisioning Profile.
I temporary solved the issue by going into Build Settings, and manually set Code Signing Identity (the old way). “Automatically manage signing” no longer work properly, but at least it work.
“Automatically manage signing” is not working on Xcode 9.3. Code signing identify should be selected manually in Build Settings.
It is right.
You can select Code Signing Identity as iOS developer for development and iOS distribution for production in Signing of build settings.
“Automatically manage signing” is not working on Xcode 9.3.
Code signing identify should be selected manually in Build Settings.
In my case, the Provisioning Profile on developer.apple.com listed two developer certificates. One was selected, and one was not. Changed it so both were selected, saved that, installed the updated profile and that fixed it.
I had to juggle a bit more too. I deleted my keychain, enabled and disabled autosigning before recreating my certificates.
Then I toggled the certificates in Build Settings section and finally I was able to select the correct certificates in general section.
Really missing the simplicity of signing for Android.. 😛
In my case, I changed the Provisioning Profile to solve the problem by changing the Certificate whose type is “iOS Distribution” to another Certificate whose type is “(Distribution) For use in Xcode 11 or later”, then download it and import it to keyChain, select it form Xcode.
In my case I had multiple profiles and various certs. I had to go to Apple developer and edit the profile from the error, and add every cert to it, and then it worked.
If you have this certificate on another machine, you can export it from keychain and import on the other.
My problem was that I didn’t know how to match private keys with certificates because I used “all items” filter in KeyChain.
If you switch to
Certificates private keys are arranged under certificates, so you can easily export the right pair.