I am new in ndk development in android.I have gone through the file system of ndk android.
Here, explaining what i have done.
1) i have created a folder named «jni» then create 2 file named Android.mk and ndkfoo.c.
In Android.mk
LOCAL_PATH := $(call my-dir)
include $(CLEAR_VARS)
# Here we give our module name and source file(s)
LOCAL_MODULE := ndkfoo
LOCAL_SRC_FILES := ndkfoo.c
include $(BUILD_SHARED_LIBRARY)
and in ndkfoo.c
#include <string.h>
#include <jni.h>
jstring Java_com_mindtherobot_samples_ndkfoo_NdkFooActivity_invokeNativeFunction(JNIEnv* env, jobject javaThis) {
return (*env)->NewStringUTF(env, "Hello from native code!");
}
then i have created NdkFooActivity class, in which i have written
// load the library - name matches jni/Android.mk
static {
System.loadLibrary("ndkfoo");
}
But now when i build from cygwin in xp it creates .so file successfully then i run as android application. It gives me java.lang.UnsatisfiedLinkError in LOGCAT.
So, Please let me know where i am wrong.
Thanks in Advance,
Juan Cortés
20.6k8 gold badges67 silver badges91 bronze badges
asked Jul 16, 2010 at 6:32
Indrajit KumarIndrajit Kumar
4011 gold badge5 silver badges13 bronze badges
3
I think you forgot to change the package name.
Java_com_mindtherobot_samples_ndkfoo
It should be your package what you have specified creating project.
answered Mar 9, 2011 at 8:33
Also(just ran into this issue), please note that System.loadLibrary() will always throw an exception if you are testing on the Intel Atom x86 emulator. It works just fine on regular Android emulators and debugging on a physical device.
answered Dec 13, 2012 at 23:47
5
Although this has not been the OP’s problem, I had the same java.lang.UnsatisfiedLinkError because of missing
static {
System.loadLibrary("mylibraryname");
}
answered Jan 20, 2012 at 6:53
1
There’s a good chance the signature is wrong, as others have mentioned.
If you run the javah utility, you can find the exact signature. From the bin folder in your project, where the .apk is and the root of the Java class hierarchy is generated, run:
javah -o jni_sig.h com.mindtherobot.whatever.your.package.is.NdkFooActivity
…and, if you got the package name and class name correct, it will write out a header (called jni_sig.h) with the correct function signature(s) for any native functions. Copy that to your header and .c file, adding parameters as needed, and it should work correctly.
answered Sep 25, 2010 at 6:23
SomeCallMeTimSomeCallMeTim
4,4332 gold badges27 silver badges27 bronze badges
1
Maybe not relevant anymore but as far as I know you also need to add the «lib» prefix to your native library name. In your case you need to change the Android.mk to
«LOCAL_MODULE := libndkfoo» and keep «System.loadLibrary(«ndkfoo»);» as it is. Check the ndk sample code.
answered Dec 11, 2012 at 20:41
0
I’m pretty sure that should be:
JNIEXPORT jstring JNICALL Java_com_mindtherobot_samples_ndkfoo_NdkFooActivity_invokeNativeFunction(JNIEnv* env, jobject javaThis) {
return (*env)->NewStringUTF(env, "Hello from native code!");
}
Which SDK are you targeting and which version of the NDK do you have? Does the error you’re getting say that it couldn’t load the library at all or that there was an unimplemented method? Either way make sure you don’t have android:hasCode=»false» set on the application tag in your manifest.
You can also open up the APK file after a build using winrar or something similar to make sure that the libndkfoo.so file is actually being included with the package.
Either way if you aren’t declaring the native function in NdkFooActivity you will get that error, i.e.
public static native String invokeNativeFunction();
answered Jan 13, 2012 at 14:39
Justin BuserJustin Buser
2,81525 silver badges32 bronze badges
JNIEXPORT jstring JNICALL Java_com_mindtherobot_samples_ndkfoo_NdkFooActivity_invokeNativeFunction(JNIEnv* env, jobject javaThis) {
return (*env)->NewStringUTF(env, "Hello from native code!");
}
the problem is that you compile for a target processor and execute in other. if you compile in ARM(armeabi) then execute in armeabi based emulator.
create a file called application.mk in same folder as Android.mk and put inside it one of this:
- APP_ABI := x86
- APP_ABI := armeabi
- APP_ABI := mips
- APP_ABI := armeabi x86 mips //to compile in all target and you will get 3 *.so files
then compile->run.
it should work.
answered Aug 11, 2013 at 21:03
SRedouaneSRedouane
4985 silver badges10 bronze badges
0
Create a file Application.mk in jni folder.Copy following line and paste it to Application.mk and save.Now build the project with your cgywin and run again
APP_ABI := armeabi armeabi-v7a
answered Nov 25, 2012 at 8:41
Sajal SahaSajal Saha
1692 silver badges12 bronze badges
The method name Java_com_mindtherobot_samples_ndkfoo_NdkFooActivity_invokeNativeFunction
may be not same as that of your package name or class name.
To make this naming of method exactly same you must use javah.
This will make a header file which will be having the same method name that is required.To make this header file go to the classes folder in the bin of your project(make sure you have created the java file with static method and build it properly) by this command in your terminal
~/workspace/Android_Example2/bin/classes$
In this directory write the following command
sudo javah -jni com.NDK.android_example2.MainActivity
Change the package name and class name according to your project.This will create a com_NDK_android_example2_MainActivity.h in your classes folder.
Simply move this file into your jni folder. In this file, there will be static methods that you have created in the MainActivity.java file but they are just declared not implemented that you will implement in your C file.
NOTE: While Coping the method check that the method parameters are need to be declared, so make them declare in your C file.
Hope this help.
answered Jun 11, 2013 at 5:58
Jagdeep SinghJagdeep Singh
1,2001 gold badge16 silver badges34 bronze badges
Replace this
Java_com_mindtherobot_samples_ndkfoo_NdkFooActivity_invokeNativeFunction
With
Java_your_packege_name_your_Activity_Name_invokeNativeFunction
Example if your package is com.pack and Activity Name name is MainActivity then
Java_com_pack1_MainActivity_invokeNativeFunction
Don’t forget to add reference in Activity.
// load the library — name matches jni/Android.mk
static {
System.loadLibrary("ndkfoo");
}
public native String invokeNativeFunction();
Repeat all these step it should work 
answered Jul 28, 2013 at 10:01
VinayakVinayak
6,0261 gold badge32 silver badges30 bronze badges
I also had a java.lang.UnsatisfiedLinkError error. I verified everything mention in above answers but was still getting the error. I eventually discovered that the JNI method names cannot have underscores.
Example:
Java_com_example_app_NativeLib_print_out_stuff <- generates java.lang.UnsatisfiedLinkError: print_out_stuff
Rename the print_out_stuff function to something without underscores:
Java_com_example_app_NativeLib_printOutStuff <- works
answered Mar 29, 2013 at 4:07
AwesomenessAwesomeness
6521 gold badge8 silver badges14 bronze badges
here’s a tutorial how to use native code: here
make sure you dont have any spaces in your project path.
also you cant use an underscore in your package or project name.
answered Mar 29, 2013 at 15:22
When I was working in JNI and using native code, actually an in-house library, I realized that java.lang.UnsatisfiedLinkError: Library not found comes mainly due to two reasons
1) First reason, which happens in 90% of scenarios is that the library which you are using directly or indirectly (some external JAR is using native library or native dll e.g. if your Java application is using TIBCO libraries for messaging or fault tolerance then tibrv.jar uses tibrvnative.dll library and throws java.lang.UnsatisfiedLinkError: Library not found tibrvnative if that library (the dll) is not in the path. In order to fix this problem, you need to update your PATH environment variable to include native libraries binary. see last section for more details.
2) The second reason which is bit rare is that the library might not have right kind of permissions e.g. placed under a home directory of a user, which is not accessible. This has only happened to me once when I copied another colleague’s settings to set up my environment and forget to change the PATH of Tibco dll, which was local to him.
This one is rather simple to fix but hard to find, all I need to do is given installation folder a read-write permission for a developer group. Alternatively, you can also copy that dll to your local home directory.
This was the case with core Java application running on Windows and Linux. In Android, there could be another reason of java.lang.UnsatisfiedLinkError, where the library wasn’t built with the NDK. This can result in dependencies on function or libraries that don’t exist on the device.
How to fix java.lang.UnsatisfiedLinkError: Library not found in Java
In order to fix this exception, just check if your PATH contains required native library or not. If PATH contains, then verify java.library.path system property, in case your application is using to find native libraries.
If that doesn’t work, try running your Java program by providing an explicit path of a native library while starting JVM like java -Djava.library.path =» native library path «
If you are working in Linux then check if your native library path exists in LD_LIBRARY_PATH environment variable. You can see it’s valued as ${LD_LIBRARY_PATH} and can further use grep command to check for your native library.
8 Steps to Solve «Library not found tibrvnative or android» Error in Java
As I said before, the java.lang.UnsatisfiedLinkError with the message «Library not found tibrvnative or android» typically occurs when a Java application is trying to load a native library (a shared library or DLL) using the Java Native Interface (JNI), but the library cannot be found.
Here are the steps you can follow to solve this issue:
1. Check library availability
Make sure that the native library tibrvnative or android (depending on which library you are trying to load) is available on the system where your Java application is running. The library should be present in a location where the Java runtime can find it, such as in a directory listed in the java.library.path system property or in a directory specified using the -Djava.library.path command-line option.
2. Verify library compatibility
Ensure that the version of the native library matches the version of the Java runtime and the operating system you are using. If the library is built for a different platform or architecture, it may not be compatible and could result in the UnsatisfiedLinkError.
3. Set java.library.path correctly
If the library is available in a directory not listed in the java.library.path, you can add the directory to the java.library.path system property using the -Djava.library.path command-line option when starting your Java application.
For example: java -Djava.library.path=/path/to/libraries -jar yourapp.jar
4. Load library correctly in Java code
Make sure that you are loading the native library correctly in your Java code using the System.loadLibrary() or System.load() method, and providing the correct library name (without file extension and platform-specific prefixes/suffixes).
5. Check library dependencies
Verify that all the dependencies of the native library, such as other shared libraries or DLLs, are available and correctly loaded. If any of the dependencies are missing, it can also result in the UnsatisfiedLinkError.
6. Check classpath
If you are using a Java library that requires the native library, make sure that the library is properly included in your classpath, and that the library and its dependencies are correctly packaged with your application.
7. Check system environment
Ensure that the system environment variables, such as LD_LIBRARY_PATH or PATH (for Linux/Unix) or PATH (for Windows), are correctly set to include the directories where the native library is located.
8. Update library
If you are using an outdated version of the native library, try updating it to the latest version, as the issue may have been fixed in a newer version.
By following these steps, you can resolve the java.lang.UnsatisfiedLinkError with the message «Library not found tibrvnative or android» and successfully load the native library in your Java application.
That’s all about this Java troubleshooting tips to fix java.lang.UnsatisfiedLinkError: Library not found. As you have learned in this article the java.lang.UnsatisfiedLinkError with the message «Library not found tibrvnative or android» is typically encountered when a Java application is unable to locate and load a native library using JNI.
It can be resolved by ensuring that the native library is available on the system, compatible with the Java runtime and operating system, and correctly loaded in the Java code. Additionally, checking library dependencies, classpath, system environment variables, and keeping the library up-to-date can also help in resolving this error.
Properly configuring the library path, loading the library correctly in Java code, and verifying the library’s compatibility and dependencies are crucial steps in resolving this error and ensuring the smooth execution of your Java application.
If you have already faced this issue and your solution differ than mine then you can also share with us by commenting.
cause:
In Android development, after the multi-party SDK’s SO library, this will happen between different models:
Java.lang.UnsatisfiedLinkError，This is because the program is not obtained when the program is running, an error is generated by the SO library package:
Only the SO bag provided by A company in your original project, he only provides thisArchitectureSO bag, later project needs to reference the SDK provided by B, the SO package provided, ARM64-V8A, Armeabi-V7a, MIPS, MIPS64, X86, etc., as a result, you will put it in. , Later, suddenly, a mobile phone crashed, and then generally because of this problem.Java.lang.UnsatisfiedLinkError。
Solution process:
1.Introducing a variety of SO library, if you only need some of them, you can add the following configuration in the gradle (for example):
productFlavors {
arm {
ndk {
abiFilters "armeabi-v7a", "armeabi"
}
}
x86 {
ndk {
abiFilter "x86"
}
}
}This time ARM will only introduce Armeabi-V7A and Armeabi when compiling, will only introduce x86 packages in X86.
At the same timeGradle.Properties Add:
android.useDeprecatedNdk = true2.Behind I found on Xiaomi 4, hammer T2, etc., open access to this library directly flicked directly. After analyzing, in Xiaomi 4, hammer T2 and other mobile phones, the system will go to the SO file in the ARM64-V8A this directory. If there is not ok, the biased my app exists ARM64-V8A directory. Because I can’t find the SO file in the directory,Directly report java.lang.unsatisfiedlinkerror: couldn’t Find «*****. So» is wrong.
Find a resolution on Stackoverflow:
When you install an APK on Android, the system will look for native libraries directories (armeabi, armeabi-v7a, arm64-v8a, x86, x86_64, mips64, mips) inside the lib folder of the APK, in the order determined by Build.SUPPORTED_ABIS.
If your app happen to have an arm64-v8a directory with missing libs, the missing libs will not be installed from another directory, the libs aren’t mixed. That means you have to provide the full set of your libraries for each architecture.
So, to solve your issue, you can remove your 64-bit libs from your build, or set abiFilters to package only 32-bit architectures:
android {
defaultConfig {
ndk {
abiFilters "x86", "armeabi-v7a"
}
}
buildTypes {
}If the configuration is followed, it will only put «x86», «armeabi-v7a», and the SO files under the SO files under the APK. Our questions are also solved because the system can only find the SO file in these two directories.
Several random customers get this exception every time I update my Android app. I’ve narrowed it down to two reasons, both related to using the jni.
- The *.so library is deleted when the app is upgraded.
- The *.so library is not upgraded when the app is upgraded, and the old version still remains.
The device reports do not signal that this issue is related to the OS version, memory, or anything rational. Rather than focus on why Android is having trouble upgrading the libraries, I’m hoping someone out there knows how to manually pull the libraries out of the app’s APK and put them in the right directory when this error is encountered.
asked Jun 25, 2012 at 3:33
Seems like you probably have an ABI mismatch — or possibly a false ABI mismatch caused by an Android bug that people have been talking about, where a generic arm library may not be accepted when one of the specialized varieties is preferred.
As for your workaround… you cannot write to the lib/ directory of your app’s installation, though you can put a library elsewhere if you use System.load() with a precise path/filename instead of loadLibrary() with just a library name. I don’t think there’s any official (as in future-proof) way to extract arbitrary contents from your apk, though it’s fairly easy to do at present with the zipfile classes (with something perhaps such as Context.getPackageCodePath() to discover the location and installation-variable name of the apk)
Checking for the success of the library loading attempt and reporting information about the device if it fails might be as useful.
answered Jun 25, 2012 at 4:43
Chris StrattonChris Stratton
39.8k6 gold badges83 silver badges117 bronze badges
2
Description
When running on Android I get the following error: java.lang.UnsatisfiedLinkError: dlopen failed: library "libjsc.so" not found.
Here’s my Logcat output:
2020-08-10 16:03:30.031 27444-27444/com.mrousavy.springsale D/SoLoader: init exiting
2020-08-10 16:03:30.032 27444-27444/com.mrousavy.springsale D/SoLoader: About to load: libjscexecutor.so
2020-08-10 16:03:30.032 27444-27444/com.mrousavy.springsale D/SoLoader: libjscexecutor.so not found on /data/data/com.mrousavy.springsale/lib-main
2020-08-10 16:03:30.032 27444-27444/com.mrousavy.springsale D/SoLoader: libjscexecutor.so found on /data/app/com.mrousavy.springsale-CXI-2b725337Ev76dSm2lg==/lib/x86
2020-08-10 16:03:30.032 27444-27444/com.mrousavy.springsale D/SoLoader: Not resolving dependencies for libjscexecutor.so
2020-08-10 16:03:30.044 27444-27444/com.mrousavy.springsale W/System.err: java.lang.UnsatisfiedLinkError: dlopen failed: library "libjsc.so" not found
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at java.lang.Runtime.load0(Runtime.java:938)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at java.lang.System.load(System.java:1631)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.SoLoader$1.load(SoLoader.java:395)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibraryFrom(DirectorySoSource.java:77)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.DirectorySoSource.loadLibrary(DirectorySoSource.java:50)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.ApplicationSoSource.loadLibrary(ApplicationSoSource.java:82)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.SoLoader.doLoadLibraryBySoName(SoLoader.java:766)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.SoLoader.loadLibraryBySoName(SoLoader.java:673)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:611)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.soloader.SoLoader.loadLibrary(SoLoader.java:559)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.react.ReactInstanceManagerBuilder.getDefaultJSExecutorFactory(ReactInstanceManagerBuilder.java:297)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.react.ReactInstanceManagerBuilder.build(ReactInstanceManagerBuilder.java:270)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.react.ReactNativeHost.createReactInstanceManager(ReactNativeHost.java:87)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.facebook.react.ReactNativeHost.getReactInstanceManager(ReactNativeHost.java:39)
2020-08-10 16:03:30.045 27444-27444/com.mrousavy.springsale W/System.err: at com.mrousavy.springsale.MainApplication.onCreate(MainApplication.java:48)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.app.Instrumentation.callApplicationOnCreate(Instrumentation.java:1182)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.app.ActivityThread.handleBindApplication(ActivityThread.java:6460)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.app.ActivityThread.access$1300(ActivityThread.java:219)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1859)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.os.Handler.dispatchMessage(Handler.java:107)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.os.Looper.loop(Looper.java:214)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at android.app.ActivityThread.main(ActivityThread.java:7356)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at java.lang.reflect.Method.invoke(Native Method)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:492)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale W/System.err: at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:930)
2020-08-10 16:03:30.046 27444-27444/com.mrousavy.springsale E/SoLoader: couldn't find DSO to load: libjscexecutor.so caused by: dlopen failed: library "libjsc.so" not found result: 0
2020-08-10 16:03:30.050 27444-27444/com.mrousavy.springsale D/SoLoader: init exiting
Some lines after that, the React Context fails to initialize (I’m guessing that’s related?):
2020-08-10 16:03:31.760 27444-27547/com.mrousavy.springsale E/ReactNativeJNI: logMarker CREATE_REACT_CONTEXT_END
2020-08-10 16:03:31.761 27444-27533/com.mrousavy.springsale E/unknown:ReactNative: ReactInstanceManager.createReactContext: mJSIModulePackage null
2020-08-10 16:03:31.762 27444-27533/com.mrousavy.springsale E/unknown:DisabledDevSupportManager: Caught exception
java.lang.RuntimeException: Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:234)
at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:29)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:258)
at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1293)
at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:131)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1016)
at java.lang.Thread.run(Thread.java:919)
--------- beginning of crash
2020-08-10 16:03:31.762 27444-27533/com.mrousavy.springsale E/AndroidRuntime: FATAL EXCEPTION: create_react_context
Process: com.mrousavy.springsale, PID: 27444
java.lang.RuntimeException: Unable to load script. Make sure you're either running a Metro server (run 'react-native start') or that your bundle 'index.android.bundle' is packaged correctly for release.
at com.facebook.react.bridge.CatalystInstanceImpl.jniLoadScriptFromAssets(Native Method)
at com.facebook.react.bridge.CatalystInstanceImpl.loadScriptFromAssets(CatalystInstanceImpl.java:234)
at com.facebook.react.bridge.JSBundleLoader$1.loadScript(JSBundleLoader.java:29)
at com.facebook.react.bridge.CatalystInstanceImpl.runJSBundle(CatalystInstanceImpl.java:258)
at com.facebook.react.ReactInstanceManager.createReactContext(ReactInstanceManager.java:1293)
at com.facebook.react.ReactInstanceManager.access$1100(ReactInstanceManager.java:131)
at com.facebook.react.ReactInstanceManager$5.run(ReactInstanceManager.java:1016)
at java.lang.Thread.run(Thread.java:919)
React Native version:
info Fetching system and libraries information...
(node:2822) Warning: Accessing non-existent property 'padLevels' of module exports inside circular dependency
(Use `node --trace-warnings ...` to show where the warning was created)
System:
OS: macOS 10.15.6
CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
Memory: 588.49 MB / 32.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 14.5.0 - /usr/local/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.7 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.9.3 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.6, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 25, 28, 29
Build Tools: 28.0.3, 29.0.2, 29.0.3, 30.0.0, 30.0.0, 30.0.0, 30.0.1
System Images: android-29 | Google APIs Intel x86 Atom, android-29 | Google Play Intel x86 Atom
Android NDK: 21.2.6472646
IDEs:
Android Studio: 4.0 AI-193.6911.18.40.6626763
Xcode: 11.6/11E708 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_262 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.13.1 => 16.13.1
react-native: 0.63.2 => 0.63.2
npmGlobalPackages:
*react-native*: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.
- Create Android Project
- Enable hermes
- Enable multidex
- Enable
enableSeparateBuildPerCPUArchitecture - Enable
enableProguardInReleaseBuilds
Expected Results
App should be running.
Snack, code example, screenshot, or link to a repository:
How should I put an example here?