Does Xcode 27 or TestFlight support installing a watch-only beta on an Apple Watch For Your Kids device? I want to test my watch only standalone app on my kids apple watch as that is the only device I have. Is it possible to use that watch for testing standalone apple watch application. The watch is setup as kids watch on my iphone.

Apple, Please Investigate: Two Apps Rejected for Information Already Provided in the Original Submissions Dear Apple Developer Community and App Review Team, I am writing to report a serious and extremely frustrating problem I have experienced with two different applications submitted to the App Store. Both applications were rejected under App Review Guideline 1.3, requesting answers to four questions that I had already answered completely in the App Review Notes during the ORIGINAL submissions. The information was not added after rejection. It was already provided before either application entered review. I fully support Apple’s strict requirements for children’s applications. However, these repeated incidents raise serious concerns about how App Review Notes and supporting documents are handled. **1. Kalimati - كلماتي Apple App ID: 6812125263** Kalimati is an educational application that helps children learn Arabic words and action verbs through interactive activities and animations. When submitting Kalimati for the first time, I explicitly answered all four required questions in the App Review Notes: Third-party analytics. Third-party advertising. Sharing user or device data with third parties. Other collection or processing of user or device information. Despite providing complete answers, Kalimati was rejected on October 11, 2026, requesting answers to those exact same questions. These answers were already included in the original submission! I responded again and resubmitted the application on October 11. As of October 22, Kalimati remains in “Waiting for Review” status, 11 days after resubmission. I contacted Apple Developer Support multiple times. Although I was informed that steps would be taken to expedite the review, the application remains in the queue. This delay followed a request for information that had already been provided. **2. HeroHop: Sky Adventure Apple App ID: 6823625184** After my experience with Kalimati, I took additional precautions before submitting HeroHop on October 20, 2026. I provided the answers in TWO separate places: First: Complete answers to all four questions in the App Review Notes. Second: A detailed two-page PDF attachment titled “HeroHop-App-Review-Notes-Build-8.pdf”, addressing each question individually and explaining privacy practices, data handling, parental controls, and in-app purchases. Nevertheless, HeroHop was rejected the following day with an automated message requesting answers to the exact same four questions! I had answered every question in the designated field AND attached detailed supporting documentation. Yet the application was rejected as though none of this information had been provided. I repeated the answers and resubmitted HeroHop on October 21. The Real Problem The issue is not Apple’s requirement to answer privacy-related questions. Those questions are reasonable and important. The issue is that Apple repeatedly requests information that developers have ALREADY provided in the designated submission fields. With Kalimati, the answers were included in App Review Notes. With HeroHop, the answers were included in App Review Notes AND a separate PDF. Both applications received requests for the same information again. This raises important questions: Are App Review Notes displayed correctly to reviewers? Are supporting documents properly accessible? Are automated requests generated without checking existing answers? Is there a procedural problem in reviewing Kids Category submissions? I cannot determine the cause from outside Apple’s systems. However, experiencing the same issue twice, despite taking additional precautions, strongly suggests that the submission or review workflow requires investigation. The Consequences for Developers Every unnecessary rejection can delay an application for days or weeks. Kalimati has remained in “Waiting for Review” since October 11. Developers spend considerable time preparing applications, testing them, documenting compliance, and answering Apple’s questions. It is extremely frustrating to complete these requirements correctly, only to receive a rejection requesting information that was already provided. This wastes developers’ time, disrupts release schedules, and undermines confidence in Apple’s review process. What Apple Should Investigate and Improve I respectfully urge Apple’s App Review management and App Store Connect teams to investigate and improve the following: 1. Verify App Review Notes: Ensure submitted information is correctly stored, displayed, and examined before requesting additional answers. 2. Verify attachments: Ensure supporting PDFs and documents are clearly visible and accessible to reviewers. 3. Prevent repeated requests: Before issuing a rejection, verify whether the requested information already exists in the original submission. 4. Provide specific explanations: If an answer is insufficient, explain precisely what is missing instead of repeating the same questionnaire. 5. Investigate the Kids Category workflow: Examine why the same four Guideline 1.3 questions are repeatedly requested despite documented answers. 6. Establish an escalation channel: Allow developers to report recurring procedural problems beyond individual rejection decisions. Concern About My Upcoming macOS Application I am currently developing another application for macOS. After these experiences, I am genuinely concerned that I may encounter another unnecessary rejection because information I carefully provide is overlooked. Developers should not have to worry whether their App Review Notes will actually be considered. A Direct Appeal to Apple I am not requesting special treatment, exceptions to Apple’s guidelines, or approval without proper review. I fully respect Apple’s responsibility to protect users, particularly children. I am simply asking Apple to ensure that information developers provide is actually read and considered before applications are rejected for supposedly missing information. Apple, please investigate this issue at both the management and technical levels. If there is a technical problem, fix it. If there is a procedural problem, improve the procedure. If answers are insufficient, explain exactly what is missing. This is a real and recurring problem that deserves serious attention. I also invite fellow developers to share their experiences: Have you received a Guideline 1.3 rejection requesting the four Kids Category answers even though you had already provided them in your original App Review Notes? I sincerely hope Apple takes this issue seriously and investigates its underlying cause. A Final Request to the Community Please help bring this issue to Apple’s attention. Salman Farhat

We're working on an iOS app distributed through the App Store and installed on an MDM-enrolled device. Our MDM server uses InstallApplication to take management of the already-installed and running app. On iOS 27 betas 3 and 4, processing this command causes iOS to terminate the app and its extensions with SIGKILL. The same flow and MDM payload work without terminating the app on earlier iOS versions (iOS <=26). Environment OS: iOS 27 betas 3 and 4 Does not happen: iOS 26 or iOS 16.7.15 Device: iPhone SE 2nd Gen Enrollment: MDM-enrolled device Distribution: App Store app App state: Already installed and running when management is requested MDM command: InstallApplication Minimal MDM command The MDM server sends an InstallApplication command for the already-installed app: Attributes = { Removable = false; }; ChangeManagementState = Managed; Identifier = "APP_BUNDLE_ID"; InstallAsManaged = true; ManagementFlags = 1; RequestType = InstallApplication; We also tested the equivalent command using iTunesStoreID = APP_STORE_ID instead of Identifier, and removing InstallAsManaged. The targeted running app was terminated in the same way. Steps to reproduce Install and launch the App Store app as an unmanaged app. Enroll the iPhone in MDM. While the app is running, send the MDM InstallApplication command to take management of the existing installation. Observe the unified logs for mdmd, appstored, manageddeviced, installcoordinationd, and runningboardd. The issue can also be reproduced by initiating the same server-side flow while the app is already in the background. iOS 27 log sequence The command is accepted and appstored starts the managed-app tasks. manageddeviced then attempts to mark the app as managed using a null persona (this differs from iOS <26): The running app has a valid persona. After the failed mapping, installcoordinationd explicitly asks RunningBoard to terminate the app to disassociate that persona: After termination, removing the valid persona also fails. The managed-app task later reports success despite the mapping failures and termination. Earlier iOS comparison As an example, on iOS 16.7.15, using the same MDM command, **iOS routes the request through dmd with persona: default. The app remains alive and receives managed-app change notifications. Expected The existing installation becomes managed without terminating the running app, consistent with the behavior on earlier iOS versions. Actual manageddeviced tries to associate the app with persona (null) and fails with MIInstallerErrorDomain Code 191. That failure causes installcoordinationd to request termination of the app and its extensions to disassociate their valid persona. runningboardd terminates them with SIGKILL (isUserKill=0). The subsequent removal of the only valid persona fails with Code 242, although the managed-app task later reports success. Documentation checked The payload follows the documented InstallApplication flow for taking management of an existing app: Apple Docs WWDC26 app MDM updates We have not found a malformed field that explains the iOS 27-only failure. More info Detailed logs and additional info can be found on the Feedback report.

Hello Apple Developer Community, I am seeking an update regarding my Apple Developer Program organization enrollment for Rajagiri School of Engineering and Technology (RSET), India. My enrollment process has been pending for around two months, and I have still not received a clear update regarding the current status. Enrollment ID: 479458S66X Organization: Rajagiri School of Engineering and Technology Country: India I have already contacted Apple Developer Support and followed up regarding this issue. However, I have not received a response to my recent follow-ups. The enrollment is required for us to publish our college's Flutter application on the Apple App Store. Because the organization enrollment is still pending, we are unable to proceed with publishing the application. The required D-U-N-S-related process has also been completed with Dun & Bradstreet. Could an Apple Developer Support representative please provide an update on the current status of my enrollment and let me know if any additional documents or verification are required from my side? As this issue has already been pending for around two months, I would greatly appreciate an update or escalation to the appropriate enrollment team.

Hello Apple Developer Support, I am requesting assistance with our Apple Developer Program enrollment migration from an individual account to an organization account, which has been stuck for [X months]. Timeline: Migration request submitted-3 months back Multiple phone calls and emails with Developer Support since last three months with no clear path forward or explanation of what is outstanding No specific blocker has been communicated to us despite repeated follow-up We urgently need this resolved as we have an app ready for immediate deployment and are fully blocked from publishing. Could an Apple Developer Support representative please review and advise: What specifically remains outstanding for this migration Whether any document or confirmation from our side is pending An estimated timeline for resolution Thank you for your help.

With the declining literacy rates I think it would be incredibly valuable for apple to implement a separate keyboard experience for minors. One without auto or predictive text, swipe to text, or even potentially also voice memos. These are all very convenient features that I think could unfortunately contribute or even enable the literacy crisis as more and more children grow up and rely on technology. I also think bringing back the ‘look up’ tool on highlighted text into the main options would support and encourage more education (or even adding a thesaurus option as well) From: A Gen Z adult who grew up learning how to spell at the same time I learned how to text. Without relying on all of the convenience features that in turn can remove the mental friction that learning to fix your mistakes provides, my iPhone was teaching me how to spell with simple red lines that required me to interact with my spelling in order to correct my mistakes. Note: Autocorrect was still a feature at the time however was often turned off by most people because of text slang culture which coincidentally helped create more intentional spell check interactions. I believe the decision to turn off autocorrect should be considered a more conscious responsibility so it should not necessarily be left up to a child to decide for themselves.

I have created a cute watchOS virtual pet. It is "Made for Kids" and allows no external links/communication without a math gate in either the iOS companion or the main watchOS app. Customers have requested the ability to share their pet with their friends, and to be able to see their friends pets alongside their own in the both apps. Is this acceptable under "Made for Kids", as long as I use DeclaredAgeRange and PermissionKit for non adult users prior to allowing them to share or receive a share? As this is quite a complex feature I don't want to start it without an idea of how likely an update to be accepted. If this is not acceptable, is the solution to remove "Made for Kids" and increase the age rating?

I am reporting what appears to be a serious integrity flaw in Safari under iPadOS 26.3 (and lower) that materially undermines the reliability of Screen Time parental controls. This is not merely a UX inconsistency but a functional contradiction within a system explicitly marketed and positioned as secure parental control infrastructure. Device / Environment Device: iPad Air M3 13" (2025) OS: iPadOS 26.3 Safari (system version) Screen Time enabled with active restrictions Child account (10 years old) Background We deliberately chose an Apple device for school use based on the expectation that Apple’s system-level parental control mechanisms — especially Screen Time — are robust, tamper-resistant, and technically consistent. Screen Time is configured with: App limits Downtime Parental controls enabled with limited web content restrictions (school requirements prevent strict blocking) Safari enabled (mandatory for educational use) further parental control restrictions Because aggressive website blocking would interfere with legitimate school activities, monitoring Safari browsing history is a central supervisory mechanism. When Screen Time is active: Clearing the entire browsing history via Safari is correctly blocked. Clearing history via system settings is correctly blocked. The system explicitly communicates that deletion is not permitted due to Screen Time restrictions. This behavior establishes a clear user expectation: Browsing history is protected against manipulation. The Issue Despite the above safeguards, individual browsing history entries can be deleted easily and silently through the address bar suggestion interface. This creates a structural contradiction: Full deletion is blocked. Selective deletion — which is arguably more problematic — remains possible. Steps to Reproduce Enable Screen Time with restrictions that prevent deletion of browsing history (for example on a student device with a child account). Open Safari and visit any website. Confirm it appears in Safari history. Tap the Safari address bar. Type part of the URL or page title. Safari suggests the previously visited page below the address bar. Swipe left on that suggestion. A red “Delete from History” button appears. Tap it. Actual Result The entry disappears immediately: No Screen Time PIN required No authentication request No warning No restriction triggered No parental notification No audit trace visible Deletion occurs silently and irreversibly. Expected Result When Screen Time is configured to prevent browsing history deletion: Individual entries must not be deletable Deletion must require Screen Time authentication Anything else defeats the protective purpose of the restriction. Real-World Impact In practical use, this allows minors to selectively sanitize browsing history while preserving a seemingly intact record. In our case, this method is widely known among classmates and routinely used to conceal visits to gaming or social media platforms during school hours. The technical barrier to exploitation is negligible. This results in: A false sense of security for parents A discrepancy between advertised functionality and actual system behavior A material weakening of parental control integrity When a system explicitly blocks full history deletion but permits silent selective deletion, the protection mechanism becomes functionally inconsistent and unreliable. Given that Screen Time is publicly positioned as a dependable parental control framework, this issue raises concerns not only about implementation quality but also about user trust and reasonable reliance on advertised safeguards. Request Please classify this as a parental control integrity and trust issue. Specifically: Disable individual history deletion while Screen Time restrictions are active OR Require Screen Time passcode authentication for deleting single entries Screen Time is presented as a secure supervisory environment for minors. In its current implementation under iPadOS 26.3 and before, that expectation is technically not met. This issue warrants prioritization.

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 approved for the Kids category" — told us to resubmit under a new App ID. We replied explaining that we never published under Kids Category and that creating a new App ID would mean losing years of reviews, ratings, and user history. Feb 20: Same rejection, same template response about Kids Category. We have scheduled a Meet with Apple appointment but it is not available soon. Meanwhile our update is blocked. Our questions: Has anyone experienced a similar situation where their app was flagged as "previously approved for Kids" when it was never intentionally submitted under that category? Is there a way to verify which version (if any) was approved with the Kids designation? We cannot find this information in App Store Connect. Has anyone successfully had this flag removed without creating a new App ID? If we did have to comply with Kids Category guidelines, would that remain a permanent requirement even though "Not Applicable" is now selected? Any advice or similar experiences would be appreciated. We have been going back and forth with the review team for over a week and the responses do not address our specific situation.

Hi! Our app has been rejected several times now. We first selected the "made for kids" category because that was the age recommended by apple. Everything went fine at first but now, two updated later, we are starting to get rejected. We unchecked the made for kids box but even after that we are still not getting approved. We have tried to explain our issue to apple support but they aren't giving us any good answers. Is there any way to resolve this issue? We are really in the need of help.

Hi Community, I'm excited to share R Helper, a speech practice app I built with accessibility as the core focus from day one. App Store: https://apps.apple.com/app/speak-r-clearly/id6751442522 WHY I BUILT THIS I personally struggled with R sound pronunciation growing up. It affected my confidence in school and job interviews. That experience taught me how important accessible practice tools are. R Helper helps children and adults practice R sounds with full accessibility support. ACCESSIBILITY FEATURES IMPLEMENTED VoiceOver - complete navigation and feedback Voice Control - hands-free operation Dynamic Type - scales to large accessibility sizes Reduce Motion - respects user preference Dark Mode - user controllable High Contrast compatibility Differentiate Without Color THE CHALLENGE Most speech practice apps ignore accessibility. I wanted to change that and prove that specialized educational apps can be fully accessible. KEY FEATURES Works 100% offline, no internet needed Zero data collection, privacy first Generous free tier with all accessibility features included 10 story missions with gamification 7 languages supported including RTL for Arabic LESSONS LEARNED Accessibility is not hard when you prioritize it from the start. VoiceOver labels and hints make a huge difference. Testing with accessibility features enabled is essential. Standard SwiftUI components handle most accessibility automatically. Reducing motion significantly helps users with vestibular issues. TECHNICAL DETAILS Built with SwiftUI, targets iOS 17 and up. Universal app for iPhone and iPad. Fully offline using CoreData and local storage. No third party analytics, privacy focused. QUESTIONS FOR THE COMMUNITY What accessibility features do you find users request most? How do you test accessibility features efficiently? WHATS NEXT I'm currently working on expanding the word library, adding more story content, improving haptic feedback Thanks for reading. Nour

We have a STEM learning app for kids, and I've been exploring ways to get it listed under the Education Ecosystem Partner (K–12) collection on the App Store. I couldn’t find a clear pathway or guidelines for eligibility. Could you please point me to the relevant documentation or let me know if there's someone I should reach out to for this?

"If your app includes any links outside the app, or offers any in-app or other purchasing opportunities, make sure these are behind a parental gate" Super Awesome and Kidoz are proving with a parental gate on ad click and they also claim that all ads are manually approved (another criteria for ads in Kids apps). So these two are the only ad networks we can use moving forward. Or we can use ad networks like Admob as well? I dont intend not to be in Kids category - so leaving Kids category is not a choice.

We're using RealityKit to create a science education AR app for iOS, iPadOS, and visionOS. In the WWDC25 session video "Bring your SceneKit project to RealityKit" https://developer.apple.com/videos/play/wwdc2025/288 at 8:15, it's explained that when using RealityKit, RealityView should be used in all cases, whereas in the past, SceneKit required SCNView, SceneView, or ARSCNView, depending on an app's requirements. Because the initial development of our app on iOS predates iOS 18's RealityView, our app currently uses ARView to render RealityKit AR content on iOS and iPadOS. Is it recommended that we migrate to RealityView, or can we safely continue using our existing ARView implementation? We'd prefer to avoid unnecessary development cost. If migrating from ARView to RealityView is recommended, what specific benefits should we expect from this transition? Thank you.

I am creating a prototype with the new Screen Time API introduced by Apple. The issue I am facing is, Applications installed in child device is not showing in parent device with FamilyActivityPicker. It is showing in Child device and apps can be shielded from child's device. Can some one describe, how to list the apps in parent's device. Both Device are running in iOS 15.3. Both falls in same family group Child is under 13 yrs old Screen Time enabled in both device and parent device can see child in Screen Time.

First double charge in a same item, i ask the game developer they accept my refund request, but i don’t know why apple rejected my request, they said i haven’t strongly support? how can i send him the support? there are no attach button allow me the send him the conversatio via email. Then suddenly charge me 2 times i haven’t buy item. i request refund they also rejected…why? i didn’t get anything from the game but i had pay already. who can help me to get back my money. totalHK188 miss charged. this is not fair they stole my money. i don’t know why the game developers accept my refund request, who gave apple the right to reject

Is there a way to check in code if a device is under Mobile Device Management? We want to show the users a different screen in the app if it is under device management. This is primarily for devices under Apple School Manager or something similar

Hi, so, we grabbed a couple of nice new watches the other week (Ultra for dad, SE for teenage son). Mostly cool and working together (calls, messages, maps, walkie talkies, etc, etc). All good. But then son said, "Dad, why can't I see my sleep stuff like you can..?". He was right, it wasn't working. Looking around a bit, it turns out that there are a bunch of things that are turned off or not available when pairing a kids watch with dad's phone. From the Apple page: "The following features and apps are not available: Medications, respiratory rate, irregular heart rhythm notifications, ECG, AF History, Cycle Tracking, Sleep, Wrist Temperature, Blood Oxygen, Walking Steadiness, Audiobooks, Remote, News, Shortcuts and the double-tap gesture". Now dev-me reacts to this situation with: "Ok, so let's just build a little standalone sleep app for son's watch. There must be lots of parents out there who would like the same thing". And there are also a bunch of other "family sharing" enabled apps that when you try and use them on kid's phone, say "iPhone requireed", i.e, they don't apparently work with just a watch hooked up to mum or dad's phone. So before I dive into that kind of project, which seems like an obvious fix path from a dev and a parents' point of view: does anybody know if this from Apple's point of view is a hardware, a software or a legal/age limitation? What's the basic framework/dev/design issue here? Is it something on the device(s) that prevents sleep data from even being collected on family/kids paired watches? (Therefore don't bother trying to build an app); I assume not becauses it's just a normal SE used by a kid; or Is it "just" that Apple hasn't wanted to make that available without a kids iPhone too (Therefore you could certainly build a standalone app to do what Apple hasn't wanted to do); or Netiher 1 nor 2, but Apple won't even allow Sleep data collection for kids for some legal/health data reason (Therefore don't bother trying to build the app).

Is there any good framework that can be used in educational app as Learning Management System (LMS). Should be full fledge for creating courseware for E Learning App. Should be compatible with all Apple Platforms. Any help or link will be greatly appreciated. As I didn't found anything that mentions designed for Xcode. All LMS belong to Web based apps.

Is there any good LMS framework that can be easily integrated to develop educational apps. It should have scoring, questionnaire, gamification , certificate generation etc. Any framework as easy as few lines of code and good payment structure would be good idea.