Firebaseui-web: Disabling 'accountchooser' doesn't prevent storing `firebaseui::rememberedAccounts` in local storage

Created on 24 Jan 2019  路  4Comments  路  Source: firebase/firebaseui-web

I have disabled 'accountchooser' using credentialHelper: firebaseui.auth.CredentialHelper.NONE. But, after each google login, firebaseui::rememberedAccounts is still created in local storage. If the data is only used by the accountchooser, is there any way to stop this storage? If not, could you please consider implementing it?

Thank you in advance.

p2

Most helpful comment

@francos To disable the "account chooser" I set credentialHelper: firebaseui.auth.CredentialHelper.NONE.
Regarding the local storage it creates (firebaseui::rememberedAccounts), you might want to manually remove it in the callbacks: signInSuccessWithAuthResult and signInFailure.

All 4 comments

@mahsa2 did you find a workaround for this? I'm having the same issue, I don't want to use the account chooser but it keeps appearing even though I disabled it.

@francos To disable the "account chooser" I set credentialHelper: firebaseui.auth.CredentialHelper.NONE.
Regarding the local storage it creates (firebaseui::rememberedAccounts), you might want to manually remove it in the callbacks: signInSuccessWithAuthResult and signInFailure.

Thanks for the info @mahsa2! 馃憤

I'm also wondering why it still seems to be doing so much stuff after being disabled..

It keeps logging:

Read saved accounts from storage: []
Send message: {"jsonrpc":"2.0","rpcToken":"1371795982","build":20160119,"method":"clientReadyNotification"}
Get accountchooser browser config: {}
Send message: {"jsonrpc":"2.0","rpcToken":"1371795982","build":20160119,"method":"emptyResponseNotification"}
Received message: {"jsonrpc":"2.0","rpcToken":"1371795982","build":20160119,"method":"emptyResponseNotification"} 
from https://www.accountchooser.com

from _accountchooser.com/static/57/ac-iframe.js_ and _gstatic.com/accountchooser/client.js_

Considering how accountchooser announced gradual shutdown in July 2019, why does FirebaseUI still have it integrated?

Was this page helpful?
0 / 5 - 0 ratings