I don't have a lot of experience with Swift 6 yet, and I couldn't figure out how to make the error go away while still keeping the method asynchronous.
Comments
Log in with your Bluesky account to leave a comment
I ended up using that as well! I appreciate the quick response
I’m currently working with RealityKit as a 3D renderer on mobile and it’s rather odd that MeshResource.Contets isn’t conforming when most of RealityKit is made to work async with swift 6 support
Maybe MeshResource.Contents was overlooked in the Swift 6 transition and the set of external developer using MeshResource.Contents and adopting Swift 6 last summer and who would actually report the issue as feedback was small.
Comments
Perhaps Apple will update this next month in Xcode 17.
@preconcurrency import RealityKit
although that's a little unsettling
The updated version of the Gist should no longer generate any errors, but unfortunately is not async.
I’m currently working with RealityKit as a 3D renderer on mobile and it’s rather odd that MeshResource.Contets isn’t conforming when most of RealityKit is made to work async with swift 6 support
Maybe MeshResource.Contents was overlooked in the Swift 6 transition and the set of external developer using MeshResource.Contents and adopting Swift 6 last summer and who would actually report the issue as feedback was small.