859462 - [B2G][Settings][Bluetooth]: If the user does not enter a pin for a bluetooth pairing, but has tapped the pin entry field, then the user will be unable to leave the "Unable to pair devices" screen.

Status: VERIFIED DUPLICATE of bug 859596

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

Description

[J Zimbrick]

Attachment: Screen displaying lack of confirmation options after timing out when pairing bluetooth devices.

Description:
  If the user enters the dialogue to sync a bluetooth device that requires a pin and lets the connection time out, then there will be no option to leave the screen displaying "Unable to pair devices". The options seem to either be hidden behind the number pad or are removed completely.
  
Prerequisite:
 Have a bluetooth device that asks for a pin to connect ready to sync. (This was found with a Jabra SP200 headset.)

Repro Steps:
1. Update Unagi device to build 20130408075751.
2. Open the Settings app.
3. Select Bluetooth.
4. Enable bluetooth and attempt to sync to a bluetooth device (other than another phone.)
5. A prompt asking for a pin to connect to the device will appear, tap the number entry field to bring up the number pad and wait for about 1 minute for the connection to time out.
6. Observe that another message will appear stating "Unable to pair devices", but there is no option to go back to the previous menu, only the number pad. Pressing the home button is the only way to leave this screen.

Actual:
  After letting the bluetooth sync time out, the user has no option to return to the previous settings screen, instead only the number pad is displayed.  The only way to leave this screen is to press the home button and open the settings app again.

Expected:
  After letting the bluetooth sync time out, the user is given the option to return to the previous bluetooth settings screen.

Environmental  Variables:
Kernel Date: Dec 5
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/24b27125d907
Gaia: b973e66f328d8e09e364654e17ddab9f2c938bc4

Notes:
Repro frequency: 100%
Q Analysts Test Team Priority: Pri 3

See attached screenshot for example of the issue occurring.

This issue does not seem to occur when attempting to sync with another phone.

Comment 1

[Chris Kreinbring [:CKreinbring]]

Also reproduces on the Inari 1.0.1 version 20130415070202
Kernel Date: Feb 21
Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/2b44e2c40cc1
Gaia: c79e761bae4d92f329154c64159f4f5c8eb49c9e

Test Suite Name: Firefox OS Daily Smoketest
UCID: Daily Smoketest
Link to failed test case: https://moztrap.mozilla.org/manage/cases/?pagenumber=1&pagesize=20&sortfield=created_on&sortdirection=desc&filter-id=6071

Comment 2

[Shelly Lin [:shelly]]

Attachment: Patch of bug 859596

The problem seems to be fixed after applying this patch. Likely a dup of bug 859596?

Comment 4

[J Zimbrick]

Verifying as duplicate...