Bug 68

Summary: SIT_TC9_TS20:MAC installer firmware upgrade does not update firmware using try again button (Reader with activated sensor)
Product: TestProduct Reporter: Sahil Parbhaker <sahil.parbhaker>
Component: TestComponentAssignee: No one <sysadmin>
Status: VERIFIED DUPLICATE    
Severity: normal CC: brian.roberge, kuanshen.an, mohankumar.karruppusamy
Priority: Highest    
Version: unspecified   
Hardware: Macintosh   
OS: Mac OS   
Attachments: Log file on MAC

Description Sahil Parbhaker 2018-08-14 16:46:56 EDT 
Mac: Retrying the update on the reader for build 155 doesn’t seem to work. On disconnecting the reader during update, there is no “Update Unsuccessful screen" on 2nd attempt of retry

Steps:
1.Launch MAC installer
2.Connect reader with sensor activated
3.Go to the step update screen and let the installer proceed to update stage
4.Disconnect reader in the middle of update. A message appears "Update Unsuccessful" with PROMPT displaying try again button
5.Press try again button on the message prompt
6.Proceed to firmware update screen


Actual Results:
The installer is stuck and does not proceed with update.
The installer has to be force quit if reader is disconnected 2nd time during the update process . On subsequent attempts the installer shows “update unsuccessful screen” using try again button

On re-launching the installer again, the update seems to proceed to its normal course but only after relaunch does it fail to launch

Expected:
Firmware should proceed with the update during 2nd attempt after relaunch
Comment 1 Sahil Parbhaker 2018-08-14 17:09:22 EDT 
Created attachment 25 [details]
Log file on MAC
Comment 2 Sahil Parbhaker 2018-08-14 17:11:21 EDT 
LibreUpdate_749_155.dmg
Comment 3 Sahil Parbhaker 2018-08-14 17:12:43 EDT 
Platform macOS Sierra
Reader firmware update file :LibreUpdate_749_155.dmg
Comment 4 Brian Roberge 2018-08-15 18:24:51 EDT 
Fixed in build 770, we were not saving language level so if we restarted we could not send down commands that needed it.
Comment 5 Mohan Kumar Karruppusamy 2018-08-22 00:33:37 EDT 

*** This bug has been marked as a duplicate of bug 63 ***