Open yashovardhan opened 1 week ago
bubbletrouble suggested in Discord that you add , "~> 3.2.2000"
or whatever version to `"OpenSSL-Universal" - that's how they got past the App Store submission.
Also said "But maybe its best instead of using OpenSSL-Universal to use the openssl compiled for ios and put into a xcframework ?"
link: https://discord.com/channels/1147256486762913884/1147309985651503234/1296518828108414996
What's happening?
Hey folks,
We use the react-native-quick-crypto library as a recommended polyfill dependency with our SDKs, but recently multiple of our clients are reporting that because of the OpenSSL dependency, people are facing iOS App Store rejections.
The particulars can be found here:
When installing the latest version of the library, it throws a series of errors as follows
The only way to solve it to add the OpenSSL binaries and manually linking it, using the following steps:
Now when this is done, the build goes through and the testflight app works, however while trying to publish to the app store, the following error is raised by them
I think this is happening due to the latest version changes in the library. In the past our clients have used this library extensively and did not face any such issues. Any recommendations here will be helpful.
Reproducible Code
Relevant log output
Device
iOS App Store
QuickCrypto Version
0.7.1
Can you reproduce this issue in the QuickCrypto Example app?
I didn't try (⚠️ your issue might get ignored & closed if you don't try this)
Additional information