Open Bug 1335864 Opened 9 years ago Updated 3 years ago

Release users see sync debug options in Settings

Categories

(Firefox for iOS :: Sync, defect)

Product:
Firefox for iOS
Component:
Sync
Platform:
Other
iOS
Type:
defect

Tracking

()

People

(Reporter: adavis, Unassigned)

Details

I have seen a couple of users mention that they see: > Debug: Require password > Debug: forget sync auth state in the release version of Firefox for iOS. I'm assuming this is not intentional. Example: https://twitter.com/TransPride52/status/821403180311388161?ref_src=twsrc%5Etfw
The user had to have tapped on 'Version 6.0 (2)' 5 times to show debug options. They can hide them again by tapping the same text field 5 times.
Debug options are intentionally included in the build, because it's very hard to provide testing builds to users, and practically impossible to get a broken profile from one build to another. Flying blind is not a good alternative. As Aaron noted, these are hidden from users. We could explore additional ways of hiding these or adding indicators of danger The problem described on Twitter is that the user not only revealed the debug options, but tapped one, and that's pretty hard to fix.
Could we make those debug options "expire" after some time (ie, force the user to re-enter that mode periodically)?
They disappear as soon as iOS kills the app in the background, which is quite frequent. Next time you launch Firefox they'll be gone. The issue here is probably that the user was absent-mindedly tapping on the Version field, then put their thumb down on one of the debug options immediately.
Although 5 taps on the version seems pretty unlikely for a user to do... I kid you not, I had these buttons reported to me and then a couple of days later I landed on this Twitter post. So it's happening in the wild to every day users. Can we display a prompt after the 5 taps to confirm? Something like... "Looks like you just enabled Debug mode. Continue into Debug mode?" (Yes/No)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.