Edge crashes when two apps use AntPlus.BikePower(Listener)

o The Environment:
- Edge 820 (6.20), Edge 1000 (12.00)
- Eclipse Neon.1a Release (4.6.1) on Windows 10
- ConnectIQ SDK 2.2.3

o A detailed description of the issue
I am working on a few data fields that use the AntPlus.BikePower(Listener) classes in order to access advanced metrics of paired power meter. While they all work in isolation (though there still seem to be some irregularities with the callbacks so I am accessing the data through the BikePower object), as soon as I have two of them simultaneously installed and in use, the device becomes unstable and crashes either immediately after selecting the second data field or later during (the next or a later) boot up. In some cases the device did not boot up properly anymore. (The boot issue was resolved after starting with lap button pressed to enforce storage device mode and then delete the apps folder, but that of course doesn't solve the problem.)

o Steps to reproduce the issue
I have a relatively minimum project that just shows power from the BikePower object (in order to make sure it's working). I have made a copy of that data field that displays the same but in different font color to make distinguishable. Both work in isolation but system becomes instable when both run simultaneously.

o A code sample that can reproduce the issue (in email only if preferred)
In email.
  • Hello,

    Thank you for reporting. I would be happy to investigate the issue. Please send your project(s) to [email][email protected][/email] in .zip format.

    Thanks,
    Coleman
  • Thank you for sending your projects. I was able to reproduce this and get an error log to the Edge 1000 team for the device crash. I was also getting an "IQ!" crash which could be something in the source code, but that should not be causing the device to crash. We will do a little more investigation and try to keep you posted.

    Thanks,
    -Coleman
  • Thanks for looking into this. Will be waiting then here for some updates.
  • Any updates on this? Got feedback from a user who ran into trouble possibly because of this issue.

    I wouldn't have published the apps on the store if I had noticed this before but now that they are out, removing them doesn't seem a good option either as that will prevent me from providing future updates. If no solution is possible in the near future, I might decide to replace by a dummy data field that does nothing so that it would at least prevent the nasty behavior - even if that could be annoying to users who didn't face any problems.
  • Hey,

    I was able to confirm that the device team is still working on this. It looks like this might have a couple of different parts that are causing the issue and one has been addressed. Unfortunately no definitive eta at this point.

    Thanks,
    -Coleman