star-micronics / react-native-star-io10

react-native-star-io10 is a library for supporting application development for Star Micronics devices.

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Unresolved reference: "ReactNoCrashSoftException"

vivekvardhanadepu opened this issue · comments

Description

While creating android build, getting Unresolved reference: "ReactNoCrashSoftException"

Your development environment

ProductName:    macOS
ProductVersion: 11.6
BuildVersion:   20G165

System:

    OS: macOS 11.6
    CPU: (8) x64 Apple M1
    Memory: 39.34 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 10.16.3 - ~/.nvm/versions/node/v10.16.3/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.14.2/bin/yarn
    npm: 6.9.0 - ~/.nvm/versions/node/v10.16.3/bin/npm
    Watchman: 2022.06.27.00 - /opt/homebrew/bin/watchman
  SDKs:
    iOS SDK:
      Platforms: DriverKit 21.2, iOS 15.2, macOS 12.1, tvOS 15.2, watchOS 8.3
  IDEs:
    Android Studio: 2021.2 AI-212.5712.43.2112.8609683
    Xcode: 13.2.1/13C100 - /usr/bin/xcodebuild
  npmPackages:
    react: 16.9.0 => 16.9.0 
    react-native: 0.61.5 => 0.61.5 
  npmGlobalPackages:
    react-native-cli: 2.0.1

android:

buildToolsVersion = "30.0.2"
minSdkVersion = 21
compileSdkVersion = 30
targetSdkVersion = 30
classpath("com.android.tools.build:gradle:3.5.4")
classpath 'com.google.gms:google-services:4.2.0'

To Reproduce

Steps to reproduce the behavior:

  • create a react-native app with above config(node, react-native, android)
  • install react-native-star-io10
  • create android build

Tried these

Sorry for our late response.

We have never encountered this exception before and have not been able to find sufficient information about it by searching the internet.

So we would like to know where this exception occurred and would appreciate it if you could provide us with a crash log.

Thank you in advance.

commented

@vivekvardhanadepu
Were you able to find a solution to this issue?
We will close the issue once, but if you are still having trouble, please reopen or post a new issue.