Failure to initialize! Your hardware does not support this application, sorry! [Android] [Shield TV]

I ran into an issue on Shield TV (Android). But really this affects any Android device.

Failure to initialize!
Your hardware does not support this application, sorry!



The cause was actually that I had a legacy native library in the Assets/Plugins/Android/lib/armeabi folder.

By default when you build a native library you get outputs for x86, armeabi, armeabi-v7a, etc. After Unity 5.X support for armeabi was deprecated.

My issue is caused by Unity being confused by the legacy armeabi and crashing at runtime. My solution was to remove all the native libraries except for armeabi-v7a which removed the offending native library.

To provide a little more detail, I edited my gradle build file to add an abiFilter to only build the armeabi-v7a native library.

Code (CSharp):

1. android {
2.     compileSdkVersion 19
3.     buildToolsVersion '19.1'
4.  
5.     defaultConfig {
6.         ndk {
7.             moduleName 'lib-ndk-unity-store-sdk'
8.             abiFilters 'armeabi-v7a'
9.             stl 'stlport_static'
10.             cFlags '-Wno-error=format-security'
11.             ldLibs 'c', 'm', 'log'
12.         }
13.     }
14. }

If you build the legacy way with ndk-build, add the filter to Android.mk.

Code (CSharp):

1. APP_ABI := armeabi-v7a

One more detail about my setup. I wrapped the native library into an AAR file which was built with Android Studio. I have the AAR file placed in Assets\Plugins\Android\libs\UnityPluginStoreSDK.aar and it works!

IMO, Unity needs a little more error handling in the packager that uses AAR files to show a more descriptive error when compiling and to add support for including multiple native libraries. Although the error happened at runtime, it could have been detected at compile time.

Hopefully this information helps someone working on a JAR/Native plugin in the future!

 

I have a question that is very similar regarding the problem you just solved here. Let me know if this thread is still active and if you are still checking it.

 

Still watching. I ran into this on another engine and should have recognized this issue...

 

It works for me! Thank you so much guys.

 

Thank you guys,you helped a lot

 

It works for me Thank you guys.

 

I don't know if this is the same issue but I get this message only after deleting data for my app. On first install it works fine, delete data, there is a problem. I wonder why?

I'll investigate further and see if this solution also fixes this delete data bug.

 

I would like to add it is actually this bug : https://issuetracker.unity3d.com/is...dward-does-not-support-this-application-sorry . There's no need to fix the gradle to build an AAR without armeabi because the fix was backported to many previous versions as listed. Fixed in: 5.6.6f2, 2017.1.3p4, 2017.2.3p1, 2017.4.3f1, 2018.1.0p4, 2018.2.0b2, 2018.3.0a1

That means if you have armeabi in your AAR and you use 2017.1.3f1 to build the game, it would cause the Failure to initialize since 2017.1.3f1 < 2017.1.3p4. If you just update it to 2017.1.5f1 (which is currently the lowest possible version with Unity Hub) you don't have to do anything to the AAR. It just works.

 

thanks bro . it worked for me .
defaultConfig {
applicationId "xxxxxxxxxx"
compileSdkVersion 25
buildToolsVersion "26.0.0"
minSdkVersion 19
multiDexEnabled true
ndk {
moduleName 'lib-ndk-unity-store-sdk'
abiFilters 'armeabi-v7a'
stl 'stlport_static'
cFlags '-Wno-error=format-security'
ldLibs 'c', 'm', 'log'
}
}