Closed Bug 1177002 Opened 10 years ago Closed 7 years ago

Enabling developer mode is not clear enough that it will wipe everything

Categories

(Firefox OS Graveyard :: Gaia::Settings, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Settings
Platform:
ARM
Gonk (Firefox OS)
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WONTFIX

People

(Reporter: hub, Unassigned)

Details

(Keywords: foxfood)

Enabling developer mode is not clear enough that it will wipe everything Including the photos taken. This is bad given that we are gonna give that to hundreds of user and that they can do it too. Solution 1: Don't require developer mode Solution 2: Don't wipe Given that we still lack proper backup tools.
The cherry on the cake is that I didn't have RC1 so on reboot it didn't tell me I had developer mode. So I lost everything for nothing. GREAT.
The wipe is done to protect the phone content because phones may not be protected by a PIN. Well, my phone is protected by a PIN so I think developer mode could have asked for the PIN and not wipe the content.
Keywords: dogfood
Keywords: dogfood → foxfood
I got bitten by this too: I set up a bunch of stuff, and visited the hackerplace - it said I should have the dev mode on, and brought me to the enabling UI. But I can't recall any warning about wiping the data. It restarted the phone and I lost all my settings.
Could you supply the build id please?
Flags: needinfo?(hub)
No because I have gotten a few OTA since. So I no longer have that information. I'm sure it is still happening, and I'm not willing to even try. In the retrospective I actually raised this problem because it goes beyond wiping data. It is also a barrier to contribute (test) as the user would have started to use the phone. And given the lack of backup / restore....
Flags: needinfo?(hub)
The reason why I ask is there's a warning overlay with huge capital letters stating that it will erase everything. You have to tap 9 times in order to activate the developer mode. I think you may have been on an earlier build prior to that landing and that caused the issue... I wanted to be sure.
Status: NEW → RESOLVED
Closed: 10 years ago
QA Whiteboard: [foxfood-triage]
Resolution: --- → WORKSFORME
Yes there is. It doesn't matter. It shouldn't happen. The problem is deeper than that. The justification I was told is that "if your phone isn't protected by a passcode we need to do that for security". But I had one. Also it is a HUGE barrier to adoption. People get phone. People start using phone. People get told to enable developer mode. Either they erase, or they actually read the warning and said what I would say "(*&^( that sh*t" and pass, never using the features that require the developer mode. Also people never read warning messages. I didn't. I am not the person to have had that issue.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
Also you don't even realize the potential for a prank.
The title suggests that the warning was not clear enough. Losing data sucks, I'm sorry that you didn't see the warning dialog state that. I did find a bug where the wrong dialog comes up for settings; bug 1184806. Having said that, it still states that data is going to be erased. If you didn't bother reading the message of tapping 9 times, I'm not sure if having to place in your pin would make that much of a difference? Also going with your suggestion, what about the case of those who haven't placed a passcode on the device? What do we do in that scenario? Perhaps the root issue is that we shouldn't clear data, in which case I think bug 1182777 has that clearly in the title.
Flags: needinfo?(hub)
No. The PIN would be to do it WITHOUT wipe since the wipe is because the phone might not be protected by a PIN. Mine was. Always is. Yes solving bug 1182777 (filed AFTER this one mind you) should be a reasonable solution since the problem is it wiped data. WORKSFORME indicated that wiping the data was part of the spec. Will then the spec is wrong. As for not bothering to read the message, well, I don't bother reading the zillions of EULA that pops up. This is part of computer life now hence we shouldn't even rely on this.
Flags: needinfo?(hub)
I still don't understand how a pin would help. The question was if someone doesn't have a pin, how would your UX work? You would force the end user to create a pin first? The point of the reset data was so that a hacker couldn't turn on these prefs that could take over your phone without you knowing. It would effectively destroy the data. This was part of the spec because of the loose privileges that the setting has.
First why would it delete when there is a pin set instead of asking for the pin. There, we have already have an improvement. Two I believe we shouldn't have a feature that delete user data, at not a feature that is about resetting things. This is a source for bad pranks and such. Just as a reminder of the damage: pictures where gone because the camera default to internal storage. Elsewhere it is being discussed that we should not actually rely on most of this for what we want to do - various bugs are being work around. Also if you really want a NI on how the user interaction should be for that complicated problem then NI somebody who actually work on UX. But if we start by not doing a wipe when the user want to enabled developer mode AND the user already protect the phone by a pin, it would already be a hell of an improvement.
Flags: needinfo?(hub)
If your fear is of pranks to delete data, there is a factory reset option in 2 different places in the settings menu. That is no more difficult to get to than the Hacker Place apps.
True. And it doesn't ask for the passcode either. I'll file a separate bug for that.
See bug 1188541
since it confuse people, here "PIN" and "passcode" are used interchangeably to designate the code that lock the phone. Since as of today only a 4 digit PIN is possible.
We removed the need for dev mode. This should resolve the issue of not needing to wipe.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 9 years ago
Resolution: --- → DUPLICATE
Developer mode controls more things than just access to extensions. It also enables full DevTools access. Bug 1196963 seems to only affect extensions, so I believe this bug is still valid.
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Firefox OS is not being worked on
Status: REOPENED → RESOLVED
Closed: 9 years ago → 7 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.