-
Notifications
You must be signed in to change notification settings - Fork 104
Fix the InvalidSignature issues on RNQuickCrypto #2123
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
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
56df6bf to
211b129
Compare
|
@gdorsi I rebased, added a commit that makes DX a bit better for certain XCode versions, but didn't make any headway. After recent merges, I don't get the InvalidSignature error (maybe because you commented out my crap code in RNQuickCrypto). But I do get which seems to be from recent work on |
|
@boorad Opened a PR to not throw when the profile is missing: #2155 The profile is missing probably because it wasn't synced before destroying the node (it can happen if the node is immediately closed). We can fix that, but for now I think we can just not throw if the profile is missing as it is not really needed anywhere by Jazz. |
…hat-signature-issue
Repro steps:
cd examples/chat-rn-expo && pnpm install && pnpm iosto start the example appif an account is already stored the loading should fail with an "InvalidSignature" errorFix: margelo/react-native-quick-crypto#690
After fix timings:
Also, there are some DX improvements for
iosbuilds, for when folks start using XCode 16.3 with Nitro Modulesfixes #2124