My overall goal is to release a new version ( v1.1.5 ) of my electron app on the mac apple store.
I've been able to release multiple version in the past couple years, currently my app is sitting at v1.1.4 in the mac apple store.
Usually when I try to package, sign, and release a new mac / mas build, there's some difficulty with making sure all the entitlements and provision profiles are up to date and correct, like what I'm experiencing now.
And with coming back to release a new version after long periods of time It's always a little rusty on figuring out how to correctly setup my keys/profiles/certs so that a mas build can get signed and uploaded through transporter successfully.
So maybe xcode isn't needed at all in my case, and I shouldn't be trying to generate a provisioning profile on that page like in my last screenshot. I just know I've gotten through this process before successfully and a trying to do it again, while taking better notes, so I can release more upcomming versions faster and without troubleshooting like this.
Even after some more attempts I'm still facing the transporter error
Asset validation failed (90284)
Invalid Code Signing. The executable must be signed with the certificate that is contained in the provisioning profile
Does this mean that maybe my file embedded.provisionprofile contains the wrong certificate? I did just generate a new MAS Developer Cert, but have been struggling trying to move past this issue.
Topic:
Code Signing
SubTopic:
Certificates, Identifiers & Profiles
Tags: