Hello. I have an 12 year old app that still has some objective-c code in it. I have a place where i have a flip animation between 2 view controllers that looks like this: [UIView transitionFromView:origView toView:newViewController.view duration:0.5 options:UIViewAnimationOptionTransitionFlipFromRight completion:nil]; It has looked like this since 2012 at least. In our production release, it works prior to 26.1, but in 26.1 and 26.2, the flip is off-center and looks weird. it's like both edges flip the same way. It's a little bit hard to explain. If seen at least 2 other app store apps that i have installed behave this way too, from 26.1 and onwards. Anyone else seen this? Is there anything that can be done about it? Thankful for thoughts.
Search results for
missing package product
51,070 results found
Selecting any option will automatically load the page
Post
Replies
Boosts
Views
Activity
After installing the app from App Store or TestFlight, when the user opens the app and then force-kills it multiple times, the app sometimes gets permanently stuck on a black screen at launch. This issue does NOT happen on Flutter 3.24.5 — works perfectly on all tested iOS devices. The problem started only after migrating to Flutter 3.35.6. This issue happens only in real production installs (App Store / TestFlight). It does not reproduce in Debug mode or through Xcode run / Android Studio run. Expected behavior App should show native splash → render Flutter UI normally. Actual behavior Sometimes after killing the app repeatedly: Native splash shows briefly → then screen turns completely black and stays stuck Steps to Reproduce: Install the app from App Store or TestFlight Launch the app Force-kill the app using app switcher Repeat launch + kill multiple times After 3–7 attempts, app gets stuck on black screen on launch Is this a known issue with the latest Flutter iOS engine? Could this be related t
Description SKTestSession.setSimulatedError() does not throw the configured error when testing StoreKit with the .loadProducts API in iOS 26.2. The simulated error is ignored, and products load successfully instead. Environment iOS: 26.2 (Simulator) Xcode: 26.2 beta 2 (Build 17C5038g) macOS: 15.6.1 Framework: StoreKitTest Testing Framework: Swift Testing base project: https://developer.apple.com/documentation/StoreKit/implementing-a-store-in-your-app-using-the-storekit-api Expected Behavior After calling session.setSimulatedError(.generic(.notAvailableInStorefront), forAPI: .loadProducts), the subsequent call to Product.products(for:) should throw StoreKitError.notAvailableInStorefront. Actual Behavior The error is not thrown. Products load successfully as if setSimulatedError() was never called. Steps to Reproduce Create an SKTestSession with a StoreKit configuration file Call session.setSimulatedError(.generic(.notAvailableInStorefront), forAPI: .loadProducts) Call Product.products(for:) w
I’m running into a problem with my Apple Developer enrollment and I’m hoping someone here has dealt with something similar. Initially, I attempted to enrol as a company. That turned out to be a mistake because Apple couldn’t retrieve my correct DUNS number, even though it was properly created in Australia. After two weeks without any reply from the email support team, we called Apple Support directly and were advised to enrol as an individual first and later convert the account to a company. At that point, it felt like the only option. Only afterwards did we find out that converting the account will disable it during the process, meaning we lose the ability to publish updates, including critical bug fixes, right at the start of our project. That’s obviously not workable. We’ve called support multiple times, but they can’t see the progress of the case or give us any estimate. Meanwhile, we’ve already provided everything requested: DUNS creation documents Official company registration papers ID verific
Hi everyone, I’m trying to register fonts system-wide using CTFontManagerRegisterFontURLs with the .persistent scope. The fonts are delivered through Apple-Hosted Background Assets (since On-Demand Resources are deprecated). Process-level registration works perfectly, but persistent registration triggers a system “Install Fonts” prompt, and tapping Install causes the app to crash immediately. I’m wondering if anyone has successfully used Apple-Hosted Background Assets to provide persistent, system-wide installable fonts, or if this is a current OS limitation/bug. What I Expect Fonts delivered through Apple-Hosted Background Assets should be eligible for system-wide installation Tap “Install” should install fonts into Settings → Fonts just like app-bundled or ODR fonts App should not crash Why This Matters According to: WWDC 2019: Font Management and Text Scaling Developers can build font provider apps that install fonts system-wide, using bundled or On-Demand Resources. WWDC 2025: Discover Apple-Hosted Backgr
Topic:
App & System Services
SubTopic:
Processes & Concurrency
Tags:
Core Text
Background Assets
Typography
Concurrency
SharedModelContainer.txt Folks who filed their feedback report may have gotten responses from the feedback system. For people who see the same issue but haven't yet filed any feedback report, I'd like to share our investigation here to hopefully help. To give you more context, SwiftData (with DefaultStore) uses Core Data as its underlying storage mechanism. At runtime, SwiftData converts the schema to an in-memory Core Data model (NSManagedObjectModel), and uses the model to load and persist the data store. Before system 26.1, when handling an attribute of an array type, SwiftData converts the array type to Binary Data. On system 26.1, it instead converts the type to Transformable. This change leads to a difference between the in-memory model and the model used in the persisted data store, triggering a migration error with the following message: Error Domain=NSCocoaErrorDomain Code=134140 Persistent store migration failed, missing mapping model.” To work around the issue, you might consider the follo
Topic:
App & System Services
SubTopic:
iCloud & Data
Tags:
Does anyone know why a CPU (and Neural Engine)-intensive job like this would slow down so dramatically when using BGContinuedProcessingTask in the background on iOS 26+, despite apparent similar resource-usage metrics? I'm not entirely certain of this, but if I had to guess, it could be happening because you lost GPU access when you entered the background. Try testing with the Metal System Trace, as I suspect that will show you a resource shift that wouldn't necessarily be visible in Activity Monitor. Are there internal iOS scheduling/hardware-allocation behaviors (e.g., falling back to lower-performing cores when backgrounded) that might explain this? Priority certainly does shift when you enter the background; however, the shift you’re describing is larger than I'd expect from that, especially since BGContinuedProcessingTask is involved. I'll also note that in your list here: ...the measured system resource metrics (process CPU usage, system CPU usage, memory, QoS class, thermal state) showed no me
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I tried deleting the configuration file, but I ended up with an alert asking me to sign in with my sandbox ID. I did, and it returned an error: Request Canceled. It is as if the purchase function doesn't update the currentEntitlements. This is my purchase function. Am I doing something wrong? func purchase(_ product: Product) async throws { let result = try await product.purchase() switch result { case .success(let verificationResult): switch verificationResult { case .verified(let transaction): // Successful purchase - deliver content await updatePurchasedProducts() await transaction.finish() // Go back to the map integratePlanAhead() case .unverified(_, let error): // Purchase failed verification throw error } case .userCancelled: // User cancelled the purchase break case .pending: // Purchase is pending (e.g., parental approval needed) break @unknown default: break } } It looks like purchases are never updated for my sandbox user... Thanks for any help :)
Topic:
App & System Services
SubTopic:
StoreKit
Hey there. I'm experiencing a critical issue with Xcode Cloud builds for my macOS application (bundle ID: com.mymind.mymind-mac) where builds fail in Xcode Cloud with 7-8 errors, yet all logs indicate successful completion. Additionally, when manually uploading builds, they become stuck in Processing status indefinitely on App Store Connect. Issue Details: Problem: Xcode Cloud reports 7-8 build errors but logs show no fatal errors Secondary Issue: Builds uploaded to App Store Connect remain in Processing status indefinitely Platform: macOS application with Safari Web Extension Xcode Version: 26.1.1 (26B100) - Xcode 26.1 Build Environment: Xcode Cloud What Works: Package dependency resolution completes successfully Archive creation succeeds (** ARCHIVE SUCCEEDED **) Export succeeds (** EXPORT SUCCEEDED **) Provisioning profiles are created correctly Code signing completes without errors Manual upload to App Store Connect completes What Fails: Xcode Cloud: Build process fails with 7-8 errors, but no co
Topic:
Developer Tools & Services
SubTopic:
Xcode Cloud
in my xcode project, i created a new package by going through File > New > Package, just like they said in https://developer.apple.com/documentation/xcode/organizing-your-code-with-local-packages I have a package, but the problem is, whenever I made any changes in the package's source code, it never showed in the main project. I can import the package just fine, but the package does not show anything. no added apis, functions, nothing. Im using Xcode 26.0.1
Ok, I found this in dmesg/syslog: [46147.634755]: DriverKitSampleA[6170] triggered unnest of range 0x1fc000000->0x1fe000000 of DYLD shared region in VM map 0x853f7106fc70fc7d. While not abnormal for debuggers, this increases system memory footprint until the target exits. [46147.634762]: DriverKitSampleA[6170] triggered unnest of range 0x1fe000000->0x200000000 of DYLD shared region in VM map 0x853f7106fc70fc7d. While not abnormal for debuggers, this increases system memory footprint until the target exits. [46148.219526]: Sandbox: ContextStoreAgent(448) allow file-read-data /Users/daniel/Library/Developer/Xcode/DerivedData/DriverKitUserClientSample-haxyygamobxzqybcidlsjqhbccev/Build/Products/Debug/DriverKitSampleApp.appSandbox: ContextStoreAgent(448) allow file-read-data /Users/daniel/Library/Developer/Xcode/DerivedData/DriverKitUserClientSample-haxyygamobxzqybcidlsjqhbccev/Build/Products/Debug/DriverKitSampleApp.app/ContentsSandbox: ContextStoreAgent(448) allow file-read-data /Users/d
Topic:
Code Signing
SubTopic:
Entitlements
The error occurred when fio attempted to verify the second 1MB data block (starting at offset 1,048,576). So what's IS there? And what should have been? These test use hashes for verification because it's the quickest way to validate the data, but the question I'm interested in here is what your driver actually put on disk. Part of my concern here is that unless you artificially cut power to the device, we shouldn't have needed any explicit cache sync as part of the copy. The system should have flushed all of it's buffers to your DEXT as part of unmount and you should have flushed them to disk shortly after that. If this is really about cache flushing, that's the failure case I'd really be concerned* about here, not the individual copy. *Failure to flush a file loses file data. Failure to flush file system blocks loses volumes. __ Kevin Elliott DTS Engineer, CoreOS/Hardware
Topic:
App & System Services
SubTopic:
Drivers
Tags:
I'm sorry for the delay in submitting a feedback item; a cross-country move happened. Not a problem, I've got plenty to keep my busy! That leads to here: I've submitted FB21093202. So, looking over the bug, there are a few things I want to clarify: F_FULLFSYNC is basically always going to be relatively slow. The API operates on a file handle, but flushing the volume to a coherent state is a broader operation the final I/O command is a device command. All of that makes it a fairly heavy operation. On the APFS side, the specific concern I have here is about the performance dip at high core count. That's partly because of the immediate issue and mostly because our core count has been increasing, and we need to be watching for these concurrency bottlenecks. Cross platform comparisons are very tricky here because the platforms are (ideally) making different design decisions based on the specifics of of their particular use case and user base. For example, in an enterprise/server environment, there's an argument th
Topic:
App & System Services
SubTopic:
Core OS
Tags:
I appreciate your previous answer. Could you please clarify what exactly is meant by “manually reset preferences” in this context? Which settings and user data are expected to be reset? Are there any settings that should explicitly not be affected? (e.g. login state, account data, personalization data etc.) What should the expected user experience be after a full reset? For example, should the app return to default configuration/factory settings? Should we display warnings or confirmation dialogs before performing the reset? If so, what exactly should the user be informed about (data loss, required reconfiguration, etc.)?
Topic:
App & System Services
SubTopic:
General
Tags:
Thanks for the replay @DTS Engineer. You are right on my requirement, currently I am looking for iOS but I would be happy with a solution that works across apple platforms as well. If so, to what end? To answer your query on why I want to detect debug build I won't be able to share my exact use-case but I will share a parallel use-case that currently Apple uses: Currently Apple allows developers to send push notifications to iOS with APNS. From what I understand, APNS exposes sandbox and production environments which are controlled with aps-environment entitlement. Since, Apple controls the tooling side of iOS development, they can inject entitlement based on the provisioning profile. I want to achieve something similar to this where the REST API domain used by my framework is decided based on either provisioning profile or build type. A lot of the time it’s not the build configuration that matters, it’s the way that the app was signed. Or the way that’s it’s run (from Xcode or like a user would).
Topic:
Developer Tools & Services
SubTopic:
General
Tags: