Bug 88 - Build 903 - Few information missing in the log file when disconnects the reader middle of upgrade
Summary: Build 903 - Few information missing in the log file when disconnects the read...
Status: RESOLVED WORKSFORME
Alias: None
Product: TestProduct
Classification: Unclassified
Component: TestComponent (show other bugs)
Version: unspecified
Hardware: All All
: Highest critical
Assignee: No one
URL:
Depends on:
Blocks:
 
Reported: 2018-11-10 00:41 EST by Mohan Kumar Karruppusamy
Modified: 2018-11-15 19:18 EST (History)
2 users (show)

See Also:

Attachments
Failure (638 bytes, application/octet-stream)
2018-11-10 00:41 EST, Mohan Kumar Karruppusamy 		Details
Log Files (115.19 KB, application/x-zip-compressed)
2018-11-15 19:18 EST, Danny Hutchings 		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 2018-11-10 00:41:27 EST 
Created attachment 53 [details]
Failure

Few information missing in the log file when disconnects the reader middle of upgrade

Steps
Connect the Reader 1 to PC 1/Mac 1
Launch the Application and navigate to Ready to Start Update screen
Click Next button on the Ready to Start Update screen and ensure that the Update is in progress.
Disconnect the Reader 1 from PC 1/MAC 1 when update is in progress.
Verify the log file on the following path

Open ‘Status.json’ file created at 
C:\Users\[youraccount]\Documents\( on Windows) or /Users/[youraccount]/Documents ( on Mac)

Expected:

Log file should write more information like previous firmware version, Langset, Marketlevel,Serial Number, UOM, Error Details etc.

Actual: Log file does not have any information if the upgrade interrupted.

Attached the log files.
Comment 1 Brian Roberge 2018-11-13 20:54:00 EST 
Fixed in build 905
Comment 2 Danny Hutchings 2018-11-14 17:49:52 EST 
As of build 905, Mac works as expected. 

Windows however is no longer creating the JSON during these failures. Brian is looking into it.
Comment 3 Brian Roberge 2018-11-14 18:32:49 EST 
I can't duplicate this.  I see the status.json file in the Documents directory with the correct information.  Since it works for me and on the Mac I suspect a permissions problem.  Could you attach the log from AppData\Local\Temp\ADC_FUAlog?
Comment 4 Danny Hutchings 2018-11-15 19:18:51 EST 
Created attachment 59 [details]
Log Files

Here are the logs.