Manually link JWTDecode and SimpleKeychain

[hoolrory]

possible fix for us not using Carthage

• All new/changed/fixed functionality is covered by tests (or N/A)
• I have added documentation for all new/changed functionality (or N/A)

📋 Changes

📎 References

🎯 Testing

[1419krusty]

should we push this to https://github.com/auth0/Auth0.swift instead of forking?

[Kevin-J-Harrison]

Is this related to the thing they are actively working on here auth0#870

[hoolrory]

@Kevin-J-Harrison doesn't look like the same thing. As far as I could tell our issue was that the dependency of Auth0 on JWTDecode only implicit in our build order, not explicit, so it was a race condition whether or not JWTDecode would be done building before Auth0 started

[hoolrory]

@1419krusty We could try, it seems to go against their preferred Carthage/Swift way of dependency management so I doubt they'd be too excited, and we'd probably have to make sure the iOS, tvOS, visionOS, watchOS targets worked with the same change.

[LGriffioen]

weird that they didn't do this. seems like a lot of apps would have this problem. should we open a PR against the main repo?

[hoolrory]

I've made a feature request and a PR in the Auth0.swift repo:
auth0#872
auth0#873

[Kevin-J-Harrison]

Nice!

Just for my curiosity, is there a reason we aren't using the swift package?

[LGriffioen]

yes, AppStore build configurations break swift packages because SPM expects debug or release only