Skip to content
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

What is the correct way to work with CredentialsManager in Swift Concurrency? #864

Closed
6 tasks done
theolampert opened this issue Jul 22, 2024 · 2 comments
Closed
6 tasks done
Labels
bug This points to a verified bug in the code

Comments

@theolampert
Copy link

theolampert commented Jul 22, 2024

Checklist

Description

The only information I can find on this is a forum post from 2 years ago in which we're directed to Github, but the option to ask a question here redirects us back to the forum so I'm opening it here as a bug https://community.auth0.com/t/credentialsmanager-credentials-and-sendability/95271

Simply initialising CredentialsManager causes strict concurrency checking to surface a warning that this code will no longer compile in Swift 6. What's the recommended way to work with CredentialsManager with strict concurrency checking enabled or in Swift 6?

Reproduction

Initialise CredentialsManager

Additional context

No response

Auth0.swift version

2.8.0

Platform

iOS

Platform version(s)

16.0

Xcode version

15.4

Package manager

Swift Package Manager

@theolampert theolampert added the bug This points to a verified bug in the code label Jul 22, 2024
@Vaidios
Copy link

Vaidios commented Sep 6, 2024

I opted to defining this import as @preconcurrency, until it will fully support swift 6. It seems like concurrent safe access is also handled using GCD inside the library

@theolampert
Copy link
Author

I opted to defining this import as @preconcurrency, until it will fully support swift 6. It seems like concurrent safe access is also handled using GCD inside the library

Thanks, I've found using @preconcurrency to be somewhat buggy in the latest betas but I'll give it another look.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug This points to a verified bug in the code
Projects
None yet
Development

No branches or pull requests

2 participants