# \#auth0-swift

**URL:** https://community.auth0.com/tag/auth0-swift/2087.md

[Latest](https://community.auth0.com/latest.md) · [Categories](https://community.auth0.com/categories.md) · [Tags](https://community.auth0.com/tags.md)

---

## [Universal Login for Auth0.swift doesn't work with the simulator?](https://community.auth0.com/t/universal-login-for-auth0-swift-doesnt-work-with-the-simulator/191745)

<div class="topic-metadata">

**Author:** [@wrightak](https://community.auth0.com/u/wrightak)\
**Replies:** 2\
**Last updated:** [December 9, 2025, 3:50pm UTC](https://community.auth0.com/t/universal-login-for-auth0-swift-doesnt-work-with-the-simulator/191745 "2025-12-09T15:50:47Z")

</div>

Given the changes, we followed the guidance in the Auth0.swift documentation to add associated domains, configure our team ID and bundle ID in the Auth0 dashboard, and add the useHttps() line to the swift code. The firs…

---

## [Can we use Authorization code with PKCE using Swift SDK only?](https://community.auth0.com/t/can-we-use-authorization-code-with-pkce-using-swift-sdk-only/183587)

<div class="topic-metadata">

**Author:** [@marehoplit](https://community.auth0.com/u/marehoplit)\
**Replies:** 3\
**Last updated:** [March 13, 2025, 4:19pm UTC](https://community.auth0.com/t/can-we-use-authorization-code-with-pkce-using-swift-sdk-only/183587 "2025-03-13T16:19:20Z")

</div>

I think I have read every possible document in Auth0 SDKs related to this and it seems it’s not possible. All SDK quickstart points to using webAuth() which uses SSO and gives me access-token without refresh token anywh…

---

## [Implementing PKCE with email password login for iOS](https://community.auth0.com/t/implementing-pkce-with-email-password-login-for-ios/124813)

<div class="topic-metadata">

**Author:** [@sayed](https://community.auth0.com/u/sayed)\
**Replies:** 2\
**Last updated:** [February 2, 2024, 8:31am UTC](https://community.auth0.com/t/implementing-pkce-with-email-password-login-for-ios/124813 "2024-02-02T08:31:05Z")

</div>

I am trying to implement PKCE for login with email and password. For that, I see this function codeExchange(withCode:codeVerifier:redirectURI:) but I don’t find any way to make this work with the login function I am curr…

---

## [New Xcode build error with Auth0](https://community.auth0.com/t/new-xcode-build-error-with-auth0/109265)

<div class="topic-metadata">

**Author:** [@isaac](https://community.auth0.com/u/isaac)\
**Replies:** 5\
**Last updated:** [June 15, 2023, 6:45pm UTC](https://community.auth0.com/t/new-xcode-build-error-with-auth0/109265 "2023-06-15T18:45:19Z")

</div>

Need a new release of auth0-swift. The underlying SimpleKeychain and JWTDecode packages now require macOS 11 or greater build target, but the current auth0-swift release requires 10.15, so will no longer build.

---

## [Access GO API Tutorial from SWIFT Tutorial](https://community.auth0.com/t/access-go-api-tutorial-from-swift-tutorial/106189)

<div class="topic-metadata">

**Author:** [@Packanimal](https://community.auth0.com/u/Packanimal)\
**Replies:** 1\
**Last updated:** [May 4, 2023, 7:00pm UTC](https://community.auth0.com/t/access-go-api-tutorial-from-swift-tutorial/106189 "2023-05-04T19:00:14Z")

</div>

Hi. I may be missing some trivial, however I’m failing to pinpoint it. VERY Similar thread, but not helpful My question is similar to this auth0 help thread. The user said they found their problem in their SPA’s config…

---

## [Swift SecureCredentialsManager token persistence](https://community.auth0.com/t/swift-securecredentialsmanager-token-persistence/99673)

<div class="topic-metadata">

**Author:** [@ryan.kramer](https://community.auth0.com/u/ryan.kramer)\
**Replies:** 4\
**Last updated:** [February 6, 2023, 4:45pm UTC](https://community.auth0.com/t/swift-securecredentialsmanager-token-persistence/99673 "2023-02-06T16:45:37Z")

</div>

Hello, we are seeing that an auth token, refresh-tokens saved with SecureCredentialsManager seem to be lost or expired once the device is turned off. To me it would seem they should be persisted through this case but may…
