App occasionally gets ERROR: System Error DETAILS: failed inside handle_json_callback

I only see this on the watch (Vivoactive HR) and never on the simulator. A user has also reported the same.
My device is at SW Version 3.90 (latest update I get from the latest Android Connect IQ app).
I have built a debug version of my app with the latest release SDK 2.3.1 and it still shows this error (there was some indication in another thread that something similar was fixed at this version).
Unfortunately I have no way to capture the web data that is loaded when the error occurs (at least no way I know of), and it happens only every hour or so (which makes for a pretty lousy watch app).

I will send in email the web url needed in the settings for my app currently in the store that will let you see the error, but it is a private web address.



ERROR: System Error
DETAILS: failed inside handle_json_callback
STORE_ID: 00000000000000000000000000000000
CALLSTACK:

<there is no callstack - that is the extent of the CIQ_LOG.TXT>
  • Are older versions of the android connect IQ app available for side loading so I can test at what point this started failing?


    i tried APKs (from apkmirror.com) back to v3.10 and they still show the problem, as does going back to older website.. this looks like a watch firmware bug. if anyone can tell me how to rollback the firmware on my watch (VivoactiveHR) i'd try that too (its a brick until this is fixed anyway).
  • i tried APKs (from apkmirror.com) back to v3.10 and they still show the problem, as does going back to older website.. this looks like a watch firmware bug. if anyone can tell me how to rollback the firmware on my watch (VivoactiveHR) i'd try that too (its a brick until this is fixed anyway).


    I found firmware 3.30 (from before Dec 2016) available on the Garmin site, along with install instructions, and put it on my watch. So far so good, it's trying to auto update but I'm avoiding that so far. No crash yet...
  • Hey Horsetooth,

    I'm sorry that we haven't gotten back to you on this. We don't really do backdates beyond the latest public release because we don't know how old software is going to react to changes that are made for compatibility. I've replied to you in email and will be trying to dig into this over the next couple of days due to some of the limitations.

    Thanks,
    -Coleman
  • fwiw V3.30 (on VA HR) worked great for a day or two, i then let it update (it went directly to latest V3.90) and the crash happened within a very shot time. I've gone back to V3.30 and its working great again...
  • any update on this? alternatively, is there a way to makeWebRequest without decoding the json, and then with a separate call decode the json on the earlier data, so i can log it for debugging?
  • is there a way to makeWebRequest without decoding the json, and then with a separate call decode the json on the earlier data, so i can log it for debugging?

    No, the only thing you have is makeWebRequest(). The JSON parser isn't exposed via the API, and I don't believe there is any way to get the JSON back from the makeWebRequest() call.

  • FWIW I am also seeing this using a ConnectIQ app, the problem only seemed to start occuring after a firmware update on my Vivofit HR.

    I recently did a reset of the watch and it appeared like it fixed the issue for a while however now it seems to have come back with a vengenece

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: Failed invoking <symbol>
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:
    @PC = 0x30000e05
    @PC = 0x30001176
    @PC = 0x10000278

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    I don't own the source to the code so can't help much on that side.
  • FWIW I am also seeing this using a ConnectIQ app, the problem only seemed to start occuring after a firmware update on my Vivofit HR.

    I recently did a reset of the watch and it appeared like it fixed the issue for a while however now it seems to have come back with a vengenece
    ...
    ERROR: System Error
    DETAILS: failed inside handle_json_callback
    STORE_ID: 33643344b2ec4bd4ae0ce9b9ec96a478
    CALLSTACK:

    I don't own the source to the code so can't help much on that side.


    if you (or anyone) mean VivoActiveHR and you want to know how to downgrade the firmware to one that doesn't have this bug (the one I found is many versions old but works for my app, not sure what else it might affect, but I can move mine freely between old & new firmware version), just PM me here and i'll send the info. i'm not sure how long it will take Garmin for a proper fix.
  • I just upgraded my VAHR to the 4.00 firmware release to see if it had a fix for this and unfortunately it does not, still see the same error.
  • Since yesterday after an update of the GCM app I have this problem running on one of my apps. If I deinstall GCM and reinstall an older version, e.g. v3.20.3 (https://www.apkmirror.com/apk/garmin/garmin-connect-mobile/garmin-connect-mobile-3-20-3-release/) the app is running as it should.
    If interested I could send you the source, the json-response which causes the problems is attached.