WatchFaceType.DIGITAL and other constants within annotation types show as RestrictTo.Scope.LIBRARY [288750666]

Fixed

Bug

Status Update

No update yet.

Description

ia...@gmail.com

created issue #1

Jun 26, 2023 12:04AM

Component used: Wear-Watchface

Version used: 1.2.0-alpha08 or higher

After upgrading to Wear Watchface 1.2.0-alpha08 or higher, I noticed an error in Android Studio on both the WatchFaceType and CanvasType integers that they should only be used within the androidx.wear.watchface library:

Companion.DIGITAL can only be accessed from within the same library
(androidx.wear.watchface:watchface)

It appears this is an unintended side effect of this CL that marked those annotation classes as @RestrictTo(RestrictTo.Scope.LIBRARY).

Would it be possible to separate the constants (which really could just be on a regular Kotlin object, rather than as part of a companion object of a restricted class) from the restricted annotation class (which it doesn't matter what the class name of that annotation actually is)?

It is really annoying to have the red underlines in Android Studio and associated lint failures.

FWIW, I noticed that this does not apply to constants such as WatchFaceStyle.PROTECT_STATUS_BAR, but only to constants within a public annotation class that is restricted.

From this search, it appears this issue affects:

all WatchFaceType constants
all CanvasType constants
all TapType constants
all ComplicationsSlotBoundsType constants

Comments

al...@google.com <al...@google.com> #2Jun 26, 2023 09:14AM

Assigned to al...@google.com.

Hi. Thanks for reporting this. Fixed in this changelist. This should be available in alpha-04

al...@google.com <al...@google.com> #3Jun 26, 2023 09:37AM

Accepted by al...@google.com.

Project: platform/frameworks/support
Branch: androidx-main

commit e782987543a9f8ccd485e970ddc74564b24378db
Author: Vighnesh Raut <vighnesh.raut13@gmail.com>
Date: Mon Jan 02 15:27:40 2023

fix: tab row crashes when only 1 tab is added

Bug:

b/264018028

Test: Added unit test

Change-Id: I6381dbac304fc1d69d3708c6655f8b595668e93f

M tv/tv-material/src/androidTest/java/androidx/tv/material/TabRowTest.kt
M tv/tv-material/src/main/java/androidx/tv/material/TabRow.kt

https://android-review.googlesource.com/2373449

ap...@google.com <ap...@google.com> #4Jun 28, 2023 02:07PM

deleted

al...@google.com <al...@google.com> #5Jun 28, 2023 03:22PM

Marked as fixed.

The following release(s) address this bug.It is possible this bug has only been partially addressed:

androidx.tv:tv-material:1.0.0-alpha04

ia...@gmail.com <ia...@gmail.com> #6Jun 28, 2023 04:17PM

Is there a reason you needed to change any part of the public API surface? Given that the annotation itself isn't part of the public API, couldn't you have just renamed the IntDef annotation class?

E.g.,

public object WatchFaceType {
    /* The WatchFace has an analog time display. */
    public const val ANALOG: Int = 0

    /* The WatchFace has a digital time display. */
    public const val DIGITAL: Int = 1
}

@RestrictTo(RestrictTo.Scope.LIBRARY_GROUP)
@IntDef(value = [WatchFaceType.DIGITAL, WatchFaceType.ANALOG])
public annotation class WatchFaceTypes

al...@google.com <al...@google.com> #7Jun 30, 2023 01:53PM

Status: Assigned (reopened)

OK if we can rename the IntDefs that does sound better.

al...@google.com <al...@google.com> Jun 30, 2023 03:13PM

Accepted by al...@google.com.

al...@google.com <al...@google.com> #8Jul 3, 2023 09:26AM

Marked as fixed.

Oops I'm probably going to confuse the tooling here. I landed a follow up patch: https://android-review.git.corp.google.com/c/platform/frameworks/support/+/2646822 but it looks like I copied the wrong bug number.

Message last modified on Jul 3, 2023 09:27AM

ia...@gmail.com <ia...@gmail.com> #9Jul 3, 2023 07:23PM

Thanks so much - that follow up change looks great! I'll be sure to test it once the next release comes out.