Skip to content
Snippets Groups Projects
Commit 4a6e5cca authored by Paul Duffin's avatar Paul Duffin
Browse files

Remove erroneous duplicate baseline entry

Due to a bug in Metalava the `VisiblySynchronized` check would report
an erroneous duplicate baseline entry that referenced some internal
implementation detail, e.g. `PsiThisExpression` instead of an actual
API element. Another entry with the same message and correct API
element was also written.

The Metalava bug has been fixed so this change removes the erroneous
entry.

Bug: 311690008
Test: m checkapi
Merged-In: If5550b8cc0a97f02fb7fb1bd949f8e5517007d4c
Change-Id: I79b3c9802e40e74ba7f0c9b102dc201d01ddeab5
parent ce4a4349
No related branches found
No related tags found
No related merge requests found
......@@ -1221,8 +1221,6 @@ UserHandleName: android.content.ContentCaptureOptions:
Classes holding a set of parameters should be called `FooParams`, was `ContentCaptureOptions`
VisiblySynchronized: PsiThisExpression:
Internal locks must not be exposed (synchronizing on this or class is still externally observable): method android.content.res.AssetManager.getApkPaths()
VisiblySynchronized: android.content.res.AssetManager#getApkPaths():
Internal locks must not be exposed (synchronizing on this or class is still externally observable): method android.content.res.AssetManager.getApkPaths()
VisiblySynchronized: android.content.res.AssetManager#getLastResourceResolution():
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment