When uploading to the store I get the following error:
*** Error: Errors uploading 'app-builds/mas/superProductivity-5.4.0.pkg': (
"Error Domain=ITunesTransporterErrorDomain Code=-18000 \"ERROR ITMS-90283: \"Invalid Provisioning Profile.
The provisioning profile included in the bundle com.super-productivity.app [com.super-productivity.app.pkg/Payload/superProductivity.app] is invalid. [Missing code-signing certificate.] For more information, visit the macOS Developer Portal.
The other logs look fine to me:
• electron-builder version=22.7.0 os=18.7.0
• loaded configuration file=/Users/johannesmillan/IdeaProjects/super-productivity/build/electron-builder.mas.yaml
• writing effective config file=app-builds/builder-effective-config.yaml
• packaging platform=mas arch=x64 electron=9.0.4 appOutDir=app-builds/mas
• signing file=app-builds/mas/superProductivity.app identityName=Developer ID Application: Johannes (16ADSK323) identityHash=D10278B411682SAAF9EF54D9F8896ASD153D3384 provisioningProfile=none
• signing file=app-builds/mas/superProductivity.app identityName=3rd Party Mac Developer Application: Johannes (16ADSK323) identityHash=B55EC8C3FB70ASDCDA32FD80490F485D2D509A71E provisioningProfile=embedded.provisionprofile
✨ Done in 49.84s.
I am pretty sure that the certificates and embedded profiles are correctly configured. I tried the process with several fresh combos of certificate and profile. Any clues what might be causing this?
The config can be found here:
https://github.com/johannesjo/super-productivity/blob/master/build/electron-builder.mas.yaml
@johannesjo any luck with this?
@msavin unfortunately not... I've been trying to make mac store builds work for almost 2 years now and I sunk many many hours into it. There is always something not working.
I’m going crazy... every minute that Electron saves you, you have to pay back in dealing with Electron Builder
Sent from my iPhone
On Jul 26, 2020, at 5:42 PM, Johannes Millan notifications@github.com wrote:

@msavin unfortunately not...—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
This is still relevant. Just tested it again with Catalina and a fresh provisioning profile. Same error. I also tried using the transporter app instead of altool. Makes no difference.
Can confirm after upgrading my device to macOS 10.15.6
Sent from my iPhone
On Sep 27, 2020, at 11:12 PM, Johannes Millan notifications@github.com wrote:

This is still relevant. Just tested it again. Same error.—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
Same issue. The 2-nd day trying to solve it.
Maybe you can upvote the original issue (thumbs up). This makes it easier to see for the devs that multiple people are affected.
@msavin unfortunately not... I've been trying to make mac store builds work for almost 2 years now and I sunk many many hours into it. There is always something not working.
Have you tried this manual building:
Mac App Store Submission Guide
I am not sure if it worth wasting time?
Haven't tested it fully yet, but apparently app-builds/mas/superProductivity.app/Contents/embedded.provisionprofile contained the wrong provisioningprofile. I had multiple of those at the root of my project (e.g. x.provisioninprofile) which I copied to embedded.provisioningprofile before the build as needed. Not 100% sure yet, but this might be worth investigating.
Ok, I'll try tomorrow with really simple app.
I had success with it! Which is truley amazing after 2 years of trying to get this dam thing deployed to the mac store. Let's see what the next obstacle will be :)
@johannesjo OMG, I guess it would be great if you will publish your success story on Medium or personal blog.😎
Where should I dig to make it finally work?
At least for me the issue was caused by the comment above. You find all related code and configuration here: https://github.com/johannesjo/super-productivity
At least for me the issue was caused by the comment above. You find all related code and configuration here: https://github.com/johannesjo/super-productivity
@johannesjo i am also struggling from last few months to submit mas build to Apple store. I have tried lot of methods to sign the build, after sign the app crash on launch there are no any error in log. Once i set sandbox to false then app is not crashing. But transporter reject to upload because of sandbox is not set true. Do you have any experience with this issue?
Documents/projects/todo-xplat/dist-app/mas/Todo\ Cloud.app/Contents/MacOS/Todo\ Cloud ; exit;
zsh: killed
[Process completed]
https://github.com/electron-userland/electron-builder/issues/5011
Looking forward for your help. Thanks
@ahmadwaliesipick I'd recommend checking out the source code but I've to admit that I am not sure if the mas store version crashes or not because I don't have another device to test and the review is not yet done.
@ahmadwaliesipick I'd recommend checking out the source code but I've to admit that I am not sure if the mas store version crashes or not because I don't have another device to test and the review is not yet done.
@johannesjo Thanks for quick reply.
I have seen your source code and i am doing same. The package.json and plist info are same. Once i create dmg without sandbox true then app is build is not crashing. I have tried my app build in another mac but still it is crashing.
I have also enabled debug mode of electron-builder and there are no any error in logs. The build is properly signing with provided provision profile and certificates.
@johannesjo how did you verify working of signed pkg?
@ahmadwaliesipick I didn't. I try to check this tomorrow.
@johannesjo I am able to resolved the build sign issues and uploaded build to Apple Store. Soon app will be available at apple store. :-)
Most helpful comment
@johannesjo I am able to resolved the build sign issues and uploaded build to Apple Store. Soon app will be available at apple store. :-)