I'm frustrated with the code signing support to publish app on macOS store

I'll keep it short
  1. My app got rejected

  2. Reason was app crash, on checking error code it looks like code signing issue

  3. I had done the best by following the code signing documentation, testing it locally and using transporter to verify the package

  4. Now I'm not sure if this is a bug in OS or code signing or something is missing in the documentation.

I have raised request to support. They shared documentation link with me again. I raised code-level support, no response.

Should I give up to publish on macOS store or there is any hope?

I raised code-level support, no response.

Code-level support is provided by my group, DTS, and we should always respond within three business days (you can learn more about this and other DTS policies by reading our page on the developer web site). If it’s been longer than that, please drop me a line via email (my address is in my signature). Make sure to reference this thread. I get a lot of email!

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"

I had done the best by following the code signing documentation, testing it locally and using transporter to verify the package

Can you clarify what you mean by "testing it locally"? I assume you are just running the app on your development machine. You should be testing in a pristine, "factory fresh" environment such as a virtual machine or, even better, a dedicated test device. These test environment must always be using the latest shipping version of macOS as that is what App Review is going to run.

And what is this "transporter" that you are talking about?

Just kidding! 😀 You are using some cross-platform app builder instead of Xcode, right? Well, you have to ask yourself. How much time and effort are you really saving?

To be honest, you don't need code-level support for this. Just build your app in Xcode and pretty much everything is done for you. Yes, I know! You are too far along to rewrite everything now. No money is worth more than money than you have already spent.

I suggest you contact whatever support resources exist for your 3rd party app-building tool. It will probably be another free forum environment like this one. But those people, unlike anyone here, will 1) know what tool you are using and 2) be familiar enough with it to offer you advice.



OP here. More information on the issue:
  • The app I'm building is an electron app.

  • I'm signing the app content using the command line tools. And then I'm packaging it as .pkg.

  • Transporter is apple's recommended app to upload app packages to MacOS App Store. It is supposed to find issues with package early on before submitting it to macOS App Store. All checks were passed.

  • I don't see how Xcode can be used(the app is written in javascript using electron, not in swift or objective C)

  • I have tried different permutation combination of signing with Apple ID, using provision profile, changing .plist file, etc.

The app I'm building is an electron app.

You don't say.

I'm signing the app content using the command line tools. And then I'm packaging it as .pkg.

Fair enough

Transporter is apple's recommended app to upload app packages to MacOS App Store. It is supposed to find issues with package early on before submitting it to macOS App Store. All checks were passed.

Apple recommends using Xcode. They provide Transporter for people who want to make life more difficult for themselves, but I wouldn't call that a recommendation.

I don't see how Xcode can be used(the app is written in javascript using electron, not in swift or objective C)

Maybe do some additional research on your Electron platform.

I have tried different permutation combination of signing with Apple ID, using provision profile, changing .plist file, etc.

You mean, random trial and error? That is not a recipe for success.

What has Electron support told you about this issue?


DTS … should always respond within three business days

Just to close the loop here, I chatted with invider offline and it seems that DTS didn’t respond because we never received their tech support incident request. Weird.

For those of you following along at home:
  • When you submit a DTS tech support incident you should receive an auto ACK email with a follow-up number almost immediately. If you don’t receive that auto ACK within a day, something has gone wrong with your submission..

  • DTS aims to respond within three business days. If you have an open incident and haven’t heard from us in week, it’s fine to send a ping.

Share and Enjoy

Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@apple.com"
I'm frustrated with the code signing support to publish app on macOS store
 
 
Q