IssueTracker

This was fixed in the same changed that fixed b/253531073, link: https://android-review.googlesource.com/c/platform/frameworks/support/+/2253857/3/sqlite/sqlite/src/main/java/androidx/sqlite/db/SupportSQLiteQueryBuilder.kt

But I think it has not reached google3 yet. Closing as dupe.

To clarify as in, has not reached Google maven, but should be part of the beta02 release.

DataStore is a KMP project. We have created an internal interface in datastore-core in #comment2, but the bcv native file was updated. This is an unexpected behavior.

The bug here is that BCV does not respect @RestrictTo and still includes it into the API files as a regular public API, when in reality we should not throw on changes to these or only track them in -restricted api files like Metalava does.

We also need to check that the restricted API lint / error works for non-JVM source sets.

Metalava treats @RestrictTo APIs differently depending on the scope used. LIBRARY scope isn't tracked in signature files. LIBRARY_GROUP_PREFIX scope is tracked in restricted_ signature files and checked for compatibility. LIBRARY_GROUP scope is treated like LIBRARY for atomic library groups and treated like LIBRARY_GROUP_PREFIX for non-atomic groups.

However, it looks like the nonPublicMarkers from the KlibDumpFilters currently can only be qualified annotation names, so we can't differentiate between the RestrictTo annotations based on the scope value.

Where annotation names are deserialized for a definition. The ProtoConstructorCall is really IrConstructorCall, and it doesn't look like that would have the value either.

Bugjuggler: https://github.com/Kotlin/binary-compatibility-validator/issues/285