Status Update
No update yet.
Comments
jo...@google.com
tn...@google.com
tn...@google.com
rv...@mozilla.com
private void refreshAllLiveData() {
AppDataBase YOUR_DATABASE_WHICH_YOU_BUILD = .....
SupportSQLiteDatabase writableDatabase = YOUR_DATABASE_WHICH_YOU_BUILD.getOpenHelper().getWritableDatabase();
//get the database count;
Cursor cursor = writableDatabase.query("SELECT count(*) FROM sqlite_master WHERE type = 'table' AND name != 'android_metadata' AND name != 'room_master_table';");
int tableCount = 0;
while(cursor.moveToNext()) {
tableCount = cursor.getInt(0);
}
for (int i = 0; i < tableCount; i++) {
//update version table with the incremented count because room modification log stores tables with ids instead of names
writableDatabase.execSQL("INSERT OR REPLACE INTO room_table_modification_log VALUES(null, "+(i)+")");
}
YOUR_DATABASE_WHICH_YOU_BUILD.getInvalidationTracker().refreshVersionsAsync();
}
-----
This is a workaroud for refreshing all live datas, I still prefer to use a proper API you implemented.
Thanx
rv...@mozilla.com
tn...@google.com
This is getting flagged now because in the new version, we made the SDK_INT check smarter! See
I didn't look carefully at the second case you linked to before:
63 fun enterPipModeCompat() = when {
64 !hasSystemFeature -> false
65 SDK_INT >= Build.VERSION_CODES.O -> enterPipModeForO()
66 SDK_INT >= Build.VERSION_CODES.N -> enterPipModeForN()
67 else -> false
68 }
And I think that is actually a bug!
Lint is trying to be smart -- it sees that the first switch case references hasSystemFeature, which is defined as
private val hasSystemFeature = SDK_INT >= Build.VERSION_CODES.N &&
activity.packageManager.hasSystemFeature(PackageManager.FEATURE_PICTURE_IN_PICTURE)
If the switch case had been hasSystemFeature -> false, then we could conclude that AFTER the switch case, SDK_INT must surely be < N. But here the switch case is inverted. And it is incorrect for lint to negate the version constraint here -- that's the bug -- it now believes that by line 65, we know SDK_INT >= N. And that's why by line 66 when it sees an SDK_INT >= N comparison, it flags it as redundant.
rv...@mozilla.com
Thanks for the quick fix! I'll verify it when alpha07 is released.
Regarding Context.kt, I did more digging into where the function gets called in our codebase and am confident now that the improved detection in 8.8 is doing the right thing in this case. I can confirm that lint still passes if I remove the @TargetApi annotation entirely as the function is only ever called when running on <Q.
tn...@google.com
Great, thank you! (P.S. I think alpha07 was released yesterday so this will be in alpha08.)
an...@google.com
Thank you for your patience while our engineering team worked to resolve this issue. A fix for this issue is now available in:
- Android Studio Ladybug Feature Drop | 2024.2.2 Canary 8
- Android Gradle Plugin 8.8.0-alpha08
We encourage you to try the latest update.
If you notice further issues or have questions, please file a new bug report.
Thank you for taking the time to submit feedback — we really appreciate it!
rv...@mozilla.com
Verified fixed in alpha08!
Description
With the AGP 8.8.0 alpha builds, we're seeing new ObsoleteSdkInt warnings that seem spurious. Our project is built with minSdkVersion = 21, targetSdkVersion = 34, and compileSdkVersion = 35.
I'm not sure if it's the TargetApi annotation that's tripping things up, but my understanding is there's nothing preventing this code from running on older API levels and the code is valid as-written.