I did notice that RealityKit defines MeshResource.Contents as not conforming to Sendable, though. Maybe that's the core issue. Perhaps Apple will update this next month in Xcode 17. - ThreadSky

About ThreadSky

drewolbrich.bsky.social • 21 days ago

I did notice that RealityKit defines MeshResource.Contents as not conforming to Sendable, though. Maybe that's the core issue.

Perhaps Apple will update this next month in Xcode 17.

Comments

drewolbrich.bsky.social•21 days ago

One workaround is to change the import statement at the top of the file to

@preconcurrency import RealityKit

although that's a little unsettling

drewolbrich.bsky.social•21 days ago

Meanwhile, I've revised https://gist.github.com/drewolbrich/82b6036f9f11a71585fc53b7e3b3f41a to use MeshResource.generate(from:) instead, which is synchronous.

The updated version of the Gist should no longer generate any errors, but unfortunately is not async.

moudiz.bsky.social•17 days ago

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

drewolbrich.bsky.social•17 days ago

That's great to hear.

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.

Posting Rules

Be respectful to others
No spam or self-promotion
Stay on topic
Follow Bluesky's terms of service

Comments

Posting Rules

Reply