apple pencil charging

Could you tell me about account security and passkeys? Our service is considering implementing passkeys, and these questions are to understand how Apple protects accounts from third parties. ① Apple website states that two-factor authentication is mandatory for newly created Apple Accounts. When did this requirement come into effect? What are the conditions for users who do not have two-factor authentication enabled? ② Apple website mentions that a verification code may be required when signing into an Apple Account from a new device or browser. Is my understanding of the situations where a verification code is requested accurate, as listed below? Are there any other situations? Completely signing out of the Apple Account on that device. Erasing the device. Needing to change the password for security reasons. ③ If a user is already using a passkey on an Apple device, and then upgrades to a new device, will additional authentication, such as enteri

Title: App stuck in Kids Category review loop — never intentionally published as Kids Our education app has been on the App Store since 2020 under the Education category. We recently submitted an update and it keeps getting rejected under Guideline 1.3 - Kids Category. The problem: we have never intentionally published our app under the Kids Category. Our current App Store Connect configuration is: Age Categories and Override: Not Applicable Calculated Age Rating: 4+ Primary Category: Education Secondary Category: Games No Made for Kids designation is selected anywhere. Here is the timeline: Feb 13: Rejected — You have selected the Kids Category for your app — asked us to add parental gates for links, purchases, etc. Feb 18: Rejected again — Your app does not appear to be designed for kids aged 11 and under — told us to resubmit without Kids Category designation. We replied with screenshots showing Not Applicable is selected and asked what else needs to change. Feb 19: Rejected again — Your app was previously

Hi everyone, For the past three days I've been unable to notarize my app — every attempt fails with an HTTP 500 error from Apple's notarization service. What's unusual is that the error occurs not only during submission, but also when simply validating credentials via store-credentials. Example: $ xcrun notarytool store-credentials notarytool-password --apple-id --team-id --password Validating your credentials... Error: HTTP status code: 500. Internal Server Error Request ID: K6NYCMIFNM66OI2WRG3ORZEDUE.0.0 Please try again at a later time. Since the failure happens at credential validation — before any package is even uploaded — I'm fairly confident this is a server-side issue, not something wrong with my setup or the binary. I've tried across different network connections, same result. Has anyone else been hitting this? Is there a known outage or incident on Apple's notarization infrastructure? Any way to escalate or get a status update beyond checking developer.apple.com/syste

I've tried to enroll in the developer program 8 days ago. I've submitted contact forms for email response. I've called customer support and they've told me there is no way to actually talk to Developer support outside of filing for a contact us form via the contact us option here in Apple Developer. Today I went to check the status and all of the recent issues I've had are gone. I paid for the membership to Apple Developer program. I have not been emailed or called or contacted in anyway and I still have the option to enroll in the Apple developer program but why would I continue over and over again and throw money away after it? I have my app built and ready for Weatherkit integration and testing but I can't access the resources due to not being enrolled in an active developer program. I literally do not know anywhere else to go for help. What am I supposed to do from here?

We are facing an issue with App Store review and would appreciate some guidance. Our application is designed strictly for iPhone devices only. The app includes a SIM binding mechanism that requires sending an SMS from the registered mobile number for device verification. This functionality depends on the physical SIM capabilities available only on iPhone devices. However, during the review process, Apple is testing the app on an iPad device. Since iPads generally do not support sending SMS from a physical SIM (especially Wi-Fi models), the SIM binding process fails, which is resulting in app rejection. We have: Configured the app deployment target for iPhone only. Set the device family to iPhone in Xcode.

We are facing an issue with App Store review and would appreciate some guidance. Our application is designed strictly for iPhone devices only. The app includes a SIM binding mechanism that requires sending an SMS from the registered mobile number for device verification. This functionality depends on the physical SIM capabilities available only on iPhone devices. However, during the review process, Apple is testing the app on an iPad device. Since iPads generally do not support sending SMS from a physical SIM (especially Wi-Fi models), the SIM binding process fails, which is resulting in app rejection. We have: Configured the app deployment target for iPhone only. Set the device family to iPhone in Xcode. Any guidance would be greatly appreciated.

I enrolled in Apple Developer Program and paid on February 5th. Payment was successfully processed, but my enrollment was never completed. The developer portal still prompts me to pay again. I have sent multiple emails with no response. This has been delaying my app launch for 2+ weeks. How do I get this resolved?

My phone's charging port is fried. It only charges wirelessly. Fixing it costs the same as the phone. I currently am having a lot of issues enrolling for apple developer program as well, so I can't use test flight right now. I want to enable developer mode on my phone, but it's never been connected to xcode before, so the option is not available. How do I enable developer mode without being able to connect it to a pc? I have a mac, and both my mac and iphone are on the same apple id. thank you

After upgrading to a new iPhone and restoring from an iCloud backup using the same Apple ID, I noticed an issue with Health app permissions. ■ What is happening On my previous iPhone, an app had permission to read step count data. After restoring to the new iPhone, the app still appears in the Health app under Sources. However, when I tap the app, the usual data type permission toggles (such as Steps) are not displayed at all. As a result, the app is unable to read step count data. ■ Additional details The app itself seems to be recognized as a Health data source. However, the data type permission screen is empty. No ON/OFF switches are shown. The backup was created on iOS 18, and the restore was performed on iOS 26. I have not yet confirmed whether this also happens with other iOS version combinations. ■ Questions Is it expected behavior that Health app permissions (per data type) are not restored via iCloud backup? Has anyone experienced a similar situation where the app appears under Sources but t

Steps to reproduce: Open Xcode 26.3 → Settings → Intelligence → Claude sign-in Click the sign-in button — spinner begins, never completes An email the arrives with a magic link. The magic link opened a browser page which displayed a 6-digit verification code with instructions reading enter this verification code where you first tried to sign in — i.e. back in Xcode. However, Xcode was showing only an endless spinner with no code entry field anywhere in the UI. This is the core bug. I did since manage to complete authentication sign-in through a second browser verification field that eventually appeared after about 10 minutes and did get signed in, but the Claude Intelligence agent still returns Your request could not be completed even after successful sign-in and a full Xcode restart. Prior to this bug starting at 10 am on February 19 I had been using the intelligence agent successfully for about a week. Anthropic did have some sort of event on their system around February 18/19 so maybe this has been a resul