electron
Team is not yet configured for notarization.
"@electron/notarize": "^2.3.0"
"electron-builder": "^24.9.1"
{ "logFormatVersion": 1, "jobId": "988a3f86-48f9-4713-a0ee-0227951a2d8c", "status": "Rejected", "statusSummary": "Team is not yet configured for notarization. Please contact Developer Programs Support at developer.apple.com under the topic Development and Technical / Other Development or Technical Questions.", "statusCode": 7000, "archiveFilename": "x'x'x'x.zip", "uploadDate": "2024-06-21T11:47:58.128Z", "sha256": "123123123", "ticketContents": null, "issues": null
}
Help !!!!!!!!
Yes, you need to talk with Apple on this. They might have you blocked because of security issues. I had obfuscation so i had to remove it in order for them to allow me to notarize. This process can take 3-4 months from their side.
I have removed the relevant compression and obfuscation, but the error still occurs in the same way; it just returns faster now.
Did anyone manage to solve this ? I have raised ticket to apple and it has been 1 month, i haven't received any solution from their end
- It's been almost 4 months for me since I first faced this issue.
- Contacted Apple developer support. They accepted it as an issue at their end.
- More than 10 email threads exchanged after that waiting for the fix.
- No fix given, no timelines given (not even tentative one), no refunds for Apple developer fee either.
- Their response is always the same - a vague and unhelpful statement:
Our engineers are looking into this. - This is a very old issue and a huge many people have got caught in this. Not a single person seems to have got this resolved. Referances:
- https://developer.apple.com/forums/thread/118465
- https://stackoverflow.com/questions/56660646/apple-notarization-error-team-is-not-yet-configured-for-notarization
- https://github.com/fastlane/fastlane/issues/19686
- https://forum.latenightsw.com/t/team-is-not-yet-configured-for-notarization-error/4714
- https://developer.apple.com/forums/thread/735253
Request everyone whoever gets caught in this, please put this issue and Apple's pathetic behavior towards fixing this on social media. Nothing else is working.
In case anyone reading this have actually found a solution, please do share. Need it ASAP.
Thanks..
PS: My electron app which got caught in this: https://zenquery.app
Hi Nitin. Its frustrating, I got my 2 accounts suspended without any notice. I have made X post - https://x.com/SS_Thakurr/status/1942495952742539533?t=TOiIQFNcTcOr1O4Yh-ioEw&s=19 Kindly retweet it. I am sick of these people ! Its frustrating
On Mon, 7 Jul 2025, 7:37 pm Nitin Bansal, @.***> wrote:
freakynit left a comment (electron/notarize#205) https://github.com/electron/notarize/issues/205#issuecomment-3045344871
- It's been almost 4 months for me since I first faced this issue.
- Contacted Apple developer support. They accepted it as an issue at their end.
- More than 10 email threads exchanged after that waiting for the fix.
- No fix given, no timelines given (not even tentative one), no refunds for Apple developer fee either.
- Their response is always the same - a vague and unhelpful statement: Our engineers are looking into this.
- This is a very old issue and a huge many people have got caught in this. Not a single person seems to have got this resolved. Referances:
- https://developer.apple.com/forums/thread/118465
https://stackoverflow.com/questions/56660646/apple-notarization-error-team-is-not-yet-configured-for-notarization
- fastlane/fastlane#19686 https://github.com/fastlane/fastlane/issues/19686
https://forum.latenightsw.com/t/team-is-not-yet-configured-for-notarization-error/4714
- https://developer.apple.com/forums/thread/735253
Request everyone whoever gets caught in this, please put this issue and Apple's pathetic behavior towards fixing this on social media. Nothing else is working.
In case anyone reading this have actually found a solution, please do share. Need it ASAP.
Thanks..
PS: My electron app which got caught in this: https://zenquery.app
— Reply to this email directly, view it on GitHub https://github.com/electron/notarize/issues/205#issuecomment-3045344871, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ732LVP7SWPSHBSHLKT6QD3HJ5JFAVCNFSM6AAAAABZG7DOTCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTANBVGM2DIOBXGE . You are receiving this because you commented.Message ID: @.***>
Done.
The whole reason Apple is able to get away with this is the same reason they have been able to get away with monopolizing Apple Pay on iOS.... because they have become the IBM of 1984 themselves. A greedy soulless monopolistic corporate.
Shame on you Apple.
It's been over a month I have this issue. I'm on Apple Developer - company account.
Apple Support are useless. Just said that "their engineers are working on the issue". That's insane, literally 1 click in their CRM to let my account notarize apps.
I can confirm that it is 100% not an issue related to the app itself, as I sent the compiled binary to my friend and they were able to notarize it from their Apple Developer (Individual) account.
@Blaumaus It's Apple's issue. And what Im suspecting is that they are intentionally holding specific accounts under this issue. How do I know this?
The moment I started sharing this issue on social media, and threatened them with a class-action lawsuit for hurting my business, within 12 hours this was fixed. And other devs are still facing this. This means it's NOT a common issue in their infra, rather, they are choosing.
We devs, and other small companies, really need to drag Aple into the court. We truly have a winning case here.
@Blaumaus It's Apple's issue. And what Im suspecting is that they are intentionally holding specific accounts under this issue. How do I know this?
The moment I started sharing this issue on social media, and threatened them with a class-action lawsuit for hurting my business, within 12 hours this was fixed. And other devs are still facing this. This means it's NOT a common issue in their infra, rather, they are choosing.
We devs, and other small companies, really need to drag Aple into the court. We truly have a winning case here.
What a joke company, treating devs who PAID for an account like that. I'll try to bring up the class-action lawsuit with them too to a customer support agent, maybe it works? Any tips to do it properly are appreciated
Are you on an individual or company account @freakynit? I'm on company one, and I think maybe if nothing works to purchase another dev membership, but an individual one? Kind of out of options at this point
@Blaumaus They even refused to refund for the payment saying it comes under non-refundable category.
I don't have any tips as such, but, try to share this issue on social media and ask more devs if you have contact with to share too. Apple values it's image too much and might take note. Legal action sure remains a viable course, even better if multiple devs can file together. The reality however is that no one wants to make it into a legal battle. It's messy, costly and gets ugly. Avoidance is best. But Apple is leaving no choice here. The social media approach is kind of like the last resort before legal course is the only way left.
Individual. By the way, I can publish your app from my account if you are okay with it. And don't worry, I won't abuse it. Just want to help.
@freakynit sorry if it's a dumb question, do you know by any chance, if for example I code-sign my app and ask someone else to notarize it so it would run on people's devices. And say in 2-3 months Apple finally let's me notarize my own apps too.
Will there by any issues when people try to upgrade from a version of my app notarized by someone else to the one notarized by me?
I assume it should not matter since notarisation is basically letting Apple check my app for any viruses (right?) and I am the one who code-signs the app in both cases. But still..
@Blaumaus Code-signing and notarization both have to come from same account (not strictly mandatory, but, Apple being Apple, have a very high probability of being rejected if not done this way). There's no harm in trying anyways. Takes a few minutes at max.
None. It's simply a stamp. Nothing related to technicals. But, Apple will show warning since the stamping account has changed. That in-place update would not work. It will be treated as a new app.
I’ve experienced the same situation as you and shared it on Twitter. Please follow and support us! Let’s fight for the rights we deserve! https://x.com/silent_orchid6/status/1954399957479567603
