Tag Archives: Android Bug

[Solved] Android Room: Database Common Error ‘missing database’

Common error 1:

D:\AndroidProjectsDemo\JetpeckTest\app\build\tmp\kapt3\stubs\debug\com\example\jetpecktest\room\BookDao.
java:15: error: There is a problem with the query: [SQLITE_ERROR] 
SQL error or missing database (no such table: BookEntity)
public abstract java.util.List<com.example.jetpecktest.room.BookEntity> loadAllBooks();

**Solution: * * the error report mentions no such table: bookentity , so first check whether your class is added to the database, that is, check the entities =?In the
annotation in your database class did you add your entity class.

@Database(version = 2, entities = [BookEntity::class])
abstract class DataBase:RoomDatabase() {

[Solved] Error: Cannot fit requested classes in a single dex file (# methods: 149346 ＞ 65536)

Any jar file that references a third-party library may trigger this error. The solution is as follows:

1. Add dependencies in build.gradle of app, and add the following code in defaultconfig [Note: it must be the module of app, not other modules]

apply plugin: 'com.android.application'

android {
    compileSdkVersion 28
    defaultConfig {
        applicationId "com.why.project.poidemo"
        minSdkVersion 16
        targetSdkVersion 28
        versionCode 1
        versionName "1.0"
        testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

        //
        multiDexEnabled true
    }
    buildTypes {
        release {
            minifyEnabled false
            proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-rules.pro'
        }
    }

    //poi
    compileOptions {
        sourceCompatibility JavaVersion.VERSION_1_8
        targetCompatibility JavaVersion.VERSION_1_8
    }
}

dependencies {
    implementation fileTree(include: ['*.jar'], dir: 'libs')
    implementation 'com.android.support:appcompat-v7:28.0.0'
    implementation 'com.android.support.constraint:constraint-layout:1.1.3'
    testImplementation 'junit:junit:4.12'
    androidTestImplementation 'com.android.support.test:runner:1.0.2'
    androidTestImplementation 'com.android.support.test.espresso:espresso-core:3.0.2'

    implementation 'com.android.support:multidex:1.0.3'
}

2. If you customize the application subclass, you need to override a method in this subclass

@Override
public void onCreate() {
    super.onCreate();
    // add the line as below
    MultiDex.install(this);
}

Unknown failure (at android.os.Binder.execTransact(Binder.java:565))Error while Installing APKs

Recently, when I was doing program debugging, I encountered a VIVO mobile phone and was always prompted with this problem. Other VIVO mobile phones did not appear and the phone was connected. Adb can also find this device and open the debugging tool



Uninstall and delete the existing application. If you want to uninstall the existing application, click ok and the following error will appear:

Unknown failure (at android.os.Binder.execTransact(Binder.java:565))
Error while Installing APKs

The original application did not uninstall, and then oneself manually uninstall, and clean up the memory, run again or the same results, I thought it was my computer’s problem, change a computer test or the same, this is a little awkward, then look up data, after testing, this method is still effective

File —> Settings – & gt; Build,Execution,Deployment —> Instant Run
Turn off the Enable Instant Run to option and rerun it again

You’ve done all this and you’ll be wondering why you can do it this way?Then take a look at what InstantRun means:
Android Studio2.0 started introducing InstantRun as a way to reduce the amount of time spent updating apps during Run and Debug. While the first Build may take a bit longer to complete, InstantRun pushes updates to the device without having to rebuild a new APK, making it easier to spot changes quickly. Note: InstantRun only supports Gradle versions of 2.0.0 and minSdkVersion of 15 in Build.gralde files. For better use, set the minSdkVrsion above 21.
Android Stuido projects using Gralde2.0.0 and above will default to Instant Run.