Apple docs for RealityView state: You can also use the optional update closure on your RealityView to update your RealityKit content in response to changes in your view’s state." Unfortunately, I've not been able to get this to work. All of my 3D content is programmatically generated - I'm not using any external 3D modeling tools. I have an object that conforms to @ObservableObject. Its @Published variables define the size of a programmatically created Entity. Using the initializer values of these @Published variables, the 1st rendering of the RealityView { content in } works like a charm. Basic structure is this: var body: some View { RealityView { content in // create original 3D content using initial values of @Published variables - works perfect } update: { content in // modify 3D content in response to changes of @Published variables - never works } Debug statements show that the update: closure gets called as expected - based upon changes in the viewModel's @Published variables. However, the 3D content never changes - even though the 3D content is based upon the @Published variables. Obviously, if the @Published variables are used in the 1st rendering, and the update: closure is called whenever changes occur to these @Published variables, then why isn't the update: closure updating the RealityKit content as described in the Apple docs? I've tried everything I can think of - including removing all objects in the update: closure and replacing them with the same call that populated them in the 1st rendering. Debug statements show that the new @Published values are correct as expected when the update: closure is called, but the RealityView never changes. Known limitation of the beta? Programmer error? Thoughts?

None of my existing apps (both in-AppStore and in-development) nor even a brand new WatchOS app can be installed to my Apple Watch. While using Xcode to build and deploy to my Watch, I get this: ”Waiting to reconnect to Apple Watch Xcode will continue when the operation completes.” However, this dialog persists and never completes. I’m running all of the latest: MacOS 14 beta 4, Xcode 15 beta 5, Watch OS 10 beta 4, iOS 17 beta 4. I’ve tried resetting my Watch (with “Erase All” option) and restarting the Mac, the phone and the watch. Any help?

Xcode Version 16.1 beta 3 (16B5029d) -- Watch Series 9 Version 11.1 (22R5569a) -- iPhone 16 Pro Version 18.1 (22B5069a) The current WatchOS version has introduced a UI bug in NavigationView.navigationTitle - and I'm attempting to install a new version of my App on my Watch. This watch was previously sync'd with an iPhone 13 Pro - which is no longer associated with my AppleID since I'm using my new iPhone 16 Pro. The watch is paired with the 16 Pro, and in previous versions of Xcode 16.1, I was able to compile and run my all of my apps on the Watch. In the current beta 3, instead I get a dialog box which states: Connecting to Apple Watch Xcode will continue when the operation completes. and this dialog box persists until the timeout (which is several minutes). Any help?

Developing along, no problems - and then suddenly: Failed to verify code signature of /var/installd/Library/Caches/com.apple.mobile.installd.staging/temp.G47wHn/extracted/Payload/Dvn8.app : 0xe8008001 (An unknown error has occurred.) Verify that the Developer App certificate for your account is trusted on your device. Open Settings on the device and navigate to General -> VPN & Device Management, then select your Developer App certificate to trust it. —> On my Mac, there is no /var/installd directory. —> On my device, there is no Developer App certificate in Settings -> General -> VPN & Device Management. I have verified on developer.apple.com under Certificates, Identifiers & Profiles that my device‘s Device ID (UUID) as listed. I have NO problem building & installing this app to my iPad, nor any problems installing other of my apps to this iPhone - it’s just this app on the phone that’s messed up. I’ve restarted everything multiple times. I’ve cleared out both /Users/me/Library/Developer/Xcode/DerivedData/ as well as /Users/me/Library/MobileDevice/Provisioning Profiles/ I’ve turned off & back on Settings -> Privacy & Security -> Developer Mode using macOS Version 14.0 (Build 23A5337a) Xcode 15.0 (22005) (Build 15A5229m) Please help! I’m 100% blocked from releasing a new version of our app, which is 100% ready to upload!

I’ve let the System Settings‘ Sofware Updates run overnight twice - and all I get is the cylon blue shifting left to right… I’ve restarted my M1 MBAir several times. I’ve attempted to download it directly from developer.apple.com - but it just stops (Zero KB of 15.87 GB) - with no further clarification. Any ideas?

Somehow, I am no longer able to connect to the AppStore in my development build. On a different device, I am running a production build (downloaded from the AppStore) and it works fine. In Xcode console, for the dev build, I get the following: Error enumerating all current transactions: Error Domain=ASDErrorDomain Code=509 "No active account" UserInfo={NSLocalizedDescription=No active account} It's been several months since I've worked on this particular project, and I can't recall what I did to enable the sandbox in the first place. ¯_(ツ)_/¯ Notwithstanding, on each device, I have gone into Settings -> App Store -> Sandbox Account and selected "Sign Out". Within Xcode, there is no Sandbox entry in any Entitlement file that I can find. Under Product -> Scheme -> Edit Scheme -> Run (Debug) -> Options, the StoreKit Configuration is set to None. In addition, 2 years ago Eskimo posted the following command that supposedly identifies if a build is Sandbox-enabled: codesign -d --entitlements - --xml /Applications/PCalc.app | plutil -convert xml1 -o - - I ran this command on my .app - and there was no hint of a sandbox entitlement. And finally, I suspect my "No active account" error is related to Xcode's sandbox feature because, when I tap on my app's Restore Purchases link, I am presented with an os-level dialog box "Sign in with Apple ID". If I do that, then the Settings -> App Store -> Sandbox Account gets filled in... I'm at a loss. Any help will be appreciated.

Using this command line incantation: AppClipCodeGenerator generate -u https://myapp.app/clip -i 9 -o ~/Desktop/appClip.svg everything works as expected. However, using this one: AppClipCodeGenerator generate -u https://myapp.app/clip?p=1 -i 9 -o ~/Desktop/appClip.svg ie, just trying to pass in 1 parameter via "?p=1", it fails with no matches found: https://myapp.app/clip?p=1 In my case, clip is a Servlet which expects the parameter named p. Any ideas?

Simply going to Settings -> Music causes the Settings app to freeze. Also, I can no longer sync music from my Mac to my iPhone - it never shows the "Sync" button. And, if that's not ugly enough all by itself - none of the music that's already loaded on my phone responds to the Play button within Music. Using iOS 17.0 beta 7 (21A5319a)

I’ve been working with Localizable, and I’m loving it. Unfortunately, upon upgrading to beta 7 this morning, it no longer works on my dev iPhone: Unable to load .strings file: CFBundle 0x281350380 </private/var/containers/Bundle/Application/743432E9-60F9-4C2D-BA6C-4FF79D4EB467/Dvn8.app> (executable, loaded) / Localizable: Error Domain=NSCocoaErrorDomain Code=3840 "Unexpected character b at line 1" UserInfo={NSDebugDescription=Unexpected character b at line 1, kCFPropertyListOldStyleParsingError=Error Domain=NSCocoaErrorDomain Code=3840 "Conversion of string failed." UserInfo={NSDebugDescription=Conversion of string failed.}} I’ve investigated this ‘unexpected character b’ - and cannot figure out what this message is talking about. What I see on the screen is the key, instead of the localized string. Using Xcode 15.0 beta 7 (15A5229h) and iOS 17.0 beta 7 (21A5319a) What makes this completely befuddling is that the Localizable DOES still work on my M1 iPad (also running today’s iPadOS 17 beta 7 - as well as on my older 2015 iPad running iOS 16 - and even on my iPhone 7 running iOS 15. Same exact target, different devices. iPhone running 17 beta 7 fails, all others still work. I’ve tried powering down everything, remove / reinstall, etc. Nothing works.

I built a quick WatchOS app that uses an @Model to populate a List within a NavigationSplitView. After several minutes, the List displays the data which is in my CloudKit database - so far so good. Unfortunately, when I attempt to tap on any of the List items, the detail view is never displayed. Here is the ContentView: import SwiftUI import SwiftData struct ContentView: View { @Query(sort: \Squats.date, order: .reverse) var exercises: [Squats] @Environment(\.modelContext) var modelContext @State var selectedExercise: Squats? = nil var body: some View { if exercises.count == 0 { Text("CloudKit not yet loaded") } else { NavigationSplitView { List (exercises, selection: $selectedExercise) { ex in Text(ex.date.format("E, MM/dd")) } } detail: { Text(selectedExercise?.exercise ?? "Nothing set") } .padding() } } } And here is the model view: import Foundation import SwiftData @Model class Squats { var date: Date = Date() var exercise: String = "" init(date: Date, exercise: String) { self.date = date self.exercise = exercise } } I’ve tried this on a number of my in-production DBs, as well as this development-only “Squats” DB - same lack of detail view on all. Thoughts?

I have a .stl in “Standard Tesselated Geometry File Format” - how do I get this into a format which VisionOS can use? Notes: double-clicking on the .stl launches Xcode and shows the Scene graph I’ve added it to a template VisionOS app. It comes in with a gray icon that is otherwise identical to the blue icon that the template creates (named “Scene”) - but I cannot figure out how to get the model contained in the .stl to be recognized. Reality Composer Pro will not open the .stl file Many thanks!

According to AppStoreConnect, one of my apps is benchmarking above the 75% percentile for crashes - at 1.89%. Using Xcode’s Organizer window, I’m able to see that 98% of them are identified as: SwiftUI: EnvironmentObject.error() + 236 Cntl-Click / Show in Finder / Cntl-Click / Show Package Contents / Logs reveals the following: Termination Reason: SIGNAL 5 Trace/BPT trap: 5 Terminating Process: exc handler [5454] …and in some of the crash logs, I find this: Kernel Triage: VM - (arg = 0x0) pmap_enter retried due to resource shortage VM - (arg = 0x0) pmap_enter retried due to resource shortage What is the graceful way to handle a “resource shortage” when the crash logs show that the error occurs immediately upon app launch - ie, while still declaring .environmentObject()s upon the main ContentView()? Any help?

I’m getting this very weird error (send this bug to NSUKVS) when trying to get data from my app into both a lock-screen widget and an Apple Watch app. Most documentation and online tutorials suggest using App Groups and UserDefaults(suiteName:). I have implemented this and can write to and read from my iOS app to UserDefaults(suiteName:) - no problem. However, despite the fact that the UserDefaults(suiteName:) is found on both the lock-screen widget and the Apple Watch app - there is never any data found within. One month ago, Eskimo posted (https://developer.apple.com/forums/thread/710966) that the UserDefaults won’t work in modern devices because the WatchOS app won’t run in an extension on the phone, so we need to use another device-to-device mechanism. OK, so hoping that one solution will work for both targets, I built a tiny app that intends to implement NSUbiquitousKeyValueStore. (Please note that I have added the iCloud Key-value storage entitlement to the app target.) Import SwiftUI struct ContentView: View { var uks = NSUbiquitousKeyValueStore() var body: some View { Text(readData()).onAppear { writeData() } } func writeData() { uks.set("Hello", forKey:"name") uks.synchronize() } func readData() -> String { return uks.string(forKey:"name") ?? "n/a" } } Unfortunately, I’m getting this: 2022-09-18 17:40:32.538800-0500 Widget[5717:1877533] [Connection] Error synchronizing with cloud for store <(DevID.BundleID.AppName)>: Error Domain=SyncedDefaults Code=101010 "Tried to access unknown store DevID.BundleID.AppName" UserInfo={NSLocalizedDescription=Tried to access unknown store DevID.BundleID.AppName} 2022-09-18 17:57:58.655802-0500 Widget[5727:1883819] [Connection] BUG IN KVS: Tried to access store that is unknown to the system (DevID.BundleID.AppName). Please send this bug to NSUbiquitousKeyValueStore. Which begs the question: just how, exactly, does one “send a bug to NSUbiquitousKeyValueStore”??? 🤣 Is this possibly a problem with my AppleID? I ask because I’m getting really weird different results from my app which is currently in the App Store - depending upon if I’ve downloaded my app from Xcode or if I’ve downloaded it from the AppStore. Just wondering if my AppleID has somehow gotten into a corrupted state because of my Promo code (StoreKit) testing… Any and all ideas / suggestions welcomed…

One of my intents responds to an optional parameter. The parameter is defined as an enum with 4 values (case today, week, month, year). I have 2 AppShortcut phrases defined, one that does not specify the parameter and another which does. AppShortcut(intent: TopCardsIntent(), phrases: [ "show \(.applicationName) top cards", "show \(.applicationName) top cards for \(\.$timeframe)", ], systemImageName: "atom" ) The 1st phrase (with no $timeframe) ALWAYS is interpreted by Siri as a Safari lookup. The 2nd phrase ALWAYS works, but only when I don't specify timeframes '.today' or '.year'. When I do specify '.today' or '.year' - I again always get a Safari lookup. I've tried all sorts of goofy debugging. Thinking maybe it's because '.today' is 1st and '.year' is the last enum value defined, I added a .decade value. So, the '.decade' works perfect, but '.year' still doesn't. #RandomAF There are lots of AppShortcut phrases which I'm trying to use that always result in Safari lookups. It almost feels as if Safari has it's own set of AppShortcut phrases, and these are evaluated before mine. Any ideas?

I've been running OpenJDK & Apache Tomcat on my M1 MBAir - but with Ventura 13.3 I can't any longer... % java --version A fatal error has been detected by the Java Runtime Environment: SIGBUS (0xa) at pc=0x00000001038e6f38, pid=1446, tid=8707 JRE version: (19.0.2) (build ) Java VM: OpenJDK 64-Bit Server VM (19.0.2, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, bsd-aarch64) Problematic frame: V [libjvm.dylib+0x3baf38] CodeHeap::allocate(unsigned long)+0x1c0 No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again I've tried brew uninstall openjdk, reboots, brew install java, reboots, etc... nothing. Any thoughts?