Bugzilla – Bug 11638
PIN confusion
Last modified: 2009-09-08 09:31:38 UTC
CAT issue User unable to find PIN due to running SC. Able to duplicate with r5096. Solution was to choose My Music source as mysqueezebox.com. Once done, you can go to Settings menu and see Player PIN.
Err, why is PIN an issue at all with Fab4? This menu item should probably be hidden on Fab4. But why was the user looking for it, is the real question.
Right, there is no PIN on Fab4.
Need more clarification about what the actual "bug" is here. Did the user go to fab4.squeezenetwork.com? If not, when was he/she asked for a PIN? New website will likely need slightly different login flows for PIN vs. non-PIN devices if setup flows are different...
We may need to solve the case where a user does not follow the setup flow we expect and has already installed some version of SC, either the right one or not, before even opening the Fab4 box. Does the Setup flow still work in this case? Will the user ever see a PIN? Should the user be able to find a PIN?
For fab4 and others moving forward (and maybe Duet if possible), the instruction on the website should read something like "go to your squeezebox to create your account." (There is a plan in the works for SN web signup that is specific to the device you own, using radio buttons or some other mechanism, so that we can still support PIN entry for Boom, Classic, SB2 etc.) This should make everyone's lives easier. If you want to create an account, do it on the device. If you want to use the device, create an account on it (or log in to an existing account if you already own another squeezebox). Part of the whole point of on-device setup is to get rid of the PIN entry requirement, and the reason the design is so heavy-handed (not letting you complete setup without account creation) is to eliminate as many of these "special case" signup scenarios as possible. Otherwise the design, implementation and code maintenance is a potential nightmare, and the user experience will suffer as well. To answer Mickey's question, there should be no need whatsoever for the user to ever be exposed to a PIN if using a Fab4 (unless there is some customer-care-related troubleshooting reason or backdoor I'm not aware of).
As for users who have installed SC, I don't see how this should change the flow during setup; someone please correct me if I am mistaken.
PIN has nothing to do with SC.
CAT testers shouldn't have encountered a PIN issue, they were using the wrong site IIRC