Apple Maps Guides

I’m generally skeptical of using Network framework for multicasts. It should work in general, but: There are a bunch of things it can’t do. And even when it can, you often hit weird edge cases. My general advice — and this makes me very sad — is to stick with BSD Sockets for broadcasts and multicasts. See Extra-ordinary Networking > Broadcasts and Multicasts, Hints and Tips. Having said that, this is weird: [quote='815127021, Anshuman1989, /thread/815127, /profile/Anshuman1989'] Reinstalling the app fixes the issue [/quote] This isn’t a standard pathology I see with Network framework’s multicast support and you are right to suspect local network privacy in that case. So let’s dig into that. First up, you’ve signed your app with the the com.apple.developer.networking.multicast entitlement, right? You didn’t mention that, and it’s very important. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You mean that the compiler crashes? If so, that’s probably something best addressed over in Swift Forums > Using Swift. And speaking generally, to improve your chances of getting traction: Be clear about what version of the compiler you’re testing with. Isolate the code into a small test project that reproduces the issue. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='875498022, dridev, /thread/814235?answerId=875498022#875498022, /profile/dridev'] Im having the exact same issue [/quote] Are you absolutely sure that this is not an Individual team? Because if it is, then the inability to access Certificates, Identifiers and Profiles is a documented limitation. This is a bit of a FAQ, so I finally got around to writing it up properly: Team Member Can’t access Certificates, Identifiers, and Profiles. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

You can expect that most uploads will be notarised quickly. Occasionally, some uploads are held for in-depth analysis and may take longer to complete. As you notarise your apps, the system will learn how to recognise them, and you should see fewer delays. For lots of additional info about notarisation, see Notarisation Resources. Specifically, it links to a Q&A with the notary service team that’s quite instructive. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

If your submission relies on features that are only available on device, I recommend that you built and test it using the Swift Playground app and then request that it be judged in that environment. The major drawback with that is that the current Swift Playground app doesn’t support the iOS 26 SDK )-: I don’t have anything to share about that limitation right now, but if and when I do I’ll update this other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='815182021, backstroke, /thread/815182, /profile/backstroke'] because multicultural themes are a main point of my app, it seems unavoidable to use other languages. [/quote] Agreed. This is one of those cases where it’s important to understand the rationale for the rule. The requirement that everything be in English exists so that the judges can review your submission, both by running the app and looking at the code. So, if the goal of your submission is to show off multiple languages, then that’s your only real option. However, it’s important to put yourself in the position of the judges who review your submission. Will they be able to understand how cool it is? Keep in mind that: Folks who grew up with alphabetic script systems are notoriously bad at recognising logograms. Folks who speak non-tonal languages struggle to hear tones. So construct your submission in a way that someone who only reads and speaks English can understand how cool it is. Share and Enjoy — Quinn “The Eskimo!” @ Developer Techni

Yes, I have encountered this situation as well. The payment was taken immediately. The Apple Developer website still said Purchase your membership... as if it was not purchased. It took Apple a week to get back to me. They are still processing my application now. Hopefully things will progress soon.

Let’s focus this discussion on your other thread. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Apple likely updated ASO signals recently and title keywords may carry less ranking influence now

I just enrolled in the Apple Developer Program and submitted my first two DMGs for notarization on February 7, 2026. Both have been stuck in In Progress for over 72 hours. a6cbabd0-5142-4b98-9282-b99aa8035722 (mono-mac-intel.dmg, submitted 18:38 UTC) 2209d5eb-4946-4908-94a9-86ed57e71039 (mono-mac-silicon.dmg, submitted 18:49 UTC) Team ID: J76VWW7PQR Both uploads completed successfully. The DMGs contain a signed .NET/Avalonia desktop app with a Developer ID Application certificate. All dylibs are individually signed with hardened runtime. I see other developers reporting similar issues in recent threads. Is this a known service-side delay? Is there anything I can do on my end, or should I just wait?

I’m experiencing the same issue. I initially submitted a request about two weeks ago but haven’t received any response. I completed the Apple Developer Program payment, received the “We’re processing your order” email and the invoice, but the membership is still not active anywhere (Apple ID subscriptions, Developer app, or the Developer website). After waiting several days with no update, I made another payment just to be safe and later confirmed that I was charged twice. Even with that, the enrollment status hasn’t changed. At this point, I’ve contacted Apple Developer Support and am waiting for an update on both the enrollment status and a refund for the duplicate payment. If you haven’t reached out to support yet, I’d recommend doing so — this doesn’t seem to resolve itself automatically once it’s past the 48-hour window. Would be curious to hear if anyone has seen this eventually resolve without support intervention.