Overview

Hi everyone Please i need someone to explain this, I wanted to ask if anyone has experienced something similar with their payments. In March, in App Store Connect → Trends → Proceeds, I can see that my total proceeds are $343. However, in Payments and Financial Reports, Apple shows that they will pay me only $258 USD. From what I understand, taxes and Apple’s commission are already deducted when calculating proceeds, so I’m confused about why there is still such a big difference between the proceeds amount and the final payment. Has anyone faced this before or knows what could explain this gap? Thanks in advance for your help!

The AppIntent feature is available on tvOS since OS 16. https://aninterestingwebsite.com/documentation/appintents I tried a real basic integration where I just want simply open a specific tab in my tabbar. But the perform action gets never called. Is it really possible already to use AppIntent on tvOS? Or is this feature still mostly targeted for mobile devices? Also, the documentaiton says so often something about shortcuts app and features, that are not available on tvOS, that I started doubting that the AppIntent is really usable on tvOS. If AppIntents are available and usable for tvOS, what could be wrong, so that I do not see the expected results?

Hi team, may I know how I can access the report for the Safari Smart App Banner here please? We want to know how many people taps to views or install the app from that specific banner. Please advise on this. Thank you.

Hello, we are currently integrating Writing Tools into our macOS application using NSWritingToolsCoordinator with a custom NSView. Overall, the integration is going well and we are generally satisfied with the API. However, text replacement is sometimes not using NSWritingToolsCoordinator callback function. When selecting “Replace” from a preview in a Writing Tools UI popup, the text replacement is performed via the NSTextInputClient callback function (insertText:), which does not seem correct. This is especially problematic in multi-context scenarios, because NSTextInputClient insertText: does not provide the required information about the Writing tools context being used. As a result, it is not possible to determine which context is being modified when managing more than a single context. In our view, Writing Tools should consistently use the callback function of NSWritingToolsCoordinator for text replacement, whatever is the action performed. This is essential for properly handling multi-context use cases. This issue is reproducible with the sample app project provided here https://aninterestingwebsite.com/documentation/appkit/enhancing-your-custom-text-engine-with-writing-tools. If you define a breakpoint in function writingToolsCoordinator:replaceRange:inContext:proposedText:reason:animationParameters:completion: of the Writing tools coordinator, the function is not triggered if text replacement is performed from a preview like for "Summary" with "replace" button. NSWritingToolsCoordinator callback function seems to be called only when text replacement is performed directly inline (in the text view) without external preview so. i have opened a issue with feedback assistant: FB22401950. Best regards.

Hello, we are currently integrating Writing Tools into our macOS application using NSWritingToolsCoordinator with a custom NSView. Overall, the integration is going well and we are generally satisfied with the API. However, text replacement is sometimes not using NSWritingToolsCoordinator callback function. When selecting “Replace” from a preview in a Writing Tools UI popup, the text replacement is performed via the NSTextInputClient callback function (insertText:), which does not seem correct. This is especially problematic in multi-context scenarios, because NSTextInputClient insertText: does not provide the required information about the Writing tools context being used. As a result, it is not possible to determine which context is being modified when managing more than a single context. In our view, Writing Tools should consistently use the callback function of NSWritingToolsCoordinator for text replacement, whatever is the action performed. This is essential for properly handling multi-context use cases. This issue is reproducible with the sample app project provided here https://aninterestingwebsite.com/documentation/appkit/enhancing-your-custom-text-engine-with-writing-tools. If you define a breakpoint in function writingToolsCoordinator:replaceRange:inContext:proposedText:reason:animationParameters:completion: of the Writing tools coordinator, the function is not triggered if text replacement is performed from a preview like for "Summary" with "replace" button. NSWritingToolsCoordinator callback function seems to be called only when text replacement is performed directly inline (in the text view) without external preview so. i have opened a issue with feedback assistant: FB22401950. Best regards.

Hi I am not able to Enroll for the fresh apple developer account getting Invalid request, Service mapping to the requested URL is not available. Invalid request, Service mapping to the requested URL is not available. anyone know the solution or alternative way through which i can enroll to apple developer account

I try to enroll the apple developer program to publish my app . But when I click enroll and fill out the info in the form the result is "Your enrollment in the Apple Developer Program could not be completed at this time." I try to contact apple support and have a call with them and he say he don't known why, he just know my account cannot enroll the program at this time. Is there anyone meet the same problem and able to enroll?

Hello everyone, I have a question regarding the Ultra-Low Latency Frame Interpolation and Super Resolution features introduced in WWDC 2025 Session 300 (https://aninterestingwebsite.com/videos/play/wwdc2025/300/). In the video, it was mentioned that these features run on any device as long as it has iOS 26.0 or later and an Apple Silicon chipset. Based on the official support guide (https://support.apple.com/ko-kr/guide/iphone/iphe3fa5df43/ios), the iPhone 11 and iPhone SE (2nd generation) are listed as supported devices. I just want to double-check and confirm: since they meet the criteria mentioned in the video, do these features actually run without any performance issues or limitations on the iPhone 11 and iPhone SE (2nd gen)? I want to make sure I understand the exact hardware capabilities before proceeding with development. Thanks for your help!

Somehow I ended up with three info.plist and entitlement files in my macOS project. Is this ok, should I merge them? There is only one target.

Navigation title also scroll below the content when using scrollview. working fine in iOS 18 and below. one of the UI component is outside the scrollview which is causing the issue. struct ContentView: View { var body: some View { VStack { Rectangle() .frame(maxWidth: .infinity) .frame(height: 60) .padding(.horizontal) .padding(.top) ScrollView { ForEach(0...5, id: \.self) { _ in RoundedRectangle(cornerRadius: 10) .fill(.green) .frame(maxWidth: .infinity) .frame(height: 100) .padding(.horizontal) } } } .navigationTitle("Hello World") } }

Hello Apple Developer Community, CaseIDs: 102856372004, 102846656019 I’m hoping someone can advise me on a serious issue. Our organization’s Apple Developer Program account has been effectively locked because our Account Holder’s Apple ID is inaccessible. I need to either unlock that Apple ID or transfer the Account Holder role so we can manage our apps. I’ve already reached out to Apple Developer Support since last month, but so far, I haven’t received a response. This situation is critical because our clients rely on us to maintain and update our apps. Key details: • We’re enrolled as an Organization/Company. • The current Account Holder’s Apple ID is no more with Organization and cannot perform any actions. • I have admin/manager access through another Apple ID. I’ve reviewed the documentation on transferring the Account Holder role, but it appears the transfer can only be initiated by the current Account Holder, which is impossible at this point. If anyone has encountered a similar issue or knows a more efficient route to escalate, I’d be extremely grateful for your insights. Thanks in advance for any advice you can share. This is critical to our organization, and we’d appreciate any pointers on how to navigate or expedite the support process.

Navigation title scroll along with the content in iOS 26. working fine in iOS 18 and below. One of my UI component is outside the scrollview which is causing the issue. var body: some View { VStack { Rectangle() .frame(maxWidth: .infinity) .frame(height: 60) .padding(.horizontal) .padding(.top) ScrollView { ForEach(0...5, id: \.self) { _ in RoundedRectangle(cornerRadius: 10) .fill(.green) .frame(maxWidth: .infinity) .frame(height: 100) .padding(.horizontal) } } } .navigationTitle("Hello World") } }

Hello everyone, We are currently preparing for an App Transfer to a new Apple Developer account due to a corporate merger. We are trying to figure out the best way to handle Apple Sign-In user migration and would love to get some advice on our proposed fallback plan. 📌 Current Situation We need to transfer our app's ownership to a new corporate entity. The app heavily relies on Apple Sign-In. The Issue: We did not collect the transfer_sub values during our initial development phase. Although we started collecting them recently, we will not have them for all existing users by the time the transfer happens. 🚨 The Risk (The 60-Day Rule) Based on Apple's documentation, even if we provide the transfer_sub, users must log into the app within 60 days of the transfer to successfully migrate their accounts. This means that users who log in after 60 days, or those whose transfer_sub is missing, will fail the Apple migration process. They will be treated as "new users" and will lose access to their existing account data. 💡 Our Proposed Custom Recovery Flow Since we cannot rely entirely on Apple's automated migration, we are planning to build a custom internal account recovery process to prevent user drop-off: A user (who failed the migration or logged in after 60 days) attempts to use Apple Sign-In on the transferred app. Since the existing account isn't linked, Apple generates a new identifier (sub), and the user enters the new sign-up flow. During the sign-up process, we enforce a mandatory identity verification step (e.g., SMS phone number verification). We query our existing user database using this verified information. If a matching existing user is found: We interrupt the sign-up process and display a prompt: "An existing account was found. We will link your account." We then update our database by mapping the new Apple sub value to their existing account record, allowing them to log in seamlessly. ❓ My Questions App Review Risk: Could this manual mapping approach—overwriting the Apple sub on an existing account based on internal identity verification—violate any Apple guidelines or result in an App Store rejection? Shared Experiences: Has anyone dealt with missing transfer_sub values or the 60-day migration limit during an App Transfer? How did you mitigate user loss? Best Practices: Are there any alternative, safer, or more recommended workarounds for this scenario?

My SwiftUI app runs as a floating card window on iOS 26 iPhone instead of full screen. UIRequiresFullScreen and UIApplicationSupportsMultipleScenes: false don't fix it. What's the iOS 26 Info.plist key or API to opt out of windowed mode? First iOS app, I'm very confused, and have been trying different things for like 3 days. Any nudge in the right direction would be wildly appreciated. Thanks! Mark

I recently completed the payment for the Apple Developer Program successfully and received a confirmation email stating that I would receive a follow-up email within 2 days. However, it has now been more than 2 days, and I have not received any further communication. This is not my first frustrating experience with this process. In the past, I attempted to enroll using a different account, but after waiting for 2–3 weeks, I was only then informed that my payment had failed. During that time, none of my support emails were responded to, which made the situation extremely difficult to resolve. To fix this, I had to coordinate with my bank and obtain a new card, since prepaid cards are not supported for the Apple Developer Program. This time, the payment has gone through successfully—yet I am still facing delays and a complete lack of communication. What makes this even more frustrating is that my app has already been live on Google Play for around 2 months. At this point, I am essentially “stuck” waiting just to complete enrollment with Apple, which is preventing me from moving forward with my iOS release. This raises a few concerns: • Why is there no clear timeline or update after successful payment? • Why are support channels unresponsive during such critical steps? • Is this level of delay normal for all users, or are developers from smaller countries experiencing slower processing times? As developers, we rely on timely onboarding to continue building and releasing our products. Delays like this—combined with no communication—feel highly unprofessional and discouraging. I would really appreciate clarity from Apple or others who have experienced similar delays.

I’m currently facing a serious delay with my Apple Developer Program enrollment and wanted to check if anyone else is experiencing the same issue or has found a solution. I completed my payment on March 30, 2026 (Order Number: W1349796922), and my account status is still stuck on “Pending.” It has been several days now, well beyond the expected processing time. This delay is directly affecting my project timeline. I’m unable to publish my app, and because of this, it is affecting my commitments to my client. It’s becoming a major blocker. I’ve already submitted a support request. Has anyone here faced a similar delay recently? Did your account eventually get approved? Did contacting Apple support (call/email) help speed things up? Is there any specific step I might be missing? Any guidance or shared experience would be really helpful at this point. Thanks in advance.

Team ID: LA64G2ZMY2. Submission f28e6a62-5a46-4554-a4b9-666269b3017f has been "In Progress" for over 24 hours. App is signed with hardened runtime, valid Developer ID certificate, HFS+ DMG format (not APFS - aware of DTS r. 134264492). Codesign verifies clean. All requirements met per Apple documentation. Is notarization provisioning needed for new accounts?

I'm relatively new to socket networking, and am migrating an older project from CocoaAsyncSocket to Swift's native Network. The project utilises GCDAsyncUdpSocket.enableBroadcast(_ flag: Bool), but I don't know how to replicate this in Network. How do I enable UDP Broadcast on NWConnection?

I have been in a rejection loop due to not being able to link the subscription item to the app for months, connect reviewers don't seem to understand my issue So I finally got the IAP /sub section to appear in the version after deleting the first rejected sub product. It linked, the IAP and app were in a 'ready to submit' state as advised from this forum post. I have deleted the sub product twice, got it to link twice but each time I submit the sub is removed from the build and doesn't get reviewed, as the sub product doesn't get approved the build gets rejected. You can clearly see the sub product linked in the attached image below, when I navigate away or refresh the page the sub product is gone and the reviewer can't see the sub product. I have advised the review team numerous times but just get the generic go to the forums etc etc. responses How do I appeal a review? or just some actual help from apple? I basically said all this in my latest reply to review and they said contact help, is that the best route? Sub ID b80d3cf0-ba67-4e6c-83af-28e6bebb973d

After months of hard work developing an app with unique mechanics and a distinct user experience, we recently faced a rejection under Guideline 4.3(b) (Spam/Saturated Category). The feedback we received stated that there are "already enough of these apps on the App Store." While we completely understand Apple's need to filter out low-quality clones, it feels like this guideline sometimes overlooks genuine originality. The most frustrating part for independent developers is that the category you fall into seems to matter more than the actual value your app provides. Whether the app is positioned in lifestyle, entertainment, or productivity, a rigid "category quota" can prevent reviewers from truly seeing the unique features we built. This creates a significant hurdle for new entrants and makes it incredibly difficult for fresh ideas to break into established categories. It feels less about the quality of the application and more about timing—as if early arrivers have a permanent advantage over newcomers, regardless of how much innovation the new app brings to the table. Ultimately, we believe this limits consumer choice. Users deserve the opportunity to discover and decide between new, modern alternatives, rather than having their options restricted by a pre-determined saturation limit. We hope Apple reconsiders how 4.3(b) is applied, ensuring that the App Store remains a place where truly innovative apps, regardless of their category, have a fair chance to be evaluated on their own merits.