Alex Nachbaur

I'm encountering the same problem. Two different workflows run in parallel (unit tests and UI tests) and the results of one get overwritten by the other. It also seems interesting...

Thank you for reporting this. @jaynewstrom-okta could you take a look at this when you have a chance?

Hi @andersonvom, I'll take a look at this soon. Before I do, I wanted to double check that you cleaned out your Pods folder, and maybe your node_modules? I've seen...

Thank you for reaching out @ValentinOUI. The SDK uses the supplied discovery URL to retrieve the OIDC configuration for your authorization server before initiating login. You can validate settings are...

The React Native SDK itself doesn't support authentication in this way. Perhaps this might be better served to be filed against https://github.com/okta/okta-auth-js

We are still working on the plan to integrate the new SDKs but we are working on prioritization. Please continue to comment on this issue. We are referring to it...

Thanks for mentioning me @arvindkrishnakumar-okta. I'll keep an eye on the other issue to see what the response is, to help narrow then problem down.

For the Swift samples, is it using the new code in the [SwiftUI-Improvements branch](https://github.com/okta/okta-idx-swift/compare/master...SwiftUI-Improvements)?

The SDK already has the support for customizing the URLSession used for authentication. For example, you can supply your own [URLSession when creating an OAuth2Client](https://okta.github.io/okta-mobile-swift/development/authfoundation/documentation/authfoundation/oauth2client/init(baseurl:clientid:scopes:authentication:session:)), which can be used when...

Yes, those all sound like sensible use-cases and are things I had planned for. The SDK utilizes the APIClient protocol (with its default implementations) which is backed by a URLSession....