INSTALL_FAILED_MISSING_SHARED_LIBRARY without google api

Ok, I looked through, but all I get is the api from google. I am not using api from google in my application.

I am writing an application that uses the sqlite browser and not any other link. Any ideas? I haven't launched the app yet, so it's very easy to try it now.


<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android"
    package="main.abvas"
    android:versionCode="1"
    android:versionName="1.0" >

    <uses-sdk
        android:minSdkVersion="14"
        android:targetSdkVersion="21" />

    <uses-permission android:name="com.symbol.emdk.permission.EMDK" />
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />

    <application
        android:allowBackup="true"
        android:icon="@drawable/ic_launcher"
        android:label="@string/app_name"
        android:theme="@style/AppTheme" >
        <uses-library android:name="com.symbol.emdk" />

        <activity
            android:name=".MainActivity"
            android:label="@string/app_name" >
            <intent-filter>
                <action android:name="android.intent.action.MAIN" />

                <category android:name="android.intent.category.LAUNCHER" />
            </intent-filter>
        </activity>
        <activity
            android:name=".OrderDetailsActivity"
            android:label="@string/title_activity_order_details" >
        </activity>
    </application>

</manifest>

      

+3


source to share


1 answer


Your project asks for the firmware library:

<uses-library android:name="com.symbol.emdk" />

      

The device or emulator on which you are testing the application does not contain this library.



Your options:

  • Remove this library if you are not actually using it

  • Test the app only on devices that have this library

  • Add android:required="false"

    to element <uses-library>

    and detect at runtime if you have access to the library, perhaps by calling Class.forName()

    on some Java class that should be in the library

+6


source







All Articles