I am interested in this too, but reviewing that page did not seem to offer a solution. Assuming I want the job title of the user sharing the app clip to appear in the subheading or a picture directly related to the shared content, is that possible without creating separate app clips for each and every permutation?

I think this might be an iOS 26 bug. Testing on iPadOS 18 does not exhibit the problem, and others testing on iOS 18 devices have not seen the issue. I have submitted a bug report via Feedback Assistant (FB19587057).

I have solved this problem. It seems that adding the Associated Domain credential inadvertently created a second entitlement file in a different location and the system was not properly resolving the entitlement. Once I deleted both entitlement files and started fresh, sign in worked properly.

I have an Apple TV 4K (3rd generation) and was able to generate a sysdiagnose, so thanks for that clarification. This document could probably use updating because it makes no such distinction between 3rd gen devices. Nevertheless, going through the swcutil_show.txt, ShinyTV is not listed among the SharedWebCredential apps. I have also tried with another app of mine with a different domain, both with validated AASA files using swcutil. If the AASA is set up correctly and in the right place, and the app has Associated Domain entitlements, what else could be preventing it from appearing in the swcutil_show.txt file?

Thanks for the suggestions. I have tried a few times streaming console data from my Apple TV, and the only items relevant to my password request are from the CompanionServices subsystem and AuthenticationServices. com.apple.swc does not show up for me. Testing with swcutil all came back positive that the file can be downloaded and that it can identify the webcredentials section, the app id, and the domain. I saw in the docs a suggestion to take a sysdiagnose but my 3rd gen doesn't support that, and tvOS shared login does not appear to work on the simulator.

Thanks for the thorough explanation!

Hi thanks for the reply; I think i wasn’t clear about what’s going on. I have a window with a RealityView in it. Currently that RealityView presents a Reality Composer scene. When I look at that window in the compiled app, the contents sit physically in front of the actual window, and moving them back in the scene has no effect at all. Since posting this, I have experimented with doing a findEntity in the scene and pulling out a Transform which parents a ModelEntity. Doing that allows me to manipulate the depth of the ModelEntity relative to that Transform. But it is surprising that I can’t do the same thing with the scene itself; I have to extract scene elements to adjust their depth.

Running Hello World in Xcode 15 beta 5 on a M1 Max still crashes and adding @ObervationIgnored just increases the errors. Ultimately I just refactored ViewModel to @ObservableObject and converted all instances to @ObservedObjects. It required a number of other tweaks too, but those were the primary changes.

Extending what has already been suggested, you can modify the predicate of the wrappedValue to dynamically trigger an update to a SwiftUI list. In the example below, toggling the isFiltered @State causes an update of the List and it reloads the FetchedResults with the filtered or unfiltered predicate. @FetchRequest private var items: FetchedResults<Item> @State var isFiltered = false let filteredPredicate: NSPredicate let unfilteredPredicate: NSPredicate init(element: Element) { self.element = element      filteredPredicate = NSPredicate(format: "element == %@ && score > 0.85", element) unfilteredPredicate = NSPredicate(format: "element == %@", element)      self._items = FetchRequest<Item>(entity: Item.entity(), sortDescriptors: [NSSortDescriptor(keyPath: \Item.name, ascending: true),           predicate: unfilteredPredicate,           animation: .default) } var listItems: FetchedResults<Moment> {      get {         _moments.wrappedValue.nsPredicate = isFiltered ? filteredPredicate : unfilteredPredicate           return moments      } } var body: some View {     List {        ForEach(Array(listItems.enumerated()), id: \.element) { index, item in Text(item.name) .toolbar {                ToolbarItem {                    Button {                        withAnimation {                           isFiltered.toggle()                        }                   } label: {                        Label("Filter Items", systemImage: isFiltered ? "star.circle.fill" : "star.circle")                   }                }           } } } }

For future viewers of this question, there is a more detailed description of the correlate method here: https://developer.apple.com/documentation/accelerate/vdsp/1d_correlation_and_convolution

Just tested Beta 6, same thing

Just tested Beta 3, same thing

I cannot speak to your difficulties. I have a pre-existing app that successfully uses the motion capture with iOS 13 and 14. In my test I ran the same app simultaneously on a device running iOS 15 beta and another running iOS 14.6. I recorded a video of each and compared them. Motion capture works on 13.5, 14, and 15, but the new precision of ARKit 5 is supposed to be limited to A14 chips

Thanks very much--the MDLTransform looks like just what I want! But the targetAlignment property is actually the problem: when using .any raycasts, most of the results you get back are .any targetAlignments which isn't particularly useful in my situation since I'm trying to distinguish between horizontal and vertical alignments.

One tricky bit I have discovered is that when working with an iPhone, the screen aspect ratio does not match the aspect ratio of the depth buffer, so translating from the buffer width to the screen position requires disregarding some of the buffer width on each side.