Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Double password visibility toggles #347

Closed
nicbell opened this issue Oct 10, 2016 · 7 comments
Closed

Double password visibility toggles #347

nicbell opened this issue Oct 10, 2016 · 7 comments
Labels

Comments

@nicbell
Copy link

nicbell commented Oct 10, 2016

When using com.firebaseui:firebase-ui-auth:0.6.0 with Android Support Library, revision 24.2.0. I get two icons to toggle password visibility because this feature is now built-in.

As temporary fix I have downgraded my Android Support Library to 24.1.0.

@samtstern
Copy link
Contributor

@nicbell thanks for the report! We're actually using 23.x for all our testing for other reasons, so we hadn't seen this yet.

@samtstern samtstern added the auth label Oct 10, 2016
@SUPERCILEX
Copy link
Collaborator

I noticed this issue before, but never bothered to do extensive research on it because I thought it was an isolated issue. I did however notice that if you don't set the eye drawable it still shows up which is weird. Since somebody else noticed this issue on the same version of the support lib that I'm using, I decided to check the release notes and indeed in v24.2.0 they added the password visibly toggle as the default. I'll submit a PR upgrading us to 24.2.1 unless somebody else wants to.

@samtstern
Copy link
Contributor

@SUPERCILEX the reason we're not on 24.x is because Robolectric still only has support for API <= 23, so if we go to 24 we lose testing (or we're testing strange zombie code, which is just as bad).

@SUPERCILEX
Copy link
Collaborator

Mockito 2.x came out. Doesn't it support api 24?

@samtstern
Copy link
Contributor

It's Robolectric, not Mockito.

We can try specifying sdk = 23 in the @Config annotation in all of our tests and then upgrading to support 24.x.x and SDK 24, if that works I'd be OK with it.

@SUPERCILEX
Copy link
Collaborator

My bad, I'll try getting Robolectric to play nice tonight.

@samtstern
Copy link
Contributor

Thanks to #349 by @SUPERCILEX I was able to push version 0.6.1 which has all the latest dependencies and should no longer have this issue!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants