Since moving up to IOS18 lat week I am getting an indication that there was a significant drop in IMU data being sent. Using the search capability, I can find very little information in the Developer Documentation that will tell me what the cause is and how to remedy it. Is there some documentation repository like Tech Notes that will tell me what I need to know to get going again? What additional sources of documentation are available for developers? The Search engine used for Developer documentation just does not cut it because it delivered a lot of useless entries that have no obvious relevance to my search terms. "2024-06-20 19:27:00.669334-0500 RoomPlanExampleApp[902:299709] [Technique] ARWorldTrackingTechnique <0x104bf6d80>: SLAM error callback: Error Domain=Slam Error Code=7 "Non fatal error occurred due to significant drop in a IMU data" UserInfo={NSDescription=Non fatal error occurred due to significant drop in a IMU data, NSLocalizedFailureReason=SlamEngineNodeGroup Failure: IMU issue: gyro data stream verification failed [Significant data drop]. Failed on timestamp: 53902.785827, Last known timestamp: 53901.416828, Delta: 1.368999, System timestamp: 53902.786251, Delta between system and frame: 0.000423. }"

I'm currently using Expo for a React Native project, and I am integrating Apple Pay, so I needed to use Xcode for the setup. Whenever I open Xcode and try to open my project, I get: My Mac OS is up-to-date. I'm using Xcode version 15.3 because 15.4 from the Mac App Store won't install properly. I've used Xcode before to open projects, and for some reason it's not working. I can open individual files in my project folder but whenever I try to open a directory it gives me the error. I've been using VS code for everything so far so the permissions for the file should be all good. I've also pulled from the repo and created a new folder and still the same thing happens. Wondering if there are any requirements that I don't know about for the development environment or something.

Xcode will build and analyze fine using the Debug build configuration but trying to use Analyze or Archive with Release configuration generates 3 errors: Undefined symbol: protocol conformance descriptor, Undefined symbol: type metadata accessor, and Undefined symbol: nominal type descriptor causing the linker to command to fail. The library is included and already linked and a previous version did not have the error so I think it's a code issue but not quite sure what it is or how to fix! The project/package can be found here: https://github.com/kudit/Device/tree/v2.1.17 (to reproduce, checkout this version and rename appending ".swiftpm" to the folder, then right-click to show package contents, open the Development folder and open the Xcode project there. It's done this way so the package can be imported and edited on iPad Swift Playgrounds)

Be warned! When developing your app in Xcode 16 be careful!!! The new SDK has changes that cause builds on Xcode Cloud and other non-beta Xcode to have bugs (EVEN WITH IOS TARGET SET LOWER). This wasted 2 days of development time, but in WKNavigationDelegate, the webView(_:decidePolicyFor:decisionHandler:) method has a new type signature that will ONLY work in the latest SDK. The change was that the decisionHandler now has a @MainActor attribute. This causes Swift to recognize that it "almost" meets an optional requirement and suggests that you change it. If you change it, it will cause builds to not include the optional method.

I recently installed the Swift OpenAPI Generator on my Xcode project. I used it for a little bit but then decided that it would not work how I wanted it to, so I uninstalled it. I uninstalled all the packages related to the OpenAPI generator, and removed the generator from my projects build phases. However, when I try to build and run my project now, I get an error saying that my application could not find the OpenAPI generator script. I did delete this script, but I also removed it as a run build tool plug-in, so it should not be trying to execute in the first place. I used the instructions found in this WWDC23 video (at around the 9:00 minute mark). I am wondering how to completely remove this plug-in. I have tried searching my XCOde project, but I cannot find any indication of this plug-in still existing within my project. I have tried cleaning the build folder as well, but to no avail. What can I do to resolve this issue?

I recently ran out of disk space and discovered that my System Data was consuming 866 GB of storage. After investigating, I found multiple directories named "Dead" nested within my developer data, consuming nearly 600 GB of storage. An example path is: /Users//Library/Developer/CoreSimulator/Devices//data/Library/Caches/com.apple.containermanagerd/Dead These directories contained multiple directories titled "temp.". Rebooting the computer did not empty these "Dead" directories; I had to manually delete them. What is the expected lifespan of the temporary directories stored in the "Dead" directory?

I'm following the guidance from [wwdc24/10171] using Xcode 16 beta 2 on Sonoma (https://developer.apple.com/wwdc24/10171) and find myself unable to active the _EXPERIMENTAL_SWIFT_EXPLICIT_MODULES = YES setting. I tried both in the project file and in the XCConfig file and nothing. After cleaning and building with timing summary, I can't find any "Compiling Swift module" nor any "modules report". I only get multiple statements of "Compiling clang module" and the "GenerateClangModulesReport" What am I doing wrong?

I have a simple little Mac app that embeds a Python interpreter. I wrote this app almost ten years ago and completely forgot about it. Anyway I submitted an update to it with a new version of Python but it's being rejected by App review for the following reason: Your app uses or references the following non-public or deprecated APIs: Symbols: • _Tcl_NewByteArrayObj • _Tcl_ResetResult • _Tcl_MutexLock • _Tcl_GetBooleanFromObj • _Tcl_SetObjResult • _Tcl_CreateInterp • _Tcl_ThreadQueueEvent • _Tcl_UnsetVar2 • _Tcl_GetBignumFromObj • _TclBN_mp_to_unsigned_bin_n • _Tcl_ListObjLength • _Tcl_ConditionWait • _Tcl_GetDouble • _Tcl_GetDouble • _Tcl_DeleteFileHandler • _Tcl_SetVar • _Tcl_SetVar • _Tcl_SetVar • _Tcl_DoOneEvent • _TclFreeObj • _Tcl_Eval • _Tcl_Eval • _Tcl_Eval • _Tcl_FindExecutable • _Tcl_NewLongObj • _Tcl_CreateTimerHandler • _Tcl_Init • _Tcl_ConditionFinalize • _Tcl_GetByteArrayFromObj • _Tcl_ListObjIndex • _Tcl_ExprLong • _Tcl_NewDoubleObj • _Tcl_GetDoubleFromObj • _Tcl_ExprString • _TclBN_mp_read_radix • _Tcl_DeleteTimerHandler • _Tcl_CreateFileHandler • _Tcl_GetVar • _Tcl_GetVar • _Tcl_CreateObjCommand • _Tcl_SetVar2Ex • _Tcl_GetStringFromObj • _Tcl_NewStringObj • _Tcl_GetObjType • _Tcl_MutexUnlock • _Tcl_DeleteCommand • _TclBN_mp_init • _Tcl_GetCurrentThread • _Tcl_ExprDouble • _Tcl_AddErrorInfo • _Tcl_Free • _Tcl_GetStringResult • _Tcl_SetVar2 • _Tcl_SetVar2 • _Tcl_GetBoolean • _Tcl_GetBoolean • _Tcl_RecordAndEval • _Tcl_EvalFile • _Tcl_GetLongFromObj • _TclBN_mp_clear • _Tcl_ThreadAlert • _Tcl_ExprBoolean • _Tcl_DeleteInterp • _TclBN_mp_unsigned_bin_size • _Tcl_AttemptAlloc • _Tcl_GetObjResult • _Tcl_GetWideIntFromObj • _Tcl_NewListObj • _Tcl_ConditionNotify • _Tcl_NewBooleanObj • _Tcl_SplitList • _Tcl_EvalObjv • _Tcl_GetThreadData • _Tcl_GetVar2Ex • _Tcl_NewWideIntObj • _Tcl_NewBignumObj • _Tcl_ListObjGetElements • _Tcl_GetString • _Tcl_GetString • _Tcl_GetString The use of non-public or deprecated APIs is not permitted on the App Store, as they can lead to a poor user experience should these APIs change and are otherwise not supported on Apple platforms. I read online that this is a sort of a widespread issue right now with apps that embed Python (would share links but then my post will have to be approved by a moderator). Anyone have a workaround?

Feedback on Documentation Page for Message Filter App Extension Documentation: Creating a Message Filter App Extension Hello, I am writing to provide feedback on the documentation for creating a message filter app extension. We followed the instructions on the page, particularly the section regarding setting up shared credentials. The instructions state: "Then, you must set up shared credentials as described in Shared Web Credentials, substituting messagefilter for webcredentials throughout the steps. Lastly, you must specify the domains in your Info.plist file, which should look similar to the dictionary shown below." However, when we tried to implement this, we encountered the following error while attempting to save credentials via the SecAddSharedWebCredential function from the message filter extension: Error Domain=com.apple.security.xpc Code=3 "<connection: 0x12e0d4500> { name = com.apple.securityd, listener = false, pid = 0, euid = 4294967295, egid = 4294967295, asid = 4294967295 }: Connection invalid - failed at lookup with error 159 - Sandbox restriction" UserInfo={numberOfErrorsDeep=0, NSDescription=<connection: 0x12e0d4500> { name = com.apple.securityd, listener = false, pid = 0, euid = 4294967295, egid = 0, asid = 4294967295}: Connection invalid - failed at lookup with error 159 - Sandbox restriction} The specific call we did: func SecAddSharedWebCredential( _ fqdn: CFString, _ account: CFString, _ password: CFString?, _ completionHandler: @escaping (CFError?) -> Void ) This error seems related to sandbox restrictions. The documentation does not provide enough information on how to properly set up the environment or what additional configurations might be needed to avoid such sandbox restrictions. More detailed guidance on configuring sandbox permissions and any additional steps required for setting up shared credentials in a message filter extension context would be highly beneficial. Thank you for your attention to this matter. We look forward to any updates or clarifications you can provide to improve the implementation.

When I start the Homekit Accessory Simulator for Xcode 16.0 beta 2 I do not see the Robot Vacuum as an option.

After trying to build with macOS 15 and XCode 16 (beta and beta2), XcodeCloud started to crash at the Resolve package dependencies step. Everything works perfect on my local system running same OS same XC. Details: [<IDESwiftPackageCore.IDESwiftPackageDependencyPlaceholderFileReference, 0x7fb23a2082a0: name:swift path:(No Path)>] Function: unregisterDependencyFileReferences(_:) Thread: <_NSMainThread: 0x600002094200>{number = 1, name = main} Hints: Backtrace: 0 -[DVTAssertionHandler handleFailureInFunction:fileName:lineNumber:assertionSignature:messageFormat:arguments:] (in DVTFoundation) 1 _DVTAssertionHandler (in DVTFoundation) 2 _DVTAssertFromSwift (in DVTFoundation) 3 _DVTAssert(_:file:line:function:varargs:) (in DVTFoundation) 4 DVTAssert(_:_:file:line:function:) (in DVTFoundation) 5 closure #1 in closure #1 in IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore) 6 closure #1 in IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore) 7 closure #1 in OS_dispatch_queue.dvt_sync<A>(execute:) (in DVTFoundation) 8 thunk for @callee_guaranteed () -> () (in DVTFoundation) 9 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation) 10 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation) 11 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation) 12 IDESPMWorkspaceDelegate.unregisterDependencyFileReferences(_:) (in IDESwiftPackageCore) 13 closure #1 in closure #1 in IDESPMWorkspaceDelegate.registerDependencyFileReferences(_:) (in IDESwiftPackageCore) 14 closure #1 in IDESPMWorkspaceDelegate.registerDependencyFileReferences(_:) (in IDESwiftPackageCore) 15 closure #1 in OS_dispatch_queue.dvt_sync<A>(execute:) (in DVTFoundation) 16 thunk for @callee_guaranteed () -> () (in DVTFoundation) 17 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation) 18 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation) 19 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation) 20 IDESPMWorkspaceDelegate.registerDependencyFileReferences(_:) (in IDESwiftPackageCore) 21 closure #1 in IDESPMWorkspaceDelegate.dependencyPackagesDidUpdate(packages:graphHasErrors:) (in IDESwiftPackageCore) 22 closure #1 in OS_dispatch_queue.dvt_sync<A>(execute:) (in DVTFoundation) 23 thunk for @callee_guaranteed () -> () (in DVTFoundation) 24 thunk for @escaping @callee_guaranteed () -> () (in DVTFoundation) 25 __58-[DVTModelObjectGraph performBlockCoalescingModelChanges:]_block_invoke (in DVTFoundation) 26 -[DVTModelGraphTransactionScope performTransaction:] (in DVTFoundation) 27 -[DVTModelObjectGraph performBlockCoalescingModelChanges:] (in DVTFoundation) 28 DVTModelObjectGraph.performBlockCoalescingModelChanges<A>(_:) (in DVTFoundation) 29 IDESPMWorkspaceDelegate.dependencyPackagesDidUpdate(packages:graphHasErrors:) (in IDESwiftPackageCore) 30 SPMWorkspace.packageGraphActionFinished(_:) (in SwiftPM) 31 closure #3 in SPMWorkspace.processPackageGraphActionsInBackgroundIfNeeded() (in SwiftPM) 32 swift::runJobInEstablishedExecutorContext(swift::Job*) (in libswift_Concurrency.dylib) 33 swift_job_runImpl(swift::Job*, swift::SerialExecutorRef) (in libswift_Concurrency.dylib) 34 _dispatch_main_queue_drain (in libdispatch.dylib) 35 _dispatch_main_queue_callback_4CF (in libdispatch.dylib) 36 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ (in CoreFoundation) 37 __CFRunLoopRun (in CoreFoundation) 38 CFRunLoopRunSpecific (in CoreFoundation) 39 +[DVTKVOConditionValidator waitForCondition:sourceObject:keyPathAffectingConditionBlock:timeout:] (in DVTFoundation) 40 -[Xcode3CommandLineBuildTool waitForRemoteSourcePackagesToFinishLoading] (in Xcode3Core) 41 -[Xcode3CommandLineBuildTool _resolveInputOptionsWithTimingSection:] (in Xcode3Core) 42 -[Xcode3CommandLineBuildTool run] (in Xcode3Core) 43 XcodeBuildMain (in libxcodebuildLoader.dylib) 44 -[XcodebuildPreIDEHandler loadXcode3ProjectSupportAndRunXcode3CommandLineBuildToolWithArguments:] (in xcodebuild) 45 -[XcodebuildPreIDEHandler runWithArguments:] (in xcodebuild) 46 main (in xcodebuild) 47 start (in dyld) bash: line 1: 4274 Abort trap: 6 xcodebuild -resolvePackageDependencies -project /Volumes/workspace/repository/***.xcodeproj -scheme '***' -derivedDataPath /Volumes/workspace/DerivedData -hideShellScriptEnvironment Error Command exited with non-zero exit-code: 134

I had code compiling with C++20 using XCode 14.3. I now updated to XCode 15.4, and that feature is not available anymore... No member named 'join' in namespace 'std::ranges::views' Why is join got dropped?

I find odd that the App Store Connect still requires 5.5" iPhone screenshots of the iPhone 8 Plus, given that this specific phone is no longer supported by the latest release: iOS 17. I am well aware that the iPhone SE still has a similar screen ratio, and that it is still being supported by iOS 17, but it doesn't have the same pixel requirements (1242 x 2208), which means that in order for my app to be even reviewed (which is an iOS 17+ exclusive), I'm gonna have to create images that will then be upscaled to the right dimensions. Am I missing something here, or is it Apple who missed this detail?

Hi, I'm looking for help on how to troubleshoot. I will probably file a bug report, but I wonder if it's Xcode or Swift, and I would like to put some more data than I currently have. With Xcode 16 beta 2, the "planning swift module" stage of one of the modules often takes several minutes (between 280 and 300 seconds). Normally it takes a few seconds. The other modules take less than a second. I have a workspace, containing a project and 3 local swift packages. My project contains one iOS app target, 1 framework target (a dependency of the app), and several test targets. The faulty module is the app module.

Xcode 16 beta2; macOS Sequoia Developer Beta; iMac 2019 Intel i5; My app runs fine in Xcode15. but after upgrade to Xcode16 it will crash when I run it. At first it crash in com.apple.CoreMotion.MotionThread, so I delete the code about CMMotionManager. but it crashed again. Xcode15 seems can't run in macOS Sequoia. Should I back to macOS Sonoma?

Prior Xcodes had a very useful function called "sort & unique" that was found under "services" in the contextual menu in the source editor. The new Xcode 16 betas seems to have had this removed, or perhaps it's been moved to a new menu. Does anyone know about this? Thanks!

Environment react-native-iap: 12.12.2. react-native: 0.72.12. Platforms (physical & simulator): iPhone 11 - OS version 17.4 /// iOS Simulator iPhone 15 Pro Max - OS version 17.4 Description Hello, I am trying to test the purchase of a subscription and an in-app product within my react native app. I have setup the necessary Sandbox account in App Store Connect, created a Store kit file in Xcode that I also synced with the products I created in the App Store Connect dashboard. If I use Xcode to run the app on a physical device (after logging into the sandbox account), I am able to purchase a subscription/in-app product without any issues. If I purchased a subscription on the physical phone I can go into Settings > App Store > Sandbox Account Management and see the purchased subscription, change renewal rate, clear purchase history etc.. If I use the TestFlight build with a physical phone (logging in with the sandbox account) the in app purchases stop working correctly. After purchasing a subscription it is not shown in the Sandbox Account Management, so I am unable to cancel it. Upon trying to purchase another subscription the apple service keeps returning the same exact subscription that I "originally" purchased. How am I supposed to cancel that subscription if it not shown in the sandbox account subscription list? Adding a different sandbox account does not help either, trying to purchase another subscription returns the same subscription that I am unable to cancel. Is there a step in the TestFlight environment that I am missing on setup? Expected Behavior Upon purchasing a subscription in the TestFlight environment on a physical device I should be able to cancel that subscription. Here's an example of what function I am calling on purchasing a subscription: const product = { productId: 'example_monthly_subscription' }; subscribe(product.productId); Any help would be appreciated.

I have a VisionOS app that uses a Game Center Leaderboard. On 'appear' of my content view, I check authentication, and if the user is auth'd, I display a 'leaderboard' button. This works on development / TestFlight – the little floating 'Game Center logged-in' pop up shows up when the app runs, and the button appears. Tapping the button opens the leaderboard, and I can tap over to 'global' and see everyone's scores. However, the app launched today on the App Store, and I'm having some issues. The leaderboard button isn't showing up, meaning that the auth call is probably failing silently. Not sure why. If I log out of Game Center on the device, and re-open the app, I'm able to auth and see my leaderboard button. Once I've done that, the leaderboard seems busted. On App Store Connect I can see the values that I expect (high scores from my beta test flight). But, on the production app, the leaderboard is just empty. And there's no 'global' tab to tap on. Wondering if this is a propagation issue? Like, does it take time to roll out the Game Center entitlements when the app is live? I'm going to distribute promo codes to try and get some more people with the App Store version testing for me to see what happens for them. Any help appreciated!

Is it possible to access the RoomPlan API from Objective-C? I cannot figure out how to include the RoomPlan framework into some legacy Objective-C code I have. I can include the RoomPlan.h header but it still does not recognize any of the API classes. I also could not figure out if there was a way to use RoomPlan-Swift.h to expose the API to the Objective-C code.

Hi, everyone! I’m a member of iPhone. Recently I decided to try a new beta version, and I liked it, everything is so new and unusual. However, iOS 18 requires improvements, this update has a lot of errors that I encountered, my problem is that I don't know how to roll back, I want iOS 17 latest again, are there any ways?