Assigned
Status Update
Comments
th...@gmail.com <th...@gmail.com> #2
IMPORTANT! Please note that if you released your library to stable with these calls, the APIs must maintain binary compatibility moving forward.
That means the restricted APIs need to be made public or @RestrictTo(LIBRARY_GROUP_PREFIX) (e.g. effectively public for the purposes of compatibility).
You CANNOT simply remove the call to the restricted API.
That means the restricted APIs need to be made public or @RestrictTo(LIBRARY_GROUP_PREFIX) (e.g. effectively public for the purposes of compatibility).
You CANNOT simply remove the call to the restricted API.
gm...@gmail.com <gm...@gmail.com> #3
Sorry, additional point of clarification. These bugs have been filed against the call sites, but the issue really applies to both the restricted API and the call site.
For the call site: the call may be safely removed, however if the call went out in a stable release then that release will crash if the restricted API is removed.
If the restricted API should be maintained to ensure binary compatibility with your library, please forward this issue to the component for the restricted API and continue reading.
For the restricted API: this bug was filed because your API was used outside of your library group. The API must now be tracked for binary compatibility. You may make the API public or LIBRARY_GROUP_PREFIX visibility.
For the call site: the call may be safely removed, however if the call went out in a stable release then that release will crash if the restricted API is removed.
If the restricted API should be maintained to ensure binary compatibility with your library, please forward this issue to the component for the restricted API and continue reading.
For the restricted API: this bug was filed because your API was used outside of your library group. The API must now be tracked for binary compatibility. You may make the API public or LIBRARY_GROUP_PREFIX visibility.
mo...@gmail.com <mo...@gmail.com> #4
No, moved on to another project.
Description
Component used: RowsSupportFragment Version used: 1.0.0 Devices/Android versions reproduced on: The problem appears on Crashlytics on all different devices. For all android versions.
BRAVIA 4K GB ATV3 (Android 10) BRAVIA VH1 (Android 10) AFTSSS (Android 9) AFTSS (Android 9) And many many other Android TV devices
If this is a bug in the library, we would appreciate if you could attach:
Steps to reproduce.
I'm sorry I couldn't reproduce the bug reliably.