“Apple Maps Guides”

Thanks for bringing this to the forums. [quote='820659021, idopte, /thread/820659, /profile/idopte'] returns the following error: Domain: CryptoTokenKit Code: -2 [/quote] That is TKErrorCodeCommunicationError, aka TKError.Code.communicationError in Swift. This is a very generic error that basically means that something went wrong with… well… the communication with the smart card. [quote='820659021, idopte, /thread/820659, /profile/idopte'] At this point, the system appears to be stuck in a non-recoverable state which affects all readers and cards [/quote] Yeah, that’s not good. This is clearly a bug and I appreciate you filing a bug report about it (FB22339746). I took a look at your bug and noticed that you haven’t attached a sysdiagnose to it. Or, more accurately, it says that there’s an associated sysdiagnose log but it hasn’t finished uploading. Please run Feedback Assistant on the iOS device that captured the sysdiagnose log and check on its upload status. Alternatively, export the sysdiagnose log to you

Annoyingly, Xcode has a bug that prevents it from exporting Network Extension apps correctly. See Exporting a Developer ID Network Extension for the details. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

[quote='820631021, Pavel, /thread/820631, /profile/Pavel'] Is it possible for a Network Extension … to act as a client for an XPC service hosted by a Launch Daemon … ? [/quote] Yes. The trick is to use an app group. Sign your client with an app group ID and then, in the MachServices property of the launchd daemon, set the XPC endpoint name to be a ‘child’ of that app group ID. See the discussion in App Groups Entitlement. App groups are a bit tricky on the Mac. See App Groups: macOS vs iOS: Working Towards Harmony for the full backstory. Given that your client is sandboxed, it must claim access to that app group ID. And in that case I strongly recommend that you authorise that claim via a provisioning profile. Your launchd daemon is (presumably) not sandboxed so it doesn’t need to claim access to the app group ID. However, if you decide to make that claim then my recommendation applies there as well: Authorise the claim with a provisioning profile. If you claim access to an app group and don’t authorise that

[quote='820695021, blackson, /thread/820695, /profile/blackson'] when NetworkExtension Activiate. [/quote] What do you mean by “NetworkExtension Activiate”? The Network Extension framework has many different subsystems, many of which can affect the Wi-Fi join process, so I need to understand which one is involved before I can offer any guidance. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

I want to be clear about where things stand. My developer account renewal was processed and payment of £79 cleared my bank on 12 March. I have a bank statement confirming this. The account was therefore active and paid in full — I am not in arrears. Despite this, my app has been removed from App Store Connect and I am now being asked to pay again. This is unacceptable. I will not pay twice for the same membership period. I have two requests: Confirm receipt of the 12 March payment against my account (Team ID: AW699Z7G8H) and restore my app listing immediately. If Apple cannot locate the payment, I will provide my bank statement as proof of transaction and expect the app to be restored upon receipt. If neither of these is actioned, I will have no choice but to dispute the original charge with my bank and submit a formal complaint. I would prefer to resolve this without escalation — but four months of unresolved support and case 102841743378 still open leaves me with limited options. Please escalate th

Please share the URL of the thread in question. Share and Enjoy — Quinn “The Eskimo!” @ Developer Technical Support @ Apple let myEmail = eskimo + 1 + @ + apple.com

Hello, Thanks for your response and for pointing me to TN3186. I have carefully followed the troubleshooting steps, but the issue still persists. Below is a detailed summary of the current situation. Configuration status: The auto-renewable subscription is fully created in App Store Connect Product ID: sylvoy_sylvoy_premium_v2_monthly Status: “Ready to Submit” Pricing is configured and available across regions The subscription is correctly added to the app version under “In-App Purchases and Subscriptions” StoreKit is properly implemented and getSubscriptions is called with the correct product ID Testing performed: Tested on a physical device (not simulator) Logged in with a Sandbox Apple ID Logged out and re-authenticated the App Store account Reinstalled the app multiple times Waited for propagation delays (over 24 hours) Verified that no StoreKit errors are returned (only an empty product array) Confirmed that bundle ID and product ID match exactly Current behavior: getSubscriptions() always retur

Any update from any Apple Engineer please?

I need to confirm , weather the format of url is correct for apple system or it need to be changed Please guide me

I can already tell you, nothing works for me anymore. I updated to macOS 26.4. This morning, it updated Xcode to 26.4 as well. As a result, I had to reinstall Codex, which I did. I logged in, and now nothing works at all. I can submit a request in the chat, sometimes I get a short response, and then it starts thinking about something and never stops. I think it is amazing what kind of unfinished mess Apple is delivering once again. This is absolutely unbelievable. I am furious that such a broken system is being provided to us developers. It would be the easiest thing for Apple to simply test Codex. If they are not even providing us with the latest Codex versions and instead releasing outdated versions with their Xcode, it is outrageous that we are given something so completely unfinished and nonfunctional. With macOS 26.3 and Xcode 26.3, I was at least able to program perfectly fine with Codex and developed several apps. Now I wake up in the morning, want to continue working on my apps, and