Update targetSdk to 33 [238790278]

Fixed

Bug

Status Update

No update yet.

Description

al...@google.com

created issue #1

Jul 12, 2022 08:30PM

We need targetSdk to be 33 before we move forward with upstreaming, otherwise we are releasing potentially broken code in betas.

Comments

al...@google.com <al...@google.com> #2Jul 12, 2022 08:35PM

Accepted by al...@google.com.

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

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

al...@google.com <al...@google.com> #3Jul 12, 2022 08:56PM

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?

al...@google.com <al...@google.com> #4Jul 12, 2022 09:00PM

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.

al...@google.com <al...@google.com> Jul 13, 2022 07:04PM

Marked as fixed.

na...@google.com <na...@google.com> #5Sep 12, 2022 05:51PM

deleted

Issue 238790278