Apple Maps Guides

I enrolled in the Apple Developer Program on February 3, 2026. The payment was completed successfully at the time of enrollment, but my membership status has remained “Pending” since then. So far: No request for additional documents or identity verification No phone call from Apple No follow-up email other than the payment confirmation Apple Developer Support has been contacted, but no response yet I understand that verification can take some time, but the complete lack of communication is concerning, especially since this is blocking active development and release planning. If this is a known backlog or system-wide delay, some transparency from Apple would help. I’d also appreciate hearing whether others who enrolled in early February are seeing the same prolonged “Pending” state. Thanks in advance to anyone who can share recent experiences or escalation paths.

Hello! This is already my third post regarding this issue. I have been waiting for almost a month and have sent approximately 10 emails to Apple Developer Program Support. I have received no response at all — no updates, no explanations, and no assistance. What makes this situation particularly unacceptable is that Apple Support is clearly active and responding to similar enrollment issues in other forum threads. Seeing support help others while completely ignoring my case for an entire month is extremely frustrating and difficult to justify. This level of silence from Apple is not just disappointing — it reflects a serious breakdown in the enrollment support process.

We are experiencing notarization submissions that remain in the “In Progress” state for an extended period (over 24 hours), with no status transition and no submission log available. This is occurring in an automated CI environment using the Notary REST API (non-interactive submission and polling). Re-submitting the same package only results in additional submissions also stuck in “In Progress”. There does not appear to be any API mechanism to cancel, clear, or expire these submissions once they are created. We have already opened an Apple Developer Support case regarding this issue (Case ID: 102818066745 & 102819008943), but have not yet received clarification on what is causing these long-running “In Progress” states. This issue is impacting our production release pipeline, as we are unable to reliably complete notarization for signed packages within an expected timeframe. Based on other reports in this forum (including thread 811968), this behavior appears similar to cases where notarization r

Okay, I just pushed a release and notarized. Works great on my test laptop (macOS 26.2) and my test desktop (macOS 14.x) But it seems to fail for a friend who's running macOS 15. I've been using the same GitHub actions successfully for months. How can notarization work for macOS 14 and 26, but not for macOS 15? I think everything looks okay as far as the signing? I've checked codesign -dvv Executable=/Applications/Avogadro2.app/Contents/MacOS/Avogadro2 Identifier=cc.avogadro Format=app bundle with Mach-O thin (arm64) CodeDirectory v=20500 size=11607 flags=0x10000(runtime) hashes=352+7 location=embedded Signature size=8986 Authority=Developer ID Application: Geoffrey Hutchison (…..) Authority=Developer ID Certification Authority Authority=Apple Root CA Timestamp=Feb 5, 2026 at 8:47:21 PM Info.plist entries=24 TeamIdentifier=….. Runtime Version=15.5.0 Sealed Resources version=2 rules=13 files=3306 Internal requirements count=1 size=172 And from spctl -a -vv /Applications/Avogadro2.app: accepted source=