Invalid APNs certificate

Hi,
I am in a situation where I am not able to find a solution and I would appreciate a lot if someone could help.

The APNs certificate of an app of ours is about to expire and, in the same way I have done in the past years (I am not new to this), I have created a new APNs certificate from developer.apple.com by executing the usual steps as everyone should be familiar with.

Unfortunately the generated certificate is said to be BadCertificate when for example using openssl as per these steps.

The puzzling part is that when I execute the exact same steps for another app of the same team the generated APNs certificate is valid.
Other team members have tried to generate an APNs certificate for the same culprit app and the result has been always an invalid certificate.

One thing we have noticed is that, when checking the Info of the generated certificate in Keychain access, it can be seen duplicated information in the extension section. So the following data is mentioned twice:
  • appbundleid

  • appbundleid.voip

  • appbundleid.complication

I have contacted also the developer technical support but I haven't received any help by far.

Few months ago we changed the company name, but I don't think that could be an issue and anyway I don't know how differently the APNs cert generation could be

Does anyone have any hints or help to give?
Thanks.
Accepted Answer
At the end I found out that the generated APNs certificate is invalid when Mac Catalyst is enabled for the app.
Completely frustrated by the fact that the APNs cert was invalid, I have tried to disable the Push Notifications for the app and that could not be done because the Mac Catalyst was enabled.

I then disabled the Mac Catalyst and tried to generate again a new APNs certificate with the result of getting a valid certificate.

Then there may be something broken on Apple side when generating an APNs certificate with the Mac Catalyst enabled.
Invalid APNs certificate
 
 
Q