Remove setViewContent APIs and refactor ViewGroup.setContent to be more consistent [160335130]

Fixed

Bug

Status Update

No update yet.

Description

le...@google.com

created issue #1

Jul 1, 2020 06:48PM

Component used:
Version used:
Devices/Android versions reproduced on:

If this is a bug in the library, we would appreciate if you could attach:
- Sample project to trigger the issue.
- A screenrecord or screenshots showing the issue (if UI related).

Comments

po...@google.com <po...@google.com> #2Jul 3, 2020 01:59PM

Reassigned to po...@google.com.

We have some support in androidx.compose.ui.autofill

Leaving this bug open in case Ralston wants to add more info

po...@google.com <po...@google.com> #3Jul 3, 2020 03:30PM

Reassigned to le...@google.com.

I found an example here. One problem is that it only works with the Google autofill service. When using any other service like Microsoft Authenticator or OneKey, the following error is shown:

D/Autofill Status: Autofill popup isn't shown because autofill is not available.
    
    Did you set up autofill?
    1. Go to Settings > System > Languages&input > Advanced > Autofill Service
    2. Pick a service
    
    Did you add an account?
    1. Go to Settings > System > Languages&input > Advanced
    2. Click on the settings icon next to the Autofill Service
    3. Add your account

Is this a bug on your side or do the app developers of these password managers need to change their implementation?

po...@google.com <po...@google.com> Jul 9, 2020 03:51PM

Reassigned to po...@google.com.

ap...@google.com <ap...@google.com> #4Jul 30, 2020 03:09AM

Another problem I am facing with autofill is that it won't save my credentials. I tried forcing to finish the context as described here, but it won't do that either although I filled in the username with the one provided by the Google autofill service.

po...@google.com <po...@google.com> #5Jul 31, 2020 10:09AM

Marked as fixed.

deleted

Issue 160335130