Acknowledged
3 months ago
CIQQA-3057

wakeTime problem on GPSMAP 67 / 67i: 8.90

Error Name: Unhandled Exception
Occurrences: 1
First Occurrence: 2024-12-31
Last Occurrence: 2024-12-31
Devices:
    GPSMAP® 67 / 67i: 8.90
App Versions: 1.7.0
Languages: eng

using Toybox.UserProfile as USP;

function getUSRPROFILE_data()
{
    var
    s             = USP.getProfile();
    if(s != null)
    {
        var WakeTime     = s has :wakeTime  ? (s.wakeTime != null ? (s.wakeTime.value() / 60) : null)     : -1;//ERROR

        ...

}

_psx_
  • 3 months ago

    Since pasted quotes with username links don't render properly here, for the benefit of anyone who hasn't seen the original posts:

    forums.garmin.com/.../1902590

    https://forums.garmin.com/developer/connect-iq/f/forum-about-the-forum/404589/re-acknowledged-bug-reports

  • 3 months ago

    > Also, the "Acknowledged" state is not meaningless

    To be clear, I didn't mean that the acknowledgement of *this* post is meaningless (and it's clear that it's been assigned a ticket number, as opposed to the old post which does not have a ticket number). Sorry if I wasn't clear on that.

    What I meant was:

    - the *original* bug report from 2023 was acknowledged a month ago

    - this was part of the wave of acknowledgements for old bug reports, that as previously discussed, was part of some of sort of internal bookkeeping action, and did not necessarily mean that they were actively being investigated

    i.e.

    https://forums.garmin.com/developer/connect-iq/f/forum-about-the-forum/404582/should-we-be-optimistic-about-the-acknowledgements/1902590#1902590

    [quote userid="277093" url="~/developer/connect-iq/f/forum-about-the-forum/404582/should-we-be-optimistic-about-the-acknowledgements/1902586#1902586"]I apologize about the email spam as that was not my intention. All issues get acknowledged and transferred to our internal tracking system for triaging and prioritizing. The forum ticket status got out of sync with our workflow of transferring issue. All old forum tickets were set to the "in review" status despite having already been acknowledged in the past. [/quote]

    forums.garmin.com/.../re-acknowledged-bug-reports

    [quote userid="187638" url="~/developer/connect-iq/f/forum-about-the-forum/404589/re-acknowledged-bug-reports"] since both  and you recommended opening new tickets if an old one that was acknowledged haven't been fixed yet[/quote]

    [quote userid="2116" url="~/developer/connect-iq/f/forum-about-the-forum/404589/re-acknowledged-bug-reports/1903046#1903046"]

    Perhaps we should have just left all of those old reports as there were. I understand your perspective, but what I was attempting to communicate was that the acknowledgement of these old issues was benign—in truth they had already been acknowledged at some point in the past—I didn't want people to assume that these were now getting some special attention.

    The specifics are that roughly a year ago, someone at Garmin with admin rights to the forums removed one of the statuses we were using in our bug reporting tool to indicate that we had reviewed and created an internal ticket to track the bug report. The result was that all of these forum reports reverted to the default state and made it appear that they had not been dealt with. I immediately had the state re-added, but there was no way to mass undo the status changes.

    [/quote]
  • 3 months ago

    This is the ERA log from PSX-8. You can install the app on any compatible device to see how it runs. Next on gpsmap and see if it is compatible - only this device produces crash and type of device suggests that profile is not needed so maybe somebody returns something not consistent with the specification. 

    It's rather impossible to provide more information thana piece of real source code... So you can prepare your own app and check if also crash on gpsmap - unfortunately I don't haven any. 

    It can be a problem with the corrupted profile/device/etc. one of user but I rather don't plan to additional checking.

  • 3 months ago

    Since this is an app crash, we'd probably need more information on where this is occurring and we'd like you to could confirm something is not getting passed a null value. I agree with Flowstate's assessment that, "...wakeTime is unexpectedly/incorrectly something other than a Duration (maybe a Number?), which is why the call to value() would crash. (As flocsy mentioned, this is probably the only possible place for the crash to occur)." I don't think anything in the supplied code throws an exception, so any other details you can provide would be appreciated.

    Also, the "Acknowledged" state is not meaningless—it means that we've created a ticket for investigation. Since we don't have better tools available for external bug tracking, we've automated the intake process and are posting back our ticket number as a comment for reference. For now, we do not plan to report back status or alert when these items are fixed because it is impractical for us to do so. I hate to put it that way, but it's often difficult to track issues over time, particularly when they are problems that span into product firmware or a mobile app. That said, I do not have direct authority to prioritize issues, so an acknowledged issue unfortunately does not indicate a fix is imminent.

  • 3 months ago

    But today we have the ticket CIQQA-3057, maybe somebody copy/paste this code an check it.