Bug 72 - RSU failed to update the configuration while FreeStyle Libre V1.0 installed
Summary: RSU failed to update the configuration while FreeStyle Libre V1.0 installed
Status: RESOLVED WORKSFORME
Alias: None
Product: TestProduct
Classification: Unclassified
Component: TestComponent (show other bugs)
Version: unspecified
Hardware: Macintosh Mac OS
: Highest critical
Assignee: No one
URL:
Depends on:
Blocks:
 
Reported: 2018-08-21 00:17 EDT by Mohan Kumar Karruppusamy
Modified: 2018-11-14 17:02 EST (History)
2 users (show)

See Also:

Attachments
Log File (85.35 KB, application/octet-stream)
2018-08-21 00:17 EDT, Mohan Kumar Karruppusamy 		Details
json file (3.88 KB, application/octet-stream)
2018-08-21 00:18 EDT, 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 2018-08-21 00:17:53 EDT 
Created attachment 30 [details]
Log File

Steps:

1. Install the Freestyle Libre app on the mac
2. Prepare Apollo Reader in 2.2.13 with 161 configuration settings.
3. Launch RSU and Apollo Reader 2.2.13 and upgrade

Expected: Upgrade should be completed successfully

Actual: Upgrade failed after starting the progress

Expected: RSU software upgraded successfully. Attached the json and log file.
Comment 1 Mohan Kumar Karruppusamy 2018-08-21 00:18:30 EDT 
Created attachment 31 [details]
json file
Comment 2 Brian Roberge 2018-08-22 07:50:22 EDT 
How often can this be reproduced? There is nothing in the log to indicate an issue with frestyle libre.  The reader failed to reconnect after downloading the firmware.  While the RSU is running does Freestyle Libre see the readers?
Comment 3 Brian Roberge 2018-08-24 18:42:21 EDT 
Fixed in build 795
Comment 4 Danny Hutchings 2018-08-24 19:56:37 EDT 
Was not fixed when run on build 795 on Macbook.
Comment 5 Brian Roberge 2018-08-24 22:38:08 EDT 
I am pretty sure this if fixed.  I have run it 10 times and no errors.  I suspect that the failure on 8/24 was a different issue.  Will have a better idea when I see the log
Comment 6 Danny Hutchings 2018-11-14 17:02:17 EST 
Fix seen in build 905