The conditional compatibility checking based on experimental annotations only checks if an API is currently experimental, and raises compatibility errors if a previously experimental API changes. This creates compatibility errors that weren't present before.

As an example:

androidx.benchmark.macro.junit4.BaselineProfileRule was experimental in 1.1.0-beta05 with a method named collectBaselineProfile.
This version is from before the experimental API tracking migration, so it was in public_plus_experimental_1.1.0-beta05.txt but not 1.1.0-beta05.txt.
Between that version and the current one, BaselineProfileRule had the experimental annotation removed, and the collectBaselineProfile method was renamed to collect.
Because BaselineProfileRule was previously experimental and not present in 1.1.0-beta05.txt, renaming the collect method did not cause a compatibility error.
Regenerating 1.1.0-beta05.txt adds an entry for BaselineProfileRule with the experimental annotation since experimental APIs are now tracked in the main API file.
checkApi for 1.1.0-beta05.txt and current.txt now raises a compatibility error saying the method collectBaselineProfile was removed.