• Replies 14 replies
  • Subscribers 20 subscribers
  • Views 829 views
  • Users 0 members are here
Options
Related

Can a not loaded IQ datafield crash a device?

mcinner1
2 months ago

I have a question for the developer community:
Is it conceivable that an Edge device crashes and the reason for this is an IQ data field that is not loaded at all?

A user of my data field MapFields claims:
His Edge 1040 crashed after several deviations from the route and the associated route recalculations. This is despite the fact that my data field is only installed in a different activity profile and has not been loaded in the profile currently in use. If he uninstalls my data field, the route recalculation works without any problems.
The Garmin support he contacted does not rule out his theory.

The data field does not provide any ERAs and I do not receive any complaints from other users.

I would really like to know if any of you have already encountered such a problem: an installed but not loaded IQ data field crashes a device?

  • 2 months ago

    Devs and end users have posted a few times in the past about instances where a CIQ data field that was installed in *another* activity profile seemed to be active during an activity profile where it’s not installed, or even while a Connect IQ device app is running.

    They were able to notice this because the data field in question (such as Stryd Zones) would record developer FIT fields, which would cause the fields to unexpectedly show up in the Connect activity page, as well as the app information (name, listing image, and link).

    So I don’t think it’s too crazy to surmise that:

    1) your data field is actually running when it shouldn’t be

    2) because of 1), their activity is crashing

    I think it would be interesting to see what would happen if the user installs your data field in the actual activity profile that they use (after uninstalling it from all other profiles). Does the activity still crash? If so, and if completely uninstalling the data field from all profiles makes the problem go away (as you said), then it’s almost certain that your app is the culprit.

    Ofc that doesn’t mean it’s “your fault”, but it’s more likely that there’s some issue in CIQ or the device that should be reported. (Maybe an issue where the activity crashes due to the combined memory requirements of your app and route recalculation?)

  • 2 months ago

    Does your DF have the background permission?  If so, onAppInstall/onAppUpdate might be running before you've added the DF to an activity

    You won't see this in the sim,

  • 2 months ago

    Thank you both for your answers.

      that’s interesting. I cannot imagine how the field can run in an not active profile - maybe if the user changes the profile after having loaded the datafield in the first profile? That may be…
    For doing tests, I would have to add a test contribution. Maybe I will ask the user.

      Yes, all my datafields have a backgound permission to fetch the device temperature. But - as I say - all of my datafields have it. It must be a special singularity in this case… But… maybe…
    For doing teszs, I would have to omit this feature.

  • 2 months ago in reply to mcinner1

    Those two only run when a DF is first installed or updated, so not every time you turn of the device

  • 2 months ago in reply to jim_m_58

    I‘ve sent the link to this thread to the user involved, and he send me a correction. (Apparently I#ve got him wrong):

    Just a quick correction - this is not a crash, neither of the data field nor of the device itself. Rather, there was a “malfunction” in the turn-by-turn instructions, which stopped for too long and the next messages simply did not appear ...

    So, sorry for having you misinformed…

    I think this new correct information makes it even more difficult to find a connection to the datafield...

  • 2 months ago in reply to mcinner1

    So if I understand correctly there are 2 datafields: A and B. B is your's it's installed on the device, but not in the currently active profile. A is installed in the current profile. I wonder though: is A made by you? 'cause this more and more sounds like misunderstanding ove rmisunderstanding. Some users send me either bad reviews ormessages via contact developer about other people's apps...

  • 2 months ago in reply to flocsy🤠

    No, there is only datafield A in focus. And A is my datafield MapFields.

    The user reports:
    He installs datafield A and sets it only in Profile 1.
    And now - if he rides with Profile 2 - and there my datafield A is not even set - he has problems with Garmin‘s native turn by turn navigation. 
    When he uninstall/deletes my datafield A from the device, turn by turn navigation works without problems.

    I don‘t know what happens, if he rides on Profile 1 - with datafield A… I assume, he would report the same problems.


    Strange…

  • 2 months ago in reply to mcinner1

    So it sounds like the background app is a good direction to follow. It's certainly a huge Garmin bug if this is what happens. Regardless if there is or isn't a bug in your app, it shouldn't cause this

  • 2 months ago in reply to flocsy🤠
    flocsy🤠 said:
    So it sounds like the background app is a good direction to follow.

    For what it's worth, Stryd Zones is one of the data fields that was reported to run when it shouldn't and it does have the background permission.

    You mentioned that you had a problem where a CIQ data field (of yours?) would run while a CIQ device app of yours was running. Did the data field have a background process?

  • 2 months ago in reply to FlowState

    No background process. Only 2 permissions: FitContributor and UserProfile