“apple pencil battery life”

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

Hey, I had the same issue. It’s caused by the 26.4 simulator you’re using in the canvas. Go to “Manage Run Destinations,” create a new one with 26.2, and set that to run in the canvas. Hope Apple fixes it at some point.

Sending an email with your situation well documented generally helps. After logging in with your account, clicking this link should lead you to Apple's developer support about program enrollment: https://developer.apple.com/contact/topic/SC1101/subtopic/30006/solution/select Good luck!

The other reply is correct that you can often ignore this warning, but I wanted to add some context since I have spent time debugging stride alignment issues with CoreML on ANE. The warning about unknown strides means that your model's hiddenStates tensor does not specify a memory layout that the E5ML compiler (the ANE backend) can optimize for. The ANE hardware has strict alignment requirements — specifically, the last axis of a tensor buffer needs to be aligned to 64 bytes (or 32 bytes on older chips). If your model runs correctly and produces accurate outputs, the warning is cosmetic — the runtime falls back to a compatible layout automatically. However, you may be leaving performance on the table. In my testing with speech models, fixing stride alignment reduced ANE inference latency by 15-25% because the hardware could use its native tiling strategy instead of the fallback path. When converting your model to CoreML (via coremltools), you can specify the output tensor's memory layout explicitly: import co

OK by this: I tried deleting iOS 18 runtime via Xcode Settings > Components, and even removed iOS 26 runtime then re-downloaded it. But the iOS 18 runtime keeps auto-reappearing right after! I also ran sudo rm -rf against the iOS 18 asset folder, and it just throws a permission error—totally useless. I checked the Info.plist under /System/Library/AssetsV2/com_apple_MobileAsset_iOSSimulatorRuntime/cc1f035290d244fca4f74d9d243fcd02d2876c27.asset/ and confirmed this folder is exactly the orphaned iOS 18.0 simulator runtime. I’m trying to delete this specific cc1f035290d244fca4f74d9d243fcd02d2876c27.asset folder but hit a wall with system permissions. I found this exact issue is already being discussed in the Apple Developer Forum thread here: Orphaned 9GB Simulator Runtime in /System/Library/AssetsV2 - Cannot Delete (SIP protected). It’s clearly a bug on Apple’s side with MobileAsset lifecycle management—these large orphaned simulator runtime assets get stuck in SIP-protected system directori

@HenryToti Thanks — that output shows all of Apple's servers are reachable and not blocked at the network or DNS level, which is what I was looking for. Beyond that, we need the requested bug report and sysdiagnose for a much fuller view of the situation. — Ed Ford,  DTS Engineer

What you'll find is that there are two clients— yours and a (presumably unrelated) 3rd party client. The other ES client is basically a 3rd party logger that's not active. Ours does some auth work, but we're fairly certain in this case it's just monitoring to do reporting and follow-up scans. Do you know exactly what kicked off your helper process? Both in terms of the triggering event and the target file? No. At the time, the system had been idle for 2 hours. In this case, we do observe a system update being staged in the background, but not in all other instances. I suspect it was a FILE_NOTIFY_CLOSE. It would be insightful to know if APFS triggers that or related ES events when decompressing a file. A big part of the problem here is that the data we're looking at is being collected LONG (2+ days) after the problem itself actually occurred, which means we don't REALLY know EXACTLY what happened. I will submit unified logs that cover the period in question, but your point remains. That ES check can now act a