Reference: | 00541 |
Type: | Issue |
Product: | hHRZone 5.2 (18 July 2017) |
Title: | Data-field Crash after Smartphone update by Bluetooth |
Device: | Fenix 5X |
Priority: | Major |
Raised On: | 04 September 2017 15:51 |
Raised By: | author |
Status: | Open-Development-Ready-Closed |
Description: | |
I've Changed refresh interval from 5 sec to 2 sec by my phone (Fenix 5X was connected by Bluetooth).
|
|
Closed: | 05 November 2018 15:32 (Cannot Reproduce) |
There are 2 Subscribers watching this Case.
04 September 2017 15:59 Aauthor | Case Updated: Description changed from 'I've Changed refresh interval from 5 sec to 2 sec by my phone (Fenix 5X was connected by Bluetooth). After that when HR face was changed - Data-field was crashed - screenshot - https://www.dropbox.com/s/cchhjr1swxgtez1/HR-error-2sec-update-by-sdmartphone.jpg?dl=0 I've tried to change intervasl back - it doesn't work for me :-(' to 'I've Changed refresh interval from 5 sec to 2 sec by my phone (Fenix 5X was connected by Bluetooth). After that when HR face was changed - Data-field was crashed - screenshot - https://www.dropbox.com/s/cchhjr1swxgtez1/HR-error-2sec-update-by-sdmartphone.jpg?dl=0 I've tried to change intervasl back - it doesn't work for me :-( I've installed last value 10 sec back by USB cable via Garmin Express and sync Fenix 5X - it's working now.' |
04 September 2017 17:23 AAdmin | Case Updated: Priority changed from 'Blocker' to 'Major' |
04 September 2017 17:26 AAdmin | Hi, Can you please connect your device via USB and send me the file under GARMIN/APPS/LOGS called CIQ_LOG.TXT Thanks Chris |
04 September 2017 17:30 Aauthor | Here it is log file - https://www.dropbox.com/s/114qppfo9lzebvc/CIQ_LOG.TXT?dl=0 Text ------------ ERROR: Unhandled Exception DETAILS: NONE STORE_ID: 4370b941487441f482d1d10924eb4bfa CALLSTACK: UnexpectedTypeException: Expected Number/Float/Long/Double, given null/Number ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe ERROR: Invalid Value DETAILS: Cannot convert Object to Long STORE_ID: e760f2d0bd3347a2aa037d47b982c8e7 CALLSTACK: @PC = 0x10001270 @PC = 0x10001abe |
04 September 2017 17:31 Aauthor | P.S. Could you check my registration credentials? I've got 2-3 duplicates of each messages login - author@prostabzor.ru |
04 September 2017 17:31 Aauthor | P.S. Could you check my registration credentials? I've got 2-3 duplicates of each messages login - author@prostabzor.ru |
04 September 2017 18:17 AAdmin | Thanks you for the log. Are you using an Android phone? PS I've check the multiple messages, and can't see a problem. Let me know if it continues. |
04 September 2017 18:29 Aauthor | yes, here it is info: -------------------- Phone - Samsung Galaxy S7 Edge OS - Android 7.0 |
10 October 2017 08:23 AAdmin | Hi, Can you try the latest update for me, as I've made some major changes behind the scenes? |
05 November 2018 15:32 AAdmin | Case closed, as unable to repeat. |
This case is now closed