LocalSize.current provides incorrect values [341002183]

Assigned

Bug

Status Update

No update yet.

Description

an...@gmail.com

created issue #1

May 16, 2024 10:24AM

Component used: LocalSize.current

Version used: 1.1.0-rc01 & 1.1.0-beta02

Devices/Android versions reproduced on: OnePlus 9 Pro Android 14

When I use SizeMode.exact, the widget size is not correct. The following code snipped should theoretically display a Yellow box, which should be equivalent to .fillMaxSize()

    val widgetSize = LocalSize.current

    Box(
        modifier = GlanceModifier
            .fillMaxSize()
            .appWidgetBackground()
            .background(
                day = LocalWidgetBackground.current.day,
                night = LocalWidgetBackground.current.night,
            )
            .cornerRadius(16.dp),
    ) {
        Box(
            GlanceModifier
                .height(widgetSize.height)
                .background(Color.Yellow)
                .fillMaxWidth()
        ) {

        }
    }

But the yellow Box is not full height. (See attached screenshot)

The widget size changes during recompositions:

recomposition: 118.0.dp x 222.0.dp
recomposition: 118.0.dp x 218.0.dp
recomposition: 267.33334.dp x 84.666664.dp

Up until the third recomposition the value seems reasonable.

Screenshot_20240516_122240.png

3.3 MB

View

Download

Comments

za...@google.com <za...@google.com> #2May 16, 2024 05:16PM

Hello,

I'm only a little familiar with Power Apps. Is your app a mobile app or a web app?

This link lists out the alternatives.

The primary recommended alternative for the Google Fit REST API is Health Connect.

If your app does not work on Android mobile devices, you can also consider the Fitbit Web API.

an...@gmail.com <an...@gmail.com> #3May 17, 2024 09:23AM

Es muy parecido a una webapp

El mié, 22 may 2024, 15:48, <buganizer-system@google.com> escribió:

- Show quoted text -

za...@google.com <za...@google.com> #4May 23, 2024 12:21AM

the Glance library respects the sizes passed to it by the platform.

You should still be able to make the UI that you want. The platform passes a collection of sizes to the library, then the app should respond to each update with a UI that matches that size. These different UIs are then passed back to the platform as a collection, but it's up to the launcher to pick which one to show.

In your case the last, different size, might not even be being presented to the user if the launcher doesn't support landscape. You could test this by outputting solid colors based on what the local size is.

an...@gmail.com <an...@gmail.com> #5May 23, 2024 08:38AM

Thanks for the valuable information.

What you are basically saying is that it's the manufacturer/launcher fault and there is no way for us to fix this except maybe contact the manufacturer and inform them about the issue?

Your suggestion with the solid colors is exactly what I have done in my original question. You can see the result in the attached screenshot.

It's quite sad that the behavior does not seem to be consistant across all Android phones... but hey, that's the Android world

mn...@gmail.com <mn...@gmail.com> #6Jan 20, 2025 03:56PM

Same problem here
Version: 1.1.1
Device: Motorola edge 30 Neo
OS : Android 14

1.recomposition:: 363.42856.dp x 262.09525.dp
2.recomposition:: 669.7143.dp x 132.57143.dp

It is full screen width widget, the size in the first recomposition is correct, but the second one ruins all the layout.

za...@google.com <za...@google.com> #7Jan 25, 2025 12:09AM

Reassigned to mn...@gmail.com.

This looks like a different situation. The second composition looks like its for the landscape view?

Issue 341002183