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

Issues with macOS Sequoia in 'Release' mode #128

Open
Joebayld opened this issue Nov 6, 2024 · 4 comments
Open

Issues with macOS Sequoia in 'Release' mode #128

Joebayld opened this issue Nov 6, 2024 · 4 comments

Comments

@Joebayld
Copy link

Joebayld commented Nov 6, 2024

I have an app that reads / writes RS256 JWTs. What I'm noticing is when my app is compiled in 'Release' mode, it fails to decode JWTs. The error thrown is JWTError.failedVerification. But if I run the same app in Debug mode it's fine.

This used to work fine pre macOS 15.

Did something change?

@spk-ynoda
Copy link

I also have the same problem.
I tried changing the build settings but it didn't solve the problem.

@Joebayld
Copy link
Author

I found the issue. It's in BlueRSA. We need this to get merged but not sure anyone maintains it anymore.

Kitura/BlueRSA#83

@dannys42
Copy link
Contributor

dannys42 commented Nov 14, 2024

Thanks all identifying the issue and submitting a bug fix. Swift-JWT 4.0.2 and BlueRSA 1.0.202 are pushed to SPM, hopefully addressing this issue. Please try it out and update here with the status.

Hopefully SPM works for you as I can't really maintain cocoapods anymore.

@numandev1
Copy link

Screenshot 2024-12-07 at 6 17 44 PM
Error: symbols referenced by indirect symbol table entries that can't be stripped in: /Users/runner/Library/Developer/Xcode/DerivedData/Ninja-gzlzbuqxevqmysgvnbspvebnzntb/Build/Intermediates.noindex/ArchiveIntermediates/Ninja-Staging/InstallationBuildProductsLocation/Applications/Ninja-Staging.app/Ninja-Staging
_$s***CryptorECC11ECPublicKeyC3derAC***Foundation4DataV_tKcfc
_$s***CryptorECC11ECPublicKeyC3keyACSS_tKcfC
** ARCHIVE FAILED **

I get this error. What could be the issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants