First, move <provider> to be a child of <application>, not <activity>. Second, change android:exported=”true” to android:exported=”false”, until such time as you secure your ContentProvider. As it stands, once you fix the <provider> element location as noted above, any app can read and write anything in your provider, which is unlikely to be what the user … Read more
When you first come across this message, you will most likely be working against an unreleased version of the database. If that is the case, most likely you should not increment the database version. Simply clearing app data will move you passed the exception. If you do not increment the database (recommended): You should clear … Read more
There are two options for creating and updating databases. One is to create a database externally, then place it in the assets folder of the project and then copy the entire database from there. This is much quicker if the database has a lot of tables and other components. Upgrades are triggered by changing the … Read more
change your insertion code to this: SQLiteDatabase db7 = db.getWritableDatabase(); ContentValues values5= new ContentValues(); for (int i = 0; i < poslist.size(); i++) { values5.put(DBManager.TableInfo.KEYID, ID1); values5.put(DBManager.TableInfo.DOCU, document); values5.put(DBManager.TableInfo.ATTEND,attendancelist.get(i)); values5.put(DBManager.TableInfo.EMAIL, emaillist.get(i)); values5.put(DBManager.TableInfo.PARTY,partytypelist.get(i) ); values5.put(DBManager.TableInfo.BIO,biometriclist.get(i)); values5.put(DBManager.TableInfo.KEY_LOGIN_USER,username2); String condition5 = DBManager.TableInfo.DOCU + ” =?”; Cursor cursor5 = db7.query(DBManager.TableInfo.UPDATEPARTY, null, condition5, new String[]{DBManager.TableInfo.ATTEND}, null, null, null); long status5 … Read more