Acknowledged
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

        ...

}

Parents
  • 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.

Comment
  • 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.

Children
No Data