IssueTracker

The issue turns out to be a problem with how the requestFocus() was being called. in updateFocusRectInWindowSnapshot, there is a check for isFocused that should also consider hasFocus(). The line should be changed from:

    if (!view.isFocused) {

to

        if (!view.isFocused && !view.hasFocus()) {

Resolved the original issues by using the correct rect value. However the focus shouldn't skip focus even with incorrect value. re-open the issue for investigation purpose. Thank you!

Project: platform/frameworks/support
Branch: androidx-main
Author: George Mount <mount@google.com>
Link:      https://android-review.googlesource.com/3447394

Fix requestFocus with bad previous rectangle

Fix requestFocus with bad previous rectangle 
 
Fixes: 388590015 
 
When requestFocus() is called on a ComposeView with a previousRect 
set to something that doesn't make sense (empty rectangle from the 
wrong direction, for example), the previous behavior would not 
find a matching component in that direction. Instead, it would 
find the next View to focus on and pass the focus on. 
 
With this CL, if the ComposeView isn't currently focused and a 
focusSearch fails to find something focusable in relation to the 
previous rectangle, an attempt is made irrespective of the 
previous rectangle. 
 
Relnote: "Fixed focus issue where requestFocus() with a 
nonsensical previouslyFocusedRect parameter (related to 
the focus direction) would skip past a ComposeView." 
 
Test: new test, manual testing 
Change-Id: Ifdc2f17b23620d1ae14848624f447f84cc1b0b5d

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

• androidx.compose.ui:ui-android:1.8.0-beta01
• androidx.compose.ui:ui-jvmstubs:1.8.0-beta01
• androidx.compose.ui:ui-linuxx64stubs:1.8.0-beta01

According to some Google DevRel it might soon be fixed, see the answer (from 8 days ago) here:

https://github.com/googlecodelabs/while-in-use-location/issues/7

This issue still exists, how can this be prioritized?

There is an issuetracker Component available these days for Play Services Location: https://issuetracker.google.com/components/1065160

Maybe move this issue to that Component to track it better?

I can't move it right now, but I think it's ok to stay here.

As I wrote in the code lab issue, I misunderstood when the rewrite went out (which should fix the issue).

It goes live in version 20 (current version location 19.0.1). The engineer who wrote the rewrite checked and wasn't seeing the same issue, i.e., it should be resolved.

However, that does mean we have to wait until 20 is released. I can check in again here when it's live for you to double check.

I haven't been on location in awhile, but I wanted to follow up on this.

The issue should be resolved with the play-services-location:20.0.0 release from my understanding.