Bug 111 - 1026 - Incompatible Reader error displayed when the user disconnect and connect before update starts
Summary: 1026 - Incompatible Reader error displayed when the user disconnect and conne...
Status: VERIFIED FIXED
Alias: None
Product: TestProduct
Classification: Unclassified
Component: TestComponent (show other bugs)
Version: unspecified
Hardware: PC All
: Highest major
Assignee: No one
URL:
Depends on:
Blocks:
 
Reported: 2019-01-03 23:29 EST by Mohan Kumar Karruppusamy
Modified: 2019-01-07 21:19 EST (History)
1 user (show)

See Also:

Attachments
Screen shot - Incompatible Reader (176.63 KB, application/pdf)
2019-01-03 23:29 EST, Mohan Kumar Karruppusamy 		Details
Screen shot - Incompatible Reader (176.63 KB, application/pdf)
2019-01-03 23:30 EST, Mohan Kumar Karruppusamy 		Details
Log file (194.89 KB, application/pdf)
2019-01-03 23:30 EST, Mohan Kumar Karruppusamy 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Mohan Kumar Karruppusamy 2019-01-03 23:29:14 EST 
Created attachment 87 [details]
Screen shot - Incompatible Reader

When the user disconnect the reader and connect it again before upgrade starts, Incompatible Reader error is displayed.

Tested in - MAC (1026-157-2.1.2).

Steps

1.Connect the reader and launch the 157 installer
2.Navigate to Ready to update screen and click Next
3.Immediately disconnect and connect the Reader (need to do before progress bar starts)
4.Click on Try Again on the Update Unsuccessful dialog and Click Next on Welcome Screen and again Click Next on the update screen (please perform all the steps quickly)

Actual: Incompatible Reader error screen is displayed.

Expected - Update progress should start

Screen shots and logs attached.
Comment 1 Mohan Kumar Karruppusamy 2019-01-03 23:30:00 EST 
Created attachment 88 [details]
Screen shot - Incompatible Reader
Comment 2 Mohan Kumar Karruppusamy 2019-01-03 23:30:26 EST 
Created attachment 89 [details]
Log file
Comment 3 Brian Roberge 2019-01-07 15:19:20 EST 
Fixed in build 1028
Comment 4 Mohan Kumar Karruppusamy 2019-01-07 21:19:51 EST 
Verified the issue on 1028 (2.1.2 - 157) and working as expected.