Page MenuHomePhabricator

Support 2FA in Wikipedia Mobile applications
Open, Needs TriagePublic

Description

More and more users are going to be using 2FA, and the mobile apps are going to need to support it :)

Related Objects

StatusSubtypeAssignedTask
OpenNone
OpenNone
ResolvedMhurd
ResolvedNone
ResolvedMhurd
DuplicateNone
ResolvedMhurd
ResolvedMhurd
ResolvedMhurd
ResolvedMhurd
ResolvedMhurd
DeclinedNone
ResolvedNone
ResolvedMholloway
ResolvedNiedzielski
ResolvedMholloway
OpenNone
OpenNone
ResolvedBUG REPORTNone

Event Timeline

Seems on Android, this just silently fails; press login, and it tries and doesn't go any further. No error, no feedback

Has work on this been abandoned? In the mobile app, a message asking for the 2FA code is delivered, but there is no input box.

Has work on this been abandoned? In the mobile app, a message asking for the 2FA code is delivered, but there is no input box.

iOS seems fine

712C9823-8021-4D20-96B9-8DC95A301CE2.png (1×750 px, 212 KB)

Android v2.7.50300-r-2019-10-08

T150899androidCapture.png (837×487 px, 98 KB)

@Reedy Thank you for the note but "Fix in alpha" seems far from actually resolving this production issue is there a task to "Release to production" that can be followed?

Maybe @Dbrant or @Charlotte can comment on this?

@Reedy Thank you for the note but "Fix in alpha" seems far from actually resolving this production issue is there a task to "Release to production" that can be followed?

Maybe @Dbrant or @Charlotte can comment on this?

Based on the comments on the other two tasks... There seems to be some confusion

The necessary fix is https://github.com/wikimedia/apps-android-wikipedia/commit/361e389dfd62cc65cf40e5e13b13289c6b51ed89 which is for sure not in a release. I don't know offhand how they track the next release and when it's coming. @Charlotte should know

Thanks Reedy, @Charlotte is there a publicly visible log of current known bugs - the phab bug is closed as new software was written - but there is still a production outage ongoing as it hasn't been released.

Thanks for the comment @Xaosflux - apologies for the confusion. As @Dbrant mentioned in T227925 this was a regression on work that had already been released, which seems to have happened when we did a cherry-picked release a week or so ago. You can always find the latest bugs we're working on in our Milestone boards. The current milestone is N: https://phabricator.wikimedia.org/project/view/4123/

As for a public backlog of bugs that have not yet been allocated to a particular release, those live in the Bug Backlog column of our main workboard.