-
Notifications
You must be signed in to change notification settings - Fork 96
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mac App Store refuses app via transporter #281
Comments
Make sure you're building a You'll also need to use the Hope this helps. |
Hey! Where you able to get a working build on the Mac App Store (TestFlight) ? |
No. :-( :-( I build both mac and mas and I'm sure that I'm dealing with the right mas file when dealing with transporter. Here is my keys. I do I have "Apple Distribution" and "3rd Party Mac Developer Installer". I'm unsure what kind of configuration I should have to make sure that the build system use the right certificates. Can you be more precise or is there a recent WORKING tutorial somewhere? |
That's annoying man. Share your config files here... I can take a look and let you know if anything stands out. What package builder are you using? I'm currently using I have now managed to successfully package the app and upload via Transporter to TestFlight BUT the app directly hits status "Not Available for Testing" without any error messages or logs. Such a pain. |
I'm a little bit confused. Do you have success or do you have (you too) an issue which would be different from mine? I'm disappointed by Apple. Their certificates are just pure nightmare. All the error messages are completely cryptic. I have complained multiple times on their forums but they don't care. It's like complaining against a wall. I'm using: @capacitor-community/electron@4.1.2 I'm building mas:
and notarize.js:
|
You don't have to notarize the app for Mac App Store submission. Im stuck on a different issue. I can successfully package and upload the build to TestFlight. However it reaches TestFlight with status "Not Available For Testing" - No error message/logs on TestFlight & No help from apple developer support. |
Can you share your setup and configuration similarly to what I have written above? |
@gregoiregentil I was able to solve that same error by switching to electron-forge. But now I'm also getting the "Not available for testing" error |
@gregoiregentil, I think I was also able to fix the error you saw by running this on the .app that was produced by electron-builder. Then repackaging with
but that resulted in this error
which Quinn Eskimo helped me a bit with over at https://developer.apple.com/forums/thread/730398 |
@gregoiregentil I'm new to Electron and experiencing my own issues so I'm no expert, but it looks like your electron-builder config may be missing some things required for the mas build. I've included my configs below along with the back story. @sanjubhambhani @ntbosscher I'm having the same problem with Forge. I was able to get a working build using electron-builder, but I'm still hoping to get Forge working. (Forge config at bottom) I'm using Electron (25.0.0) Forge (6.1.1). I can package with Forge and "make" (dist) with electron-builder (^22.14.13), but I can't figure out how to make with Forge (App Store Connect says "Not Available for Testing" and app crashes on launch).
Works:
Note: The latest version of electron-builder (23.x.x) didn't work. I had to downgrade for it to work (^22.14.13).
|
@nathanarritt One thing that stands out to me is that For an approach that worked for me: electron-userland/electron-builder#4553 (comment) |
I have an app that I can notarize, sign and execute properly. But when I upload it to Mac App Store for review via transporter, I get the following errors:
I suspect that I have a mis-configuration somewhere rather than a bug, but I can't find the problem.
To give more precisions:
What could be wrong? I apologize if it's not a bug.
The only thing that doesn't make sense is that I'm not using the provisioning file downloaded from the apple website for the platform "macOS".
The text was updated successfully, but these errors were encountered: