Update: You cannot use MainActor.assumeIsolated because the render graph, which uses the com.apple.SwiftUI.AsyncRenderer queue, can operate off the main thread.

Love seeing so much interaction in the Swift Forums! I'm going to summarize the discussion: Potential Workarounds: Add @preconcurrency to the Equatable Protocol: One potential solution discussed is adding @preconcurrency to the Equatable protocol. This would suggest that we are confident Apple will improve this in the future. However, this information hasn’t been officially communicated in the forums. @DTS Engineer isn't it? Using MainActor.assumeIsolated: Another approach mentioned is using MainActor.assumeIsolated as described in Swift documentation . This works under the assumption that Equatable will only be used from the MainActor. While this might work in some cases, it could lead to issues such as the program stopping if the assumption is incorrect. It seems like a good solution but not ideal practice, even, in this case won't stop the program. Additionally, some forum members pointed out that using the Equatable protocol with views might not be possible. There is also a feature request (FB15753655) proposing the creation of a custom Equatable protocol specifically for views that use @MainActor

Ensure that Swift Concurrency is marked in the build settings @Claude31

@Frameworks Engineer this means that those apps are breaking sandboxing? Is there any way to open the app without using private apis?

One day after report it through the Appstore, size was fixed and now it is correct.

@eskimo could be that App Store is not counting safari extensions or some resources like fonts or others in the app size?

Sill happen in iOS 18.

@sha921

@eskimo @meaton, please redeploy to include the endpoint.

It's only a reference for filling nutrition labels when you update/upload the app inside the App Store Connect. But It will be great @eskimo @meaton if we can include the nutrition labels inside our app with a predefined format. I mean for enforcing privacy user knowledge. We are a privacy-first Company and I know more people want to include the info also in their web and app, we want to clarify these aspects, and using something corroborated by Apple, makes users trust in.

Thanks for your reply @sha921, but it is not what I'm looking for. The openURLAction is for open urls programmatically vs what I'm looking that it's someone runs a scheme or a Dee-link and you can manage it.

any information about it @eskimo ?

@eskimo @meaton if you have any knowledge about the question, feel free to post it.

No updates

Yas, it's not possible using swiftUI, try with UIKit.