Don't Perform Disk IO on Main Thread [117796731]

Fixed

Bug

Status Update

No update yet.

Description

su...@twofortyfouram.com

created issue #1

Oct 16, 2018 11:44AM

Component used: WorkManager
Version used: Alpha 10
Devices/Android versions reproduced on: All

WorkManager performs disk IO on the main thread during application startup, as it touches disk for its SharedPreferences file. Ideally this would be done in a background thread to avoid adding delays to app launch.

I was able to identify this by removing the auto initialization ContentProvider via the manifest merger, enabling strict mode in Application.onCreate(), and then manually initializing WorkManager after strict mode was turned on.

Comments

ha...@gmail.com <ha...@gmail.com> #2Oct 16, 2018 08:28PM

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

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

ha...@gmail.com <ha...@gmail.com> #3Oct 16, 2018 08:30PM

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?

ha...@gmail.com <ha...@gmail.com> #4Oct 16, 2018 08:36PM

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.

ap...@google.com <ap...@google.com> #5Oct 17, 2018 10:12PM

deleted

su...@google.com <su...@google.com> Oct 17, 2018 10:13PM

Marked as fixed, reassigned to su...@google.com.

su...@twofortyfouram.com <su...@twofortyfouram.com> #6Oct 18, 2018 12:50AM

Facing the same issue here, Google autofill service seems to work. Zero documentation on adding support for Autofill framework on jetpack compose.

su...@twofortyfouram.com <su...@twofortyfouram.com> #7Oct 18, 2018 12:51AM

Hello, I am trying to implement the same thing - it seems like there's no way for current password managers like 1Password or Bitwarden, to automatically pick up the fields. Is there a possible solution?