“build disappears”

If I see it correctly, it is currently not possible to validate a drop operation on a DynamicViewContent when using dropDestination? Just a simple example: Let's say I build a folder view on macOS where I can arrange folders freely. In this case I need to use DynamicViewContent.dropDestination to get an insertion index on drop. However, it seems that methods like dropConfiguration do not have any effect. Als dropDestionation(…, isTargeted:) seems not to be available. Here is my sample code: struct FolderRow: View { let folder: Folder var body: some View { DisclosureGroup(isExpanded: .constant(true)) { ForEach(folder.children) { child in FolderRow(folder: child) } .dropDestination(for: Folder.self) { item, idx in print(Dropped at (idx)) } } label: { Label(folder.name, systemImage: folder) .draggable(folder) .dropDestination(for: Folder.self) { items, _ in print(Dropped on Item) } } .dropConfiguration { session in DropConfiguration(operation: .move) } } } struct ContentView: View { @State private var f

after doing all the steps as in The app version submission must be in the “Prepare for Submission” state There must be at least one IAP/subscription in the “Ready to Submit” state All banking & agreements must set up and in place I am still not seeing the In-App purchase and subscription in my iOS App Version page to add to my newest version slash build

Hello everyone, I wanted to check whether other developers have recently experienced unusually long “Waiting for Review” times. Our current submission timeline looks like this: Timeline Feb 14, 2026 – Initial build submitted Feb 14 – Present – Status has remained “Waiting for Review” (never entered “In Review”) Feb 18–19 – Contacted App Review support Feb 24 – Received reply that the case was escalated / expedited Feb 26 – Mar 9 – Continued communication with support; each time they confirmed the app is still in the queue and that they contacted the review team Mar 12 – Still Waiting for Review So as of now, the build has been waiting for review for nearly four weeks without ever entering active review. I’m trying to understand whether this is an isolated case or if others are seeing similar delays recently. Questions: Has anyone else experienced multi-week “Waiting for Review” delays recently? If you had a similar situation, did you eventually receive any explanation from the review team? A

We build TestFlight/App Store builds of our app through Xcode Cloud. Our app uses Metal shaders so we install the Metal toolchain through a ci_pre_xcodebuild.sh script which simply runs: xcodebuild -downloadComponent metalToolchain in our Xcode Cloud builds. This has been working well for us for the last 6 months or so, but since yesterday (March 5) we have been seeing consistent failures when running this script in our Xcode Cloud builds: Beginning asset download... 2026-03-06 04:14:34.727 xcodebuild[13315:58523] Writing error result bundle to /var/folders/6h/_32gb9js77g6c54h3q7g6q1h0000gn/T/ResultBundle_2026-06-03_04-14-0034.xcresult xcodebuild: error: Failed fetching catalog for assetType (com.apple.MobileAsset.MetalToolchain), serverParameters ({ RequestedBuild = 17C7003j; }) Prior to Mar 5 it looks like the toolchain image which was being downloaded/installed was 17C519 but this has now changed to 17C7003j. We haven't changed anything with our Xcode Cloud workflow setu

There is a long-standing, structural issue with the iPadOS Korean IME when using a hardware keyboard. The IME forcibly intercepts the (quote) keydown event and injects Unicode smart/curved quotes (“ or ”) directly into the text field. This hardcoded behavior ignores both: User Settings: The global Smart Punctuation toggle in [Settings > General > Keyboard] is completely ignored. Developer APIs: Setting UITextInputTraits.smartQuotesType = .no on a UITextView or UITextField has absolutely no effect when the Korean keyboard is active. Steps to Reproduce: Set smartQuotesType = .no on a standard UITextView. Connect a hardware keyboard. Switch input language to English -> Press the quote key. (Result: ASCII straight quote - Correct behavior) Switch input language to Korean -> Press the quote key. (Result: Unicode curved quote “ - Incorrect behavior) Impact on Developers & Users: Because the OS IME forcefully injects the curved Unicode character before the app can process the raw key event, develop

When using the new RealityKit Manipulation Component on Entities, indirect input will never translate the entity - no matter what settings are applied. Direct manipulation works as expected for both translation and rotation. Is this intended behaviour? This is different from how indirect manipulation works on Model3D. How else can we get translation from this component? visionOS 26 Beta 2 Build from macOS 26 Beta 2 and Xcode 26 Beta 2 Attached is replicable sample code, I have tried this in other projects with the same results. var body: some View { RealityView { content in // Add the initial RealityKit content if let immersiveContentEntity = try? await Entity(named: MovieFilmReel, in: reelRCPBundle) { ManipulationComponent.configureEntity(immersiveContentEntity, allowedInputTypes: .all, collisionShapes: [ShapeResource.generateBox(width: 0.2, height: 0.2, depth: 0.2)]) immersiveContentEntity.position.y = 1 immersiveContentEntity.position.z = -0.5 var mc = ManipulationComponent() mc.releaseBehavior =

I'm building a macOS app with two separate NSPanel windows, both using the new liquid glass material (NSVisualEffectView / macOS 26). The UI intentionally has two separate floating panels visible at the same time. The problem: only the key window displays the active liquid glass appearance. The non-key panel always renders with the inactive/foggy appearance, even with: NSWindowStyleMaskNonactivatingPanel canBecomeKeyWindow = false orderFrontRegardless() addChildWindow(_:ordered:) Is there any way — documented or otherwise — to force the active liquid glass appearance on a non-key NSPanel? Or is this fundamentally a compositor-level restriction? If it's impossible with two separate windows, is there an alternative approach to achieve two visually separate liquid glass boxes that both appear active simultaneously?

Ok, so I've been following the directions in Apple's documentation here: https://developer.apple.com/documentation/storekit/testing-in-app-purchases-with-sandbox?language=objc It lists a bunch of requirements all of which I have done. I have verified the strings exactly match for the bundle names and the IAP bundle names between my code and AppStoreConnect. The docs continue, saying to prepare to test: During developement[sic], build and run your app from Xcode. At this stage, you don’t need to upload your app binary to App Store Connect to test it in the sandbox environment. When the app loads, I see this error on the console in Xcode: [IAPManager] Store init failed: PurchasingUnavailable - Retrieve Products failed, and could not retrieve any products. UnityEngine.DebugLogHandler:Internal_Log(LogType, LogOption, String, Object) IAPManager:OnInitializeFailed(InitializationFailureReason, String) Unity documentation indicates that my app is reaching AppStore successfully but it is not responding with a

Hello I'm using this sdk DeclaredAgeRange to get the user age range When I'm doing in debug mode using sandbox account it is working as expected and I can get the user age range But when I tried in TestFlight build using sandbox account it is not working and it is always return the age range 18+ and also isEligibleForAgeFeatures API is always returning false Any advise on this?