build disappears

Hello, did you ever find a resolution to this? I am building an Apple Watch App and I am also having an issue with background refreshes not being delivered. It can work fine for hours and then just completely stall during charging or entering low power mode and then it never recovers and I have to restart the watch to get it to continue giving me background refreshes.

FB20653170: Autofill command still in Edit menu after using [builder removeMenuForIdentifier:UIMenuAutoFill]; in AppDelegate Nobody needs credit cards, contacts, or passwords in my app. They do want scan text, and I’d replace Autofill with Scan Text if I could. But I can’t so I want to get rid of something nobody will ever use. Here is my appDelegate method: (void)buildMenuWithBuilder:(id)builder { [super buildMenuWithBuilder:builder]; if (builder.system != UIMenuSystem.mainSystem) { return; } NSLog(@Building menu for %@, builder.system);//it's building just checking [builder removeMenuForIdentifier:UIMenuAutoFill]; } I would expect if the option is there along with all the other menu identifiers, that one could remove the menu. But nope, there it is.

Hi, I am trying to load files from the Apple Vision Pro's storage into a Unity App (using Apple visionOS XR Plugin and not PolySpatial package). So, my immediate question here is what your larger goal here actually is? visionOS generally uses the same file access model as iOS, which means apps get access to files through one of two broad mechanisms: The files are added to one of the app’s container directories. There are many different APIs that use the broad flow, but the simplest case is having your app appear in File.app so that the user can directly add files. Basic access can be enabled by setting UIFileSharingEnabled and (possibly) LSSupportsOpeningDocumentsInPlace. The app uses an API like UIDocumentPickerViewController to allow the user to give their app access to specific files or directories. Finally, apps that are built around documents generally use the approach described in Building a document browser-based app, which actually provides a unified interface for both of the two approaches a

@EduardoDominguez If I understand correctly, you're noting that Foundation Models is able to see the structure of your generable type, and you are asking if this means that guides are redundant. Our general advice is this: First, create your @Generable type with just descriptive property names, and see what kinds of values are created. Then, in areas where the model isn't consistently generating relevant data, try adding @Guide to provide additional guidance to the model for generating those values. With on-device models, reducing complexity and keeping the context window small with succinct instructions is generally preferably, but through experimentation you may find that property-specific guides lead to more consistent results. Remember, building with large language models is all about testing and iterating! Best, -J

Ok, I think I got it to work. I think I was using the wrong build scheme. It appears to work when selecting the test scheme in xcode before running the tests. I think previously xcode would automatically switch schemes, or at least a prompt would appear asking if I wanted to switch schemes, I could be wrong, though. Thanks.

Hi @thanhnd24 Yes, to use the entitlement (in your case, main camera access), you need to include both the entitlement and a corresponding license file in your app. After Apple approves your app for one or more entitlements, you receive a license file, along with additional instructions. Developers enrolled in the Apple Developer Program as an individual or sole proprietor/single-person business do not meet the requirements for Enterprise APIs. To meet the requirements for Enterprise APIs, you need to be enrolled in the Apple Developer Program as an organization or enrolled in the Apple Developer Enterprise Program. For more information on obtaining and configuring the license, see Building spatial experiences for business apps with enterprise APIs for visionOS. Refer to Accessing the main camera for more information on using the main camera API.

Hi Kevin, Thank you for the suggestions. We have conducted a test of your third proposal regarding the IOKit User Client Class Temporary Exception. Our test procedure was as follows: We started from a known-good baseline commit where our DEXT loads correctly and the/dev/diskX node appears (though it reports 0 bytes, which is a separate issue we are debugging). We made only one change: we updated our App's .entitlements file to include the temporary exception. For absolute clarity, the exact content of the .entitlements file used for this test was: com.apple.security.temporary-exception.iokit-user-client-class IOUserUserClient com.apple.security.app-sandbox com.apple.developer.system-extension.install After a full clean, build, and reboot, the IOServiceGetMatchingService(DriverKitAcxxx) call still fails at runtime, returning IO_OBJECT_NULL. This result seems to indicate that the temporary exception entitlement is not sufficient to grant our app visibility of the active IOKit service on macOS. Be

Check if you have this flag: _SQLITE3_H_=1 under Build Settings > Preprocessor Macros (GCC_PREPROCESSOR_DEFINITIONS). I had this value and this resulted in your same error. I still need to find why I had this in the first place. But at least removing it resulted in the project building correctly and I can continue testing it using the new Xcode.