Here's some simple sample code which produces warnings (or errors if using Swift 6 language mode), annotated with the errors:
struct MyEffect: GeometryEffect {
var animatableData: CGFloat // ERROR: Main actor-isolated property 'animatableData' cannot be used to satisfy nonisolated protocol requirement
func effectValue(size: CGSize) -> ProjectionTransform { // ERROR: Main actor-isolated instance method 'effectValue(size:)' cannot be used to satisfy nonisolated protocol requirement
ProjectionTransform(.identity)
}
}
I run into the same issue with Shape:
private struct MyShape: Shape {
var foo: UnitPoint = .zero
var animatableData: CGPoint.AnimatableData = .zero // ERROR: Main actor-isolated property 'animatableData' cannot be used to satisfy nonisolated protocol requirement
func path(in rect: CGRect) -> Path {
print(foo) // ERROR: Main actor-isolated property 'foo' can not be referenced from a non-isolated context
return Path()
}
}
It seems that by conforming to these protocols (which share Animatable conformance), all properties within the struct become annotated with @MainActor. Is this a bug?
jbutton
Users receive reputation points by contributing quality content to the forums.
Posts include post and replies published on the forums.
Post authors can mark replies as Accepted to indicate successful solutions.
Apple Developer Forums admins can mark replies as Apple Recommended to indicate an approved solution
Last seen
User for