I want to use ARKit as a background app. Is it possible? Specifically, I'd like to use it while using an app like FaceTime (using the front camera) and simultaneously record blendshape weights with ARKit (using the front camera). Is it possible to run as a background app? Is it possible to access the front camera information simultaneously? My app uses the ScreenTime API to allow users to block other apps. For some users, the FamilyActivityPicker doesn't render any apps, and they aren't able to block anything. When they go into Settings -> Screen Time, there is no section titled "Apps With Screen Time Access", and when they go into Settings -> , there is no toggle for Screen Time Restrictions - even though they enabled screen time access when setting up my app. Has anyone else seen this issue and/or resolved it? I have a usdz model with animation that I can preview in RCP. When I create a new base/example visionOS project in Xcode it's set up to load in the 'Scene" and "Immersive" reality kit content. But my models don't play the animation. How do I fire off the contained animations in those files? Is there a code snippet that someone can share that takes into account how the example project is setup? Hello World ! Is UIKit available on macOS project ? I use Firebase package in my project and I encounter this error : SwiftUIPreviewHelpers No such module 'UIKit' This is in the file FirebaseInAppMessaging import UIKit import FirebaseInAppMessaging @available(iOS 13.0, tvOS 13.0, *) @available(iOSApplicationExtension, unavailable) @available(tvOSApplicationExtension, unavailable) public enum InAppMessagingPreviewHelpers { public static func cardMessage(campaignName: String = "Card message campaign", title: String = "Title for modal message", body: String? = "Body for modal message", textColor: UIColor = UIColor.label, backgroundColor: UIColor = UIColor.black, portraitImage: UIImage = UIImage(systemName: "rectangle")!, landscapeImage: UIImage? = UIImage(systemName: "square"), primaryButtonText: String = "Click me!", primaryButtonTextColor: UIColor = UIColor.systemBlue, primaryButtonBackgroundColor: UIColor = UIColor.systemGray, primaryActionURL: URL? = nil, secondaryButtonText: String? = "Dismiss", secondaryButtonTextColor: UIColor? = UIColor.secondaryLabel, secondaryButtonBackgroundColor: UIColor? = UIColor.systemYellow, secondaryActionURL: URL? = nil, appData: [String: String]? = nil) -> Any solutions ? After update my Xcode to 15.0, my SwitUI views stoped to open on Preview Canvas It runs on Simulator, but I can't previews the UI. Can someone help or give some tips where should I look for? Everytime I launch Xcode now i'm getting this crash. I tried all version of XCode 15 and none are working. Only Xcode 14 opens properly. Process: Xcode [971] Path: /Applications/Xcode.app/Contents/MacOS/Xcode Identifier: com.apple.dt.Xcode Version: 15.0 (22265) Build Info: IDEApplication-22265000000000000~3 (15A240d) Code Type: ARM-64 (Native) Parent Process: launchd [1] User ID: 501 Date/Time: 2023-09-22 15:19:20.4158 -0400 OS Version: macOS 13.5.2 (22G91) Report Version: 12 Anonymous UUID: 552B0663-5A0A-7299-3393-EAB927768D4A Time Awake Since Boot: 120 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Termination Reason: Namespace SIGNAL, Code 6 Abort trap: 6 Terminating Process: Xcode [971] Application Specific Information: abort() called Application Specific Signatures: _mutableDirectExtensions != ((void *)0) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_kernel.dylib 0x1a88ec764 __pthread_kill + 8 1 libsystem_pthread.dylib 0x1a8923c28 pthread_kill + 288 2 libsystem_c.dylib 0x1a8831ae8 abort + 180 3 IDEKit 0x106f74d58 +[IDEAssertionHandler _handleAssertionWithLogString:assertionSignature:assertionReason:extraBacktrace:] + 972 4 IDEKit 0x106f75198 -[IDEAssertionHandler handleFailureInMethod:object:fileName:lineNumber:assertionSignature:messageFormat:arguments:] + 872 5 DVTFoundation 0x1028199a8 _DVTAssertionHandler + 424 6 DVTFoundation 0x102819b28 _DVTAssertionFailureHandler + 196 7 DVTFoundation 0x1028618d0 -[DVTExtensionPoint _registerExtension:] + 296 8 DVTFoundation 0x102685360 -[DVTExtension awakeFromPropertyList] + 176 9 DVTFoundation 0x1026c2530 -[DVTPlugIn awakeFromPropertyList] + 308 10 DVTFoundation 0x1027f85a4 -[DVTPlugInManager _createPlugInObjectsFromScanRecords:] + 340 11 DVTFoundation 0x1027f6a30 __52-[DVTPlugInManager _recordNonApplePlugInDescriptor:]_block_invoke + 92 12 DVTFoundation 0x1027f6ff8 -[DVTPlugInManager _allowNonApplePlugInsFromDescriptors:error:] + 304 13 DVTFoundation 0x1027f71e0 -[DVTPlugInManager _checkNonApplePlugIns] + 204 14 DVTFoundation 0x1027f72bc -[DVTPlugInManager initializePlugIns:] + 20 15 IDEFoundation 0x1088250c8 _IDEInitializeOtherPlugInStuff + 168 16 IDEFoundation 0x108827408 IDEInitialize + 4952 17 IDEKit 0x106f54620 -[IDEApplicationController applicationWillFinishLaunching:] + 484 18 CoreFoundation 0x1a89f7180 __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 148 19 CoreFoundation 0x1a8a92eec ___CFXRegistrationPost_block_invoke + 88 20 CoreFoundation 0x1a8a92e34 _CFXRegistrationPost + 440 21 CoreFoundation 0x1a89c84cc _CFXNotificationPost + 704 22 Foundation 0x1a99268e4 -[NSNotificationCenter postNotificationName:object:userInfo:] + 88 23 AppKit 0x1abc1b1bc -[NSApplication finishLaunching] + 248 24 DVTKit 0x1030dfe48 -[DVTApplication finishLaunching] + 196 25 AppKit 0x1abc1aea8 -[NSApplication run] + 252 26 DVTKit 0x1030dfcbc -[DVTApplication run] + 60 27 AppKit 0x1abbf23cc NSApplicationMain + 880 28 dyld 0x1a85cbf28 start + 2236 Thread 1: 0 libsystem_pthread.dylib 0x1a891ed8c start_wqthread + 0 Thread 2: 0 libsystem_pthread.dylib 0x1a891ed8c start_wqthread + 0 Thread 0 crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x00000001a89bd730 x5: 0x0000000000000065 x6: 0x0000000000002800 x7: 0x000000016da54f28 x8: 0x9ade123b8a873d80 x9: 0x9ade1239891d5d00 x10: 0x00006003f937b55f x11: 0x0000000000000007 x12: 0x0000000000000007 x13: 0x0000600002fd11e0 x14: 0x0100000203ec3191 x15: 0x0000000203ec3190 x16: 0x0000000000000148 x17: 0x00000002084cb3a0 x18: 0x0000000000000000 x19: 0x0000000000000006 x20: 0x00000002039a6080 x21: 0x0000000000000103 x22: 0x00000002039a6160 x23: 0x0000000000000000 x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x00006000016c40c0 x27: 0x00006000003c1a00 x28: 0x00000002039a79a0 fp: 0x000000016da55b30 lr: 0x00000001a8923c28 sp: 0x000000016da55b10 pc: 0x00000001a88ec764 cpsr: 0x40001000 far: 0x00000001538b4000 esr: 0x56000080 Address size fault Binary Images: 0x1023a8000 - 0x1023abfff com.apple.dt.Xcode (15.0) <6c185205-c752-3ce5-bea5-b4e74e423759> /Applications/Xcode.app/Contents/MacOS/Xcode 0x1034b4000 - 0x10394bfff com.apple.MIL (5.33) <2f2bbe88-0c7d-3006-88ac-7843837d9a63> /Applications/Xcode.app/Contents/SystemFrameworks/MIL.framework/Versions/A/MIL I have an app being deployed to QA ad hoc. All the builds have always been signed with the same provisioning profile under the same developer account. In the last two weeks, I built two different versions (e.g. 0.0.2 and 0.0.3). So, QA has been working with version 0.0.2 until last Wednesday when 0.0.3 was ready. The new build was signed in exactly the same way as before. However, on a test device with iOS 16.3.1, it did not start, showing the following message: (Note: Everything was OK with Internet connection there, as QA tried to run the app immediately after downloading it and also tried it dozens of times.) NB1: After the problem appeared, QA checked the previous version 0.0.2, and it still ran fine on the target device. However, the issue persisted when returning to 0.0.3. NB2: The app does not appear in Settings/General/VPN&Device management section, so there is no way to actually verify it NB3: The same IPA file runs on iOS 12 and 14 without any issues all the time. I would greatly appreciate it if somebody could clarify the reasons of such behaviour or at least point out how to avoid it in future. I just want to know witch one of these two options is preferable and why: HStack(spacing: 0, content: { HStack(spacing: 0) { Hello, I’m trying to allow my MacOS app written in swift to run a kill command. it works when I test it manually in my terminal but when I run it in the app I get an not permitted error. j was reading about work space authorization and put in a request but i got a response saying I didn’t need that type of authorization for what I’m doing. Any help pointing me in the right direction? https://developer.apple.com/documentation/appkit/nsworkspaceauthorizationtype Thanks! Hi we are developing a appattestation devicecheck feature . we would like to is there a limit on creating a DCAppAttestService.generateKey() ? what happens to the cryptographic key in the Secure Enclave that already created when we call the DCAppAttestService.generateKey() again . Does it overrides the old keypair OR does it create a new key always Hello! I have found a weird behavior change when running xcodebuild -create-xcframework in Xcode 15 compared to running it in Xcode 14.3.1. If I run the command like this in Xcode 15: xcodebuild -create-xcframework -framework "pathToFrameworkInATemporaryDirectory" -debug-symbols "pathToDebugSymbols" -output "Something.xcframework" I get this error: error: cannot compute path of binary 'Path(str: "temporaryPathToTheUnixExecutableFile")' relative to that of 'temporaryPathToTheFramework' But if I trace that path to the unix executable file in the framework, it is present. If I run that same command in Xcode 14.3.1, it works fine. I can create the xcframework successfully in Xcode 15 if I don't copy the framework to a temporary directory before calling xcodebuild -create-xcframework and I use that original path. Why is this problem happening now in Xcode 15? Any help is appreciated, thank you. I've gone through several tutorials, and the documentation, it seems there's no way to adjust the logging level dynamically, or even at build time for that matter. i.e. there is apparently nothing that exists such as: static let logger = Logger(subsystem: subsystem(), category: category()) logger.setMinimalLevel(.Warning) logger.trace("I won't get displayed because minimal level is debug") Am I mistaken and there is something like this? I've added a privacy manifest (via Xcode 15) in my iOS app and created a new release that was approved and published.. However, in App Store Connect my apps Privacy Nutrition Labels (General > App Privacy) have not been updated, nor have the privacy labels been updated in the actual App Store for my latest release. So my question is: Shouldn't have my app's App Store Connect privacy page and App Store privacy nutrition labels be automatically updated, per my latest release that included the new privacy manifest? I'm under the impression that they should have but maybe I'm mistaken; it would seem odd to still have to manually update privacy nutrition labels in App Store Connect when a privacy manifest was in the latest approved/published release. Thanks. Are there any updates for WKWebView on iOS 17? I see that Safari now has more privacy settings such as "Advanced tracking and Fingerprinting Protection", but does this apply to WKWebViews or just Safari? I'm assuming just Safari. Also, is there a way to detect the fingerprinting settings on Safari? Thank you. Hello, What is the key for In-App Purchases entitlement I can add to my app.entitlements file in my project, so that I can autonomously enable the In-App Purchase capability? I have searched far a wide for this, however, it's unclear where it can be located. I know I can enable this capability manually by opening Xcode -> Selecting the "Signing & Capabilities" tab -> selecting "+ Capability" -> selecting "In-App Purchase" capability. However, this is not really an ideal solution for adding the capability to my app, especially when automated processes for building, testing, distributing via CI/CD are integrated. It would beneficial to be able to reference some documentation or resources for enabling capabilities (or any other build settings) autonomously in a project as opposed to having to manually click my way through enabling them. Looking forward to hearing back. Thanks! Our company has 2 developer accounts, an old one and a new one that we are transitioning to. Until today when logged into the Developer website I could select which account I wanted to look at but now I only see the new one. The same is for Xcode, when I add my account it used to give me both the old and new and now it only gives me the new. If I log into Appstore Connect I can see both accounts as expected. The unfortunate part is I need to compile the App using the old account and cannot. Any help is appreciated.

Developer Footer

Forums

Apple Developer Program

Apple Developer Enterprise Program

App Store Small Business Program

MFi Program

News Partner Program

Video Partner Program

Security Bounty Program

Security Research Device Program

Terms of Use Privacy Policy License Agreements