https://kotlinlang.org logo
#compose-wear
Title
# compose-wear
f

FEDUSS

12/07/2023, 6:40 PM
Made scrollbar always visibile in ScalingLazyColumn -->
Hi, my app was rejected during review process for the following error:
"Issue found: Missing scrollbar
Your app does not display the scroll bar when the user interacts with a scrollable view. For more information, see Show the scrollbar."
I was wondering if you could suggest me how to keep the scrollbar always visible instead of showing it only during scroll, thanks :).
y

yschimke

12/07/2023, 7:32 PM
I hope that isn't what they are asking for
It should only be when scrolling
f

FEDUSS

12/07/2023, 7:35 PM
It's already visible only when scrolling :(
y

yschimke

12/07/2023, 7:39 PM
Check all screens, then appeal.
👍 1
f

FEDUSS

12/07/2023, 7:40 PM
I'll do, thanks
Hi @yschimke, your hypothesis was right: the scrollbar was missing in one page and the app is now rejected for other reason XD Thanks :D
b

Beowulf

12/13/2023, 6:20 PM
It is impossible for us to release for wearOS. In 1.2.0, chips are not scaling correctly when the user increases the font size. In 1.3.0-beta01, the scrollbar is no longer displayed when scrolling with the crone. Both reasons why Google rejects the app - thanks to Google for rejecting the app because of bugs in their own code...
f

FEDUSS

12/13/2023, 6:28 PM
You shoudn't use beta lib in your production channel...btw i'm using horologist 0.5.12 and google didn't reject my app because of scrollbar
b

Beowulf

12/13/2023, 6:30 PM
Yeah, but the last stable version lacks the scaling which was added in 1.3.0-beta01 > Chip and ToggleChip now adjust their height to accommodate content that has grown due to large fonts for accessibility. And yes we can use horologist, but then we need to pull it in, only for this. And the horologist library causes crashes, when the users rotates the crown during app start.
f

FEDUSS

12/13/2023, 6:31 PM
I don't reproduce that crash during app start
y

yschimke

12/13/2023, 6:32 PM
Can you report that bug with crown rotation. Happy to try to fix it. But think it's the first I've heard of it.
b

Beowulf

12/13/2023, 6:33 PM
for horologist or compose-wear?
y

yschimke

12/13/2023, 6:33 PM
I guess whereever you think it's caused. Or horologist if unsure.
b

Beowulf

12/13/2023, 6:34 PM
In compose-wear we have the problem, that the PositionIndicator is no longer shown with 1.3.0-beta01 and with horologist we found crashes when the crown is rotated on app start. So which issue do you mean? 😄
If you mean the horologist bug, I’m sry I don’t have a GitHub-Acc so I cannot report the bug..
y

yschimke

12/13/2023, 6:37 PM
This function is what is used in the stable branch of horologist to resize the Chips for font scaling.
Copy code
/** Adjusts height of the chip as per the font scale. */
public fun Modifier.adjustChipHeightToFontScale(fontScale: Float, padding: Dp = 0.dp): Modifier =
    if (fontScale > 1.06) {
        this.then(Modifier.height(60.dp + padding))
    } else {
        this
    }
There are a lot of Google apps using the Wear Compose and Horologist code, so it definitely can work. Not sure why not for you. If you can officially report the bugs then we will fix them.
b

Beowulf

12/13/2023, 6:51 PM
Ok, have now converted it to horlogist again and it looks like it no longer occurs in the latest version. It’s still silly that the PostitionIndicator is no longer displayed without horogist since 1.3.0.