-
Notifications
You must be signed in to change notification settings - Fork 232
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
Swift 6 support #890
Comments
Hi @honus, By "Compiling in Swift 6 language mode", do you mean changing the Swift version for the Auth0.swift target, or just your app's target? Also, are you getting errors (compilation fails), or just warnings? |
App's target. Errors. |
Unfortunately my project isn't in a state where I can easily reproduce this issue right now. When I get a chance I'll try to get you more specific examples of problems. |
I just tried with the sample app (cleaning the cache beforehand) and was able to compile successfully: Screen.Recording.2025-01-16.at.16.00.13.mov |
Hi @papekoja, that doesn't seem to be a compiler error, but a trap instruction. |
@Widcket yes you're right, I formulated myself badly |
It compiles completely fine and this happens when the Swift language version is set to 6 |
@papekoja can you please post the stack trace (redacting things as needed)? |
There isn't any when this happens, unfortunately. The console is completely blank. I'm running Xcode 16.2 and Auth0 2.10.0 package version. |
Try cleaning Derived Data after switching to Swift 6. |
Checklist
Describe the problem you'd like to have solved
Compiling in Swift 6 language mode results in concurrency errors like problems with Sendability of Credentials as discussed in this forum issue from 2022 https://community.auth0.com/t/credentialsmanager-credentials-and-sendability/95271
Describe the ideal solution
The SDK should be updated to compile without errors when used in Swift 6.
Alternatives and current workarounds
Importing with
@preconcurrency
may be a workaround but could be hiding issues in concurrent code.Additional context
No response
The text was updated successfully, but these errors were encountered: