0.67.5 - Android BigInt being NaN

Description

I tested using BigInt on Android BigInt(1) results in NaN. On iOS it is working fine.

Version

0.67.5

Output of npx react-native info

System:
    OS: macOS 12.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 774.41 MB / 32.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm
    Watchman: 2022.03.21.00 - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
    Android SDK:
      API Levels: 23, 29, 30, 31, 32
      Build Tools: 29.0.2, 30.0.2, 30.0.3, 32.0.0, 32.1.0
      System Images: android-29 | Google APIs Intel x86 Atom, android-29 | Google Play ARM 64 v8a, android-32 | Google APIs ARM 64 v8a
      Android NDK: 22.1.7171670
  IDEs:
    Android Studio: 2021.1 AI-211.7628.21.2111.8139111
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.11 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 17.0.2 => 17.0.2
    react-native: 0.67.5 => 0.67.5
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Steps to reproduce

Simply using BigInt on Android. No reproduce steps.

Snack, code example, screenshot, or link to a repository

None

[Kudo]

yes, the Intl only is a breaking change from new jsc. that’s why the new version is still jsc-android@next (not in latest dist-tag). since hermes is now acting as a default engine, i’m waiting a proper time when jsc-android is retired as a third-party package by lean core effort.

[cortinico]

So it seems using org.webkit:android-jsc-intl:+ for the latest JSC is a must.

Great thanks for clarifying. @Kudo it seems like we need to update the template to remove the non-intl variant from it?