“DTiPhoneSimulatorErrorDomain Code 2”

We have conducted performance stress tests using an LSI 3108 RAID controller via Thunderbolt 3, configured with 4 HDDs in RAID 5. The results from AJA System Test Lite (4GB, 10-bit RGB) and fio (BS=1M, iodepth=32, Direct=1) show that I/O throughput in Bundled Mode remains at approximately 800 MB/s, which is identical to the performance measured in Legacy Mode. Do either of these tests generate parallel I/O (meaning, multiple threads are generating I/O to the same target)? More specifically, I'd look at: Parallel I/O within the test itself. I/O targeting different partitions on the same target. I/O targeting unrelated targets on the same controller. Also, what does your overall I/O flow look like? Is your card receiving commands fast enough that it's processing them in parallel, even though they arrived as separate commands? What's your peak simultaneous task count? Analysis of the driver logs during these tests reveals that the count parameter in UserProcessBundledParallelTasks is consistently 1, even under h

Thanks for the post, I would recommend to put the output of the console errors on the body of the message as well will easier to see and warning and errors to that point The error I see at the last screen may happen when Xcode attempts to install your app onto a physical device, but the app or probably one of its embedded 3rd party frameworks lacks a valid code signature? If you haven't set up code signing yet, the easiest way to fix this is to let Xcode handle it. Look first at the app team dropdown and make sure everything is valid. Go to the Signing & Capabilities tab and check the box for Automatically manage signing. In the team dropdown, select your Apple Developer account/team. If your main app is signed but a third-party library or framework is not, Xcode will throw this exact error. In General, scroll down to Frameworks, Libraries, and Embedded Content. Look at the Embed column for your frameworks. If you have dynamic frameworks like .framework or .xcframework files that are not

To clarify the issue, our preview pipeline rotates the sample-buffer display layer by applying the RotationCoordinator angle as a transform on the layer itself, while leaving the data-output connection's rotation unset — a pattern that worked on every iPhone before 17 Pro because the buffer always arrived in the same default orientation. On the iPhone 17 Pro front cam the same code renders 90° off: RC still returns correct values, but the buffer's default orientation is itself 90° offset from every earlier device, so RC's angle applied as a layer transform no longer lands upright. The hidden dependency that broke is exactly this — applying RC's angle on the layer only works when the buffer's default orientation is fixed across devices, and since we never set the connection's rotation, we were silently relying on that default, which shifted on this one camera. The supported fix (driving connection.videoRotationAngle directly) corrects orientation but causes the emitted buffer's pixel dimensions to swa

We were even able to reproduce it on an iPad with iOS 17.5.1 and on iPhone with iOS 18.7.8 with one of these two affected apps. With StoreKit 2, AppStore.sync() does not synchronize previously purchased in-app purchases. When attempting to purchase the product again, the message appears that the purchase has already been made, and then the error is thrown at: let result = try await product.purchase() and the purchase cannot be restored. Printing description of nsError: Error Domain=SKErrorDomain Code=0 Ein unbekannter Fehler ist aufgetreten UserInfo={NSLocalizedDescription=Ein unbekannter Fehler ist aufgetreten, NSUnderlyingError=0x12cef54a0 {Error Domain=ASDServerErrorDomain Code=2047 Du hast diesen Artikel nicht gekauft. UserInfo={NSLocalizedFailureReason=Du hast diesen Artikel nicht gekauft.}}}

As I said in my first post, I already filed a bug, FB22735405. I have updated it with the shorter code.

Thank you for your reply, I tried the method you suggested, but folder.circle‘s drawOff animation is still partially missing. iOS Simulator 26.4.1 My code Thanks for the update, @Mim0sa. I see the same thing but only when using SF symbols with certain animations. For example, when I replace folder.circle with text.below.folder the drawOff animation plays in full, but is cut off again with square.and.arrow.up. This might be a bug. I'd greatly appreciate it if you could open a bug report using Feedback Assistant. Include the code you sent as a sample project, so I can share this with the relevant engineering team. Bug Reporting: How and Why? has tips on creating your bug report. Reply with the feedback number once you filed the report.  Travis

We have been experiencing the same issue for a few days now in two of our apps. Users have reported it via email and through negative App Store reviews. In all of our other apps, in-app purchases are still working without any problems. In our case, the issue affects non-consumable in-app purchases (one-time purchases). In one of the affected apps, we can reproduce the issue with a Sandbox user. The problem occurs not only with StoreKit 2, but also with the old StoreKit implementation. We noticed it because we are currently migrating this app to StoreKit 2. With StoreKit 1, in-app purchases can be restored using restoreCompletedTransactions. But when trying to purchase an in-app purchase that has already been bought, the App Store displays a message saying that the item has already been purchased and asks whether it should be downloaded again for free. However, the download/restore then fails: Printing description of nsError: Error Domain=SKErrorDomain Code=0 Ein unbekannter

Thanks for this great post and so interesting, I have always worked with tcp sockets and probably the most fun programming time of my life. But definitely it’s been a while a far from using sockets with Swift. However, there are many great engineers that work on that team and I’m sure they are going to jump in this thread if we can unpack all the details. My first thought was I didn’t see any code showing how are you consuming the sockets to make sure you are not running out of available sockets because the iOS app is abandoning connections without properly closing them. You need a strict teardown process. Whenever you disconnect, encounter an error, or the app goes to the background, you must explicitly cancel the connection and break any retain cycles in your state handlers. Would you be able to create a simple focused project to share here? That'll help us better understand what's going on. If you're not familiar with preparing a test project, take a look at Creating a test project. Albert
  Worl

I don't see that Core Data provides any way for developers to customize the system-provided lightweight migration process, and so can only suggest that you file a feedback report – If you do so, please share your report ID here. You might consider achieving your goal by migrating the data with your own code. That can be a bit involved though, depending on the complexity of your data set. Best, —— Ziqiao Chen  Worldwide Developer Relations.

Thank you for providing additional information. And definitely thanks for providing the focus sample reproducing the issue. May I request that you file a bug so that I can route it correctly to that team? Please include the project not just the code so they can use the project file to reproduce it when creating the bug, you can upload the project on a zip file. Once you open the bug report, please post the FB number here for my reference. If you have any questions about filing a bug report, take a look at Bug Reporting: How and Why? Thanks again for providing everything! Albert
  Worldwide Developer Relations.

What is the current status of this issue? In the Xcode/iOS 26.4.1 SDK, attempting to use Metal 4 symbols still causes an error. The code below works when targeting iOS Device, Designed for iPad, or mac, but for the Simulator, I get the error: “Cannot find protocol declaration for ‘MTL4CommandQueue’; did you mean ‘MTLCommandQueue’?” #import #import @interface MyClass : NSObject @end @implementation MyClass - (void)test { id queue; } @end