I cant get my new app version built because apple has the white and blue + no longer showing to create new app version. I have a rejected app due to IAP's not approved. This requires a new version of the app to get them approved so im stuck until new version is submitted for IAPs to get approved through.

Hi everyone, I’m building a messaging app because I’ve seen firsthand how much support and safety is overlooked for this generation online. My goal is to give teens a foundation of security, privacy, and mental health support, while still letting them connect freely. I want to leverage Apple’s platform to help this mission reach the right audience and have real impact. The app already includes: Community chat with message blurring for sensitive or harmful words. Anti-shoulder surfing tools to protect private conversations. Shake dashboard for quick access to emergency services. In-chat locks with ML detection for grooming patterns, offering resources while respecting privacy. Full user control: messages can be deleted anytime, blocking is permanent, and accounts can’t bypass restrictions on the same device. User consent-first design: every feature is opt-in and controlled by the user. At this point, I’m looking for guidance on how to position and prepare the app to reach Apple editorial or headline attention — what steps or best practices help mission-driven apps get noticed for features, WWDC spotlights, or App Store promotion? My focus isn’t just on improving the app, but on launch strategy and visibility in a way that amplifies the mission responsibly. If it’s helpful, I can share a TestFlight build or walkthrough to illustrate the app in action. Thank you for any insights or advice — I want to make sure this mission has the best chance to reach and support the generation it’s built for.

Hello Apple Developer community! While reading the SSC Full Terms and Conditions, I noticed that "Your app playground requires sign in" is a term for disqualification. If our app idea requires sign in for personalization and security, can we submit a prototype without the sign in feature and add it later before publishing the app? Or should we steer clear of app ideas that require sign in altogether?

I have a strange problem. My code works perfectly on my iPhone, i.e. on a real iPhone, but when I upload the build version to TestFlight, it no longer works. I use React Native. The issue is as follows: I have created a code for Grid View that runs automatically when another person joins the stream. It works locally without any problems, but unfortunately the public version does not work. What could be the reason for this?

There is a bug in Unity Plugins: Corehaptics.AssetPickerDrawer throws exceptions and draws incorrectly when fieldInfo or assetType is null (FB17305973). I fixed it and created a pull request: https://github.com/apple/unityplugins/pull/47 It has been months and this bug is really annoying.

Hello all. I am currently working on a bug that has recently grown due to the beta release of iOS 18.4. I am unable to reproduce the crash at the moment; however, given that the bug is mostly exclusive to 18.4, I was wondering if this is a known issue or one specific to my app? App crashes on the main thread with EXC_BREAKPOINT. Below is the truncated stack trace before the crash: 0x000000018fff6044 (CoreText + 0x00069044) TLine::EnumerateCaretOffsets(std::__1::function<void (double, long, bool, bool*)>) const 0x000000018fff5938 (CoreText + 0x00068938) TLine::EnumerateCaretOffsets(std::__1::function<void (double, long, bool, bool*)>) const 0x000000018fff478c (CoreText + 0x0006778c) TLine::CharIndexToOffsets(long) const 0x000000018fff4564 (CoreText + 0x00067564) CTLineGetOffsetForStringIndex ... [internal code] Aside: I wonder if this has anything to do with some visibly hidden unicode characters.