PS: If I change enum HTTPMethod<Payload> {     case get     case post(Payload)     case patch(Payload) } to enum HTTPMethod<Payload> {     case get(Payload)     case post(Payload)     case patch(Payload) } the problem also goes away. Filed a bug report using the Feedback Assistent, there shouldn't be reason why the .get case has an associated value.

PS: If we remove one of the fields from Resource , say delete the authToken field, the method will no longer crash. I believe that would reduce the size of the struct Resource to where the init method would no longer be outlined

So, now that we have an iPad 5th Generation with the 12MP camera I can see the problem more clearly. Basically, what we'd need is for the ARSCNView to also have the center stage function that Apple offers in FaceTime. The full wide-angle-camera image is too big.

Turns out homebrew seems to have spammed hundreds of lines eval "$(/opt/homebrew/bin/brew shellenv)" into my ~/.zprofile which I didn't even know existed.

We're seeing the same issue in all our WebGL applications. It definitely worked in April 2021, since then without changing any code the Safari performance went from 60fps to 2fps. Example scene built in unity (with a camera-texture since camera input is important for our AR applications): https://test.looc.io/forest/index.html

Seeing the same issue here. Our test scene used to render at 60fps back in April 2021, now without changing any code it's at 2FPS and my whole Macbook Air freezes. Test scene: https://test.looc.io/forest/index.html

So it seems just putting the line token preliminary:anchoring:type = "face" in was not enough. What worked was writing a python script, importing the from pxr import Usd, Sdf, UsdGeom, Kind stuff and then creating a scene hierarchy with /Root/Scenes/Scene/Children/MyModel where the scene gets the anchor-token. The USD Classes reference (https://graphics.pixar.com/usd/docs/api/class_usd_stage.html) helped a little but It was way more complicated then I expected it to be.

Mhm, so I thought according to the Swift package Manager Team an Xcode project is not necessary to build an xcframework based on a Swift Package. - https://github.com/apple/swift-package-manager/pull/2981#issuecomment-710282803. boris is also referencing the same demo example he did in the WWDC video Distribute binary frameworks as Swift packages - https://developer.apple.com/videos/play/wwdc2020/10147/ from 2020, so I thought this is the latest status compared to the video Binary Frameworks in Swift from 2019. As a swift package, my project automatically gets an extension that provides the Bundle.module extension, e.g. swift let string = NSLocalizedString(self, tableName: nil, bundle: .module, value: "", comment: "") which is no longer available if I wrap the code into an xcodeproj. I thought based on the above mentioned github issue, the xcodeproj way is no longer necessary.

If I comment out the .binaryTarget and only use the .target(name:) the bash output is ARCHIVE SUCCEEDED [58.086 sec] but then if I look into the archived file, it has no *.framework inside it.