-
Notifications
You must be signed in to change notification settings - Fork 199
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Amplify.Auth
does not Sendable
conform, will this be solved until release of Swift 6?
#3828
Comments
Amplify.Auth
not Sendable
conform, will this be solved until release of Swift 6?Amplify.Auth
does not Sendable
conform, will this be solved until release of Swift 6?
Thanks for raising the concern. Our team will look into prioritizing this request. |
This has been identified as a feature request. If this feature is important to you, we strongly encourage you to give a 👍 reaction on the request. This helps us prioritize new features most important to you. Thank you! |
|
Hi @MMise , |
Is there any update on this issue? @5d did you enable the Swift 6 warnings? :) |
@5d I am using Xcode 15.3 with |
Thank you for your patience - our team will take a look and post updates here. |
Describe the bug
Regarding using
Amplify.Auth
in SwiftUI with Swift 5.10, there will be warnings over all the place because some of the Auth's classes, protocols, etc. are not actor'ized.This will lead to compilation errors in Swift 6 but currently there will be a lot of warnings that may break CI checks for warning threshold.
If this can be solved in the client app, please let me know.
Steps To Reproduce
Expected behavior
Amplify.Auth works fine with SwiftUI, actors
Amplify Framework Version
2.36.0
Amplify Categories
Auth
Dependency manager
Swift PM
Swift version
5.10
CLI version
not installed - iOS only
Xcode version
Version 15.4 (15F31d)
Relevant log output
Is this a regression?
No
Regression additional context
No response
Platforms
iOS
OS Version
iOS 17
Device
all
Specific to simulators
no
Additional context
No response
The text was updated successfully, but these errors were encountered: