Assigned
Status Update
No update yet.
Comments
ti...@google.com
Can you attach / share a project that reproduces the issue?
au...@google.com
Now i sure this is viewpager2's bug.
because just occur recyclerview inside viewpager2 with constraintlayout, if paging3 use Independently with viewpage2 it's not problem.
because just occur recyclerview inside viewpager2 with constraintlayout, if paging3 use Independently with viewpage2 it's not problem.
ti...@google.com
deleted
ti...@google.com
deleted
al...@google.com
al...@google.com
Since we don't have
@Deprecated(level=HIDDEN)in Java, what's the recommended way to make these properties visible to old libs?
Two options:
- Make the API internally visible in a
1.13.1release using Javapublicand@RestrictTo(LIBRARY_GROUP_PREFIX). This will fix compatibility with historicalvectordrawablereleases and new releases can use the preferred public APIs. There will still be issues with1.13.0. - Release a stable version of
vectordrawablethat uses the new public API, then define a constraint in1.13.1that requires that version or newer. This won't fix compatibility with older versions, but it will avoid the issue by forcing an update tovectordrawable. There will still be issues with1.13.0.
Description
Related libraries:
androidx.core:core– starting on version 1.13.0androidx.vectordrawable:vectordrawable– up to 1.2.0-beta01 (latest available)Related changes:
In this change, one API was changed from public to private (
androidx.core.graphics.PathParser.PathDataNode.mType) inandroidx.core:corewhich affectedandroidx.vectordrawable:vectordrawable, since it uses that inandroidx.vectordrawable.graphics.drawable.VectorDrawableCompat.VPath.nodesToString.The change affected both libraries, as expected, but the problem is that there hasn't been a release of
androidx.vectordrawable:vectordrawablethat contains the code change (I checked 1.2.0-beta01, which is the latest at the time).