Overview

Hi, I am running build on ios 26.2 device, connected with cable (not wifi) and it crashes because files are not loaded or something. But when i turn off Debug Exetuble, it works just fine. Also, tried to run on ios 18.2 device, with Debug executable On - everything is ok, and breakpoints work. My guess, App crashes on reading and loading Assets and others app files like certificates. XCode run logs shows: **"Too many file errors". ** sample.txt xcode_run_logs.txt Also, exectued image list on lldb console, could not attach here, if needed i can add it with some url here.

We are developing Apple AI for foreign markets and adapting it for iPhone models 17 and above. When the system language and Siri language are not the same—for example, if the system is in English and Siri is in Chinese—it can cause a situation where Apple AI cannot be used. So, may I ask if there are any other reasons that could cause Apple AI to be unavailable within the app, even if it has been enabled?

I changed the AppIcon in Images.xcassets,and distribute a new version on appstore;The icon have changed on the desktop, but elsewhere, such as when switching between apps, the top left corner shows the old version of the icon.When I restart my phone,the top left corner show the new version of the icon;My phone is iPhone 13 Pro Max,iOS 18.4.1;Is there other ways to resolve the problem without restart the phone?

Bank Accounts details are outdated and status is stack on processing with error: "Your banking updates are processing, and you should see the changes in 24 hours. You won't be able to make any additional updates until then." This is now stack for a few years since we activated a previous Apple developer account. we must change banking details as it holds up development of an app with in-app purchases. Finance department has been contacted and they do not answer What shall we do? senior support staff keep referring to finance department and is not helping

I'm ready to submit a new app with 3 subscription plans. But the status of the group remains 'Prepare for Submission.' And it won't change. All the individual subscription plans have the 'Ready to Submit' status. I have triple-checked individual plans to see if there is anything missing. No. Nothing is missing. There are no pending business contracts to review, either. I have even deleted an existing group and created a whole new subscription group. And I still end up with this prepare status. Am I the only one having this subscription group difficulty? One thing that I realize is that the status appears as 'Ready to Submit' on individual subscription plans. But their respective localization pair of display name and description get the Prepared status. The display name and the description fields are both filled for all three plans. What a nice, merry, merry Christmas. I don't know what else I can do to resolve this Prepared madness. I've been stuck for 4 hours.

I’d like to submit a feature request regarding the availability of Foundation Models in MessageFilter extensions. Background MessageFilter extensions play a critical role in protecting users from spam, phishing, and unwanted messages. With the introduction of Foundation Models and Apple Intelligence, Apple has provided powerful on-device natural language understanding capabilities that are highly aligned with the goals of MessageFilter. However, Foundation Models are currently unavailable in MessageFilter extensions. Why Foundation Models Are a Great Fit for MessageFilter Message filtering is fundamentally a natural language classification problem. Foundation Models would significantly improve: Detection of phishing and scam messages Classification of promotional vs transactional content Understanding intent, tone, and semantic context beyond keyword matching Adaptation to evolving scam patterns without server-side processing All of this can be done fully on-device, preserving user privacy and aligning with Apple’s privacy-first design principles. Current Limitations Today, MessageFilter extensions are limited to relatively simple heuristics or lightweight models. This often results in: Higher false positives Lower recall for sophisticated scam messages Increased development complexity to compensate for limited NLP capabilities Request Could Apple consider one of the following: Allowing Foundation Models to be used directly within MessageFilter extensions Providing a constrained or optimized Foundation Model API specifically designed for MessageFilter Enabling a supported mechanism for MessageFilter extensions to delegate inference to the containing app using Foundation Models Even limited access (e.g. short text only, strict execution limits) would be extremely valuable. Closing Foundation Models have the potential to significantly raise the quality and effectiveness of message filtering on Apple platforms while maintaining strong privacy guarantees. Supporting them in MessageFilter extensions would be a major improvement for both developers and users. Thank you for your consideration and for continuing to invest in on-device intelligence.

Hi, I have a recurrent problem with an Xcode workspace that I cannot figure out how to solve: When I command-click a symbol (or press ctrl-cmd-J) to find its definition, and when that definition is in a header file belonging to a custom static library, Xcode opens a header located in the derivedData folder rather than in the project's source codes. The exact location of this file is not in the main 'Build' folder but rather in a folder that seems dedicated to indexing: derivedData/myProject/Index.noIndex/Build/Products/Debug/Include/theHeader.h Consequently the file opened by Xcode is uneditable, I have to close it and reopen the source using another method. Even when the correct header is already opened, and I try again, Xcode reopens the wrong file so that it's opened twice with different paths. In the config file of the main application project, I reference the sources of these static libraries like this: HEADER_SEARCH_PATHS = ${SRCROOT}/myLibrary1/Sources ${SRCROOT}/myLibrary2/Sources ${SRCROOT}/myLibrary3/Sources However, removing this doesn't fix the issue and I don't see any other related-settings. Any idea to fix this annoying issue would be greatly appreciated, thanks!

I'm an algo engineer-turned-entrepreneur. About two months ago, I signed up for the Apple Developer Program. Last month, I launched an AI avatar video calling app called Twome (pronounced "Two-me") on the App Store. But just a few days after launch, I used EAS Update (a React Native tool for hot updates) to push a quick bug fix, and soon after, I got hit with a "Pending Termination Notice." They said I violated the Apple Developer Agreement—my app got pulled, and my developer account was flagged for removal. (The App Review message was pretty vague: "App submissions from your account have engaged in concept or feature switch schemes to evade the review process." I'm guessing that's what triggered it.) I was totally shocked. I'd done my homework beforehand and seen tons of devs saying hot updates for bug fixes were fine. No choice but to appeal, so I filed one right away on the App Review Board. Then came the real nightmare: 28 whole days later, I finally got a response—and they upheld the rejection. The reasoning was even fuzzier this time; it felt like a copy-paste template. No specific evidence like before (at least the first notice had some details). Maybe they realized our update didn't actually change any features? Anyway, I'm trying another appeal now, but who knows when it'll come back. The waiting is brutal. We did a full internal audit and pinpointed just two things that might've raised red flags with App Review: Post-launch, we tested an unreleased "rate us" feature and posted a review using our developer account. We figured the App Store would know it was from the app owner and auto-remove it from public view. It was our only review, and we didn't think it'd count as misleading since Apple handles that stuff. The bug fix hot update I mentioned. Beyond that, our post-mortem showed zero other issues. All metadata, product descriptions, and screenshots are 100% compliant—no misleading claims, no dark patterns pushing payments, nothing. Before launch, friends were hyped, saying it'd blow up—it's the world's first realistic AI digital human real-time video calling app for everyday social/entertainment use, aimed at regular folks. But now we're tied up in knots with this appeal mess, desperate to get back on the Store ASAP. It's insane that appeals take a full month to get a response—especially when we didn't blatantly violate anything, or at worst, tripped over something unintentionally. We've already been down for over a month without even knowing the exact issue. Feels way too harsh. Posting here to ask: Has anyone dealt with something similar? Is a 28-day wait (or more) normal for appeals? Any ways to expedite the process? Any practical advice would be hugely appreciated!

I was planning to add the Facebook SDK in one of the releases, and I had everything prepared (including changing the privacy policy to state that my app tracks users for advertising). I changed the privacy policy in the App Store connect, thinking that this wouldn't take effect until I sent the app to review. However, after careful consideration, I decided not to move on with the Facebook SDK. My app does not currently track users for advertising. Even though I sent a new release (UI improvements only), I still can't change the privacy policy to remove that my app "tracks" the user. I read multiple posts with people facing similar issues. For my binary, I have: No PrivacyInfo.xcprivacy file NSUserTrackingUsageDescription in Info.plist No tracking declarations in my app configuration I contacted support, and I was redirected here. My case number is 102778907920

I'm updating an existing distributed game to add turn-based matches. When the Matchmaker ViewController Info Button next to a game is pressed, the results vary: iOS 15.x - Button under avatar says "Accept Invite" or "View Game" (depending on if invite has already been accepted) iOS 18.x - Button always says "App Store" - I assume that means it would lead one to the App store to install the game. Both devices (iPad 15.x and iPhone 18.x) have the same version of the game installed. The results are the same when running in the simulator. When the game is released, I assume this button will work properly, no?

Hello, We are trying to use the new Background Upload Extension to improve uploads of assets (Photos, Live Photos, Videos) in the background in our application. 1-The assets have finished uploading, but I'm unable to retrieve successful records using PHAssetResourceUploadJob.fetchJobs(action: .acknowledge, options: nil). When will the successful records be returned? 2-How to retrieve the system's pending tasks ? We want to cancel tasks handed over to the system when returning to the main app to avoid duplicate resource uploads. 3-When we set UploadJobExtensionEnabled = true, will tasks handed over to the system still execute after returning to the main app? Do we need to set UploadJobExtensionEnabled = false upon returning to the main app? If we set UploadJobExtensionEnabled = false, will previously submitted upload tasks be cleared?

We have initiated the development of a new application, which is exclusively compatible with Apple silicon chips. As our application utilizes artificial intelligence, it is not operational on Intel-based systems due to specific technical constraints. Using the Transporter app, we tried to submit a package that only supports arm64 but we received the following message: "Validation failed (409) Invalid bundle. The “live-mac.moises.ai.pkg/Payload/Moises Live.app” bundle supports arm64 but not Intel-based Mac computers. Your build must include the x86_64 architecture to support Intel-based Mac computers. For details, view: https://developer.apple.com/documentation/xcode/building_a_universal_macos_binary. (ID: 8b93f8c7-ac3d-4665-934a-e1a81832cc18)" Upon reviewing your documentation, I noticed that: "To only support Macs with Apple silicon, your application must require a minimum OS version of macOS Monterey 12 or later and must never have supported Intel-based Macs." Given that we launched a universal package as our initial version, I would like to inquire if there are any alternative approaches that would allow us to limit the distribution of this application to exclude Intel chips.

Several lessons in Keep Going with Apps cannot be completed even when the code is correct. This blocks progression and greys out the Next button permanently.

Hi; Here is a simple program that reads a file and counts number of 1s bits in it. The file it reads, simple.txt, is a static text file, resides in the file system, and nothing is touching it during the program execution. The file's length is 436 bytes. When the program is run in the terminal it produces consistent results. Each run counts 1329 1s bits. It behaves differently when run in Xcode. A simple command-line tool project having a single file. Running the program multiple times, via Command-R, produces something strange. That is each execution randomly produces one of two results. One is expected 1329 1s bits, another one shows 1333 1s bits. That is it counts four bits more. Again, each run randomly produces one of those two results. And it happens only when I run the program in Xcode. I tried a different sample text file and experienced the same behavior, but the difference in 1s bits count was five bits. Any idea of how this behavior can be explained? func countOnes(in byte: UInt8) -> Int { var nOnes = 0 var mask: UInt8 = 0x1 while mask != 0 { if (byte & mask) > 1 { nOnes += 1 } mask <<= 1 } return nOnes } func countOnes(in buffer: UnsafeMutableRawBufferPointer, length: Int) -> Int { var nOnes = 0 for byte in buffer[0...length] { nOnes += countOnes(in: byte) } return nOnes } var fd = try FileDescriptor.open("sample.txt", .readOnly) var buffer = UnsafeMutableRawBufferPointer.allocate(byteCount: 4096, alignment: 4) var nBytes = try fd.read(into: buffer) var nOnes = 0 while nBytes > 0 { nOnes += countOnes(in: buffer, length: nBytes) nBytes = try fd.read(into: buffer) } buffer.deallocate() try fd.close() print(nOnes) My machine Darwin MacBookPro 24.6.0 Darwin Kernel Version 24.6.0: Wed Oct 15 21:08:19 PDT 2025; root:xnu-11417.140.69.703.14~1/RELEASE_ARM64_T8103 arm64 macOS Sequoia 15.7.2 Xcode 26.1.1 (17B100) Thanks, Igor

Hello- I'm new to this so I'm in need of some help. I've attempted to upload a number of versions of tiny apps I've been making to beta test with friends. However I am unable to install the app via TestFlight on my own phone and iPad. As I get the error message "The requested app is not available or does not exist." I've seen a lot of posts with the same problem but no fixes. I've been going through the Apple documentation and I can't figure out what I'm missing. Has anyone had this problem and solved it? I'm uploading to App Connect. I guess I'll try the straight to TestFlight option next. Any help is appreciated.

Environment Device: iPad Air (5th generation, M1) OS Version: iPadOS 26.1 Device Orientation Lock: OFF Stage Manager / Multitasking: Disabled App Mode: Full screen (UIRequiresFullScreen = true) Supported Orientations: iPhone: Portrait + Landscape iPad: Landscape only Description On iPadOS 26.x, when device orientation lock is OFF, iPad apps that support only landscape orientation can be displayed in portrait orientation, even though portrait is explicitly not supported for iPad. This issue: Occurs not only at app launch Can also happen during runtime, such as: Returning to the app from background Unlocking the device Rotating the device while the app is running Switching focus (Control Center, Notification Center, multitasking gestures) When orientation lock is ON, the system consistently respects the app’s supported interface orientations and the issue does not occur. This behavior is a regression in iPadOS 26.x. Expected Behavior Regardless of device orientation lock state: The system should never display an app in an unsupported orientation supportedInterfaceOrientations must always be enforced Physical device orientation should only be applied within supported orientations Actual Behavior With orientation lock OFF: The system can force the app into portrait orientation This happens even though portrait is not listed in UISupportedInterfaceOrientations~ipad The app UI becomes incorrectly laid out or broken With orientation lock ON: Orientation behavior is correct and stable This suggests iPadOS 26.x is allowing device orientation to override supportedInterfaceOrientations during runtime. Info.plist Configuration UIRequiresFullScreen UISupportedInterfaceOrientations UIInterfaceOrientationPortrait UIInterfaceOrientationLandscapeLeft UIInterfaceOrientationLandscapeRight UISupportedInterfaceOrientations~ipad UIInterfaceOrientationLandscapeLeft UIInterfaceOrientationLandscapeRight

Hi everyone, I have a question regarding App Store approval. In my country, Apple In-App Purchases are not supported, so for users in unsupported regions we need to use a third-party payment provider. For countries where In-App Purchases are supported, we plan to use Apple IAP. Could you please advise on the correct approach to ensure the app complies with App Store guidelines and can be approved?

I’m trying to test IAP in Sandbox, but I can't find any product IDs. It seems my Paid Apps Agreement is still "Pending User Info" even though Bank, Tax, and Compliance forms are all marked as "Active." It’s been over 10 hours. Does anyone know what "Pending User Info" might refer to if everything looks complete? I noticed I left the "Nickname" field blank in the Tax Form—could that be the reason? If so, how can I edit it since the forms are already submitted?

I'm developing a watchOS nap app that detects when the user falls asleep by monitoring heart rate changes. == Technical Implementation == HKWorkoutSession (.mindAndBody) for background execution HKAnchoredObjectQuery for real-time heart rate data CoreMotion for movement detection == Battery Considerations == Heart rate monitoring ONLY active when user explicitly starts a session Monitoring continues until user is awakened OR 60-minute limit is reached If no sleep detected within 60 minutes, session auto-ends (user may have abandoned or forgotten to stop) App displays clear UI indicating monitoring is active Typical session: 15-30 minutes, keeping battery usage minimal == The Problem == HKWorkoutSession affects Activity Rings during the session. Users receive "Exercise goal reached" notifications while resting — confusing. == What I've Tried == Not using HKLiveWorkoutBuilder → Activity Rings still affected Using builder but not calling finishWorkout() (per https://developer.apple.com/forums/thread/780220) → Activity Rings still affected WKExtendedRuntimeSession (self-care type) (per https://developer.apple.com/forums/thread/721077) → Only ~10 min runtime, need up to 60 min HKObserverQuery + enableBackgroundDelivery (per https://developer.apple.com/forums/thread/779101) → ~4 updates/hour, too slow for real-time detection Audio background session for continuous processing (suggested in https://developer.apple.com/forums/thread/130287) → Concerned about App Store rejection for non-audio app; if official approves this technical route, I can implement in this direction Some online resources mention "Health Monitoring Entitlement" from WWDC 2019 Session 251, but I could not find any official documentation for this entitlement. Apple Developer Support also confirmed they cannot locate it? == My Question == Is there any supported way to: Monitor heart rate in background for up to 60 minutes WITHOUT affecting Activity Rings or creating workout records? If this requires a special entitlement or API access, please advise on the application process. Or allow me to submit a code-level support request. Any guidance would be greatly appreciated. Thank you!

In my impression, this issue has been around for years. In the Mac App Store, the app description is collapsed by default. After clicking "More" to expand it, the last few lines of the description are always cropped. It seems that the more content there is, the more content gets cropped. The following screenshots are from the same app, one with the system language set to Chinese and the other to English.