[Archive] Getting Error when trying to 'Archive' - iOS (React-Native)

[aditya1]

Archived Content from Web3Auth Community

This topic was originally posted by aditya1 on 10/11/2024.
This content has been migrated from our previous community forum to preserve valuable discussions.

---

when I try to ‘Archive’ after installing ‘react-native-quick-crypto’, I get series of errors. Upon manually linking OpenSSL, app works till Test Flight. But when I try to add app to apple review, it gets rejected 'saying ‘binary error’.

I have attached the Screenshot of the error for the reference.

we are using Metamask, wallet-connect and coinbase as well where ‘react-native-random-values’ is used.

could you please assist us resolve this?

image1702×1042 200 KB

IMG_69391170×1144 243 KB

[w3abot]

Hi Aditya! Thank you for reaching out and providing such detailed information about the issue you’re facing.

Here’s a summary of the details you provided for the support team:

• SDK Details: PnP React Native SDK
• SDK Version Number: (not specified)
• Platform: iOS (React-Native)
• Issue: Error when trying to ‘Archive’ after installing ‘react-native-quick-crypto’.
• Additional Libraries Used: Metamask, wallet-connect, Coinbase, and ‘react-native-random-values’.
• Error Description: The app works until Test Flight but gets rejected during apple review due to a ‘binary error’.
• Attached: Screenshot of the error.

For the support team to assist you better, could you please provide the following additional information?

• The specific SDK version you are using.
• Code snippets related to Web3Auth initialization and login, if possible.
• Any relevant browser console screenshots that could help in diagnosing the issue.

Thank you again, and we hope to get this resolved for you soon!

Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.

[aditya1]

We are using 7.0.1 version

[yashovardhan]

Can you try using an older version of react-native-quick-crypto? i think this is happening due to some changes in the latest version of the library. Additionally, if get random values is working for you with other libraries you can try using that with our SDK as well and skip the react-native-quick-crypto entirely.

[yashovardhan]

If you check our pnp react native quick start, we do not use this module there as well. We use this module only in our mpc sdks: web3auth-pnp-examples/react-native/rn-bare-quick-start/index.js at main · Web3Auth/web3auth-pnp-examples · GitHub

So you can safely skip this quick crypto library altogether.

Nonetheless, I have raised an issue on their github as well: 🐛 Apple Store Rejection · Issue #470 · margelo/react-native-quick-crypto · GitHub

[aditya1]

When we use web3auth without react-native-quick-crypto, we get the following error:
TypeError: undefined is not an object (evaluating ‘subtle.digest’)

import ‘react-native-get-random-values’;
this line is there in index.js

[yashovardhan]

Can you try running our quick start example and see if you face the same issue? Additionally, just make sure to do a fresh pod install --repo-update following the removal of react-native-quick-crypto and addition of random values

[aditya1]

@yashovardhan

pod install --repo-update

We have manually signed the OpenSSL.xcframework and pushed for review and waiting from apple to review.

[yashovardhan]

Checkout the github issue on this, they have posted an update

  <a href="https://github.com/margelo/react-native-quick-crypto/issues/470#issuecomment-2420276771" target="_blank" rel="noopener">github.com/margelo/react-native-quick-crypto</a>

🐛 Apple Store Rejection

<div class="github-info">
  <div class="date">
    opened <span class="discourse-local-date" data-format="ll" data-date="2024-10-14" data-time="08:19:50" data-timezone="UTC">08:19AM - 14 Oct 24 UTC</span>
  </div>


  <div class="user">
    <a href="https://github.com/yashovardhan" target="_blank" rel="noopener">
      <img alt="yashovardhan" src="https://web3auth.io/community/uploads/default/original/2X/1/192e7e3fc381fee9bf51127585b8004f28bf8bcc.png" class="onebox-avatar-inline" width="20" height="20" data-dominant-color="5D5A69">
      yashovardhan
    </a>
  </div>
</div>

<div class="labels">
</div>

### What's happening?

Hey folks,

We use the react-native-quick-crypto librar…y 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:

  1. Install OpenSSL:
  Run brew install openssl to ensure OpenSSL is installed.
  
  
  2. Link OpenSSL in Xcode:
  In Xcode, go to Build Settings and add the following paths:
  
  Library Search Paths: /usr/local/opt/openssl/lib
  
  Header Search Paths: /usr/local/opt/openssl/include
  
  
  
  3. Update Podfile:
  Add pod 'OpenSSL-Universal' to your Podfile.
  Run pod install inside the ios directory.
  
  
  4. Link OpenSSL Libraries:
  In Xcode, under General > Linked Frameworks and Libraries, add libssl.a and libcrypto.a.
  
  
  5. Clean and Rebuild:
  Use Product > Clean Build Folder in Xcode, then rebuild the project.
  

• 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

import {install} from 'react-native-quick-crypto';

install();

Relevant log output

N/A

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

• I am using Expo

• I have read the Troubleshooting Guide

• I agree to follow this project’s Code of Conduct

• I searched for similar issues in this repository and found none.

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: Discord