Connect IQ data field: Flexirunner (version 6.1.0, built with Connect IQ SDK 2.2.3 - https://apps.garmin.com/en-US/apps/c...8-c93edadabe3d)
Garmin device: Forerunner 235 (firmware 7.10)
Mobile device: Google Nexus 5X (Android 7.1.2, 5 January 2017 security patch level)
Mobile app: Garmin Connect Mobile for Android (version 3.13.1)
Eclipse version: Neon.2 Release (4.6.2), Connect IQ SDK 2.2.3
Existing forum threads discussing the issue:
https://forums.garmin.com/showthread...ith-data-field
Problem:
When editing an activity recorded with this data field (native Run mode) in Garmin Connect Mobile, upon pressing the back arrow in the top left to save the changes (e.g. activity name) and return to the activity overview, a small toast popup appears with the message "An error has occurred.", and the changes are not saved. It is possible to edit the name or make other similar changes using the Garmin Connect web interface.
Steps to reproduce:
1. Record an activity with the Connect IQ data field, Flexirunner active. Additional FIT fields are recorded.
2. View the activity in Garmin Connect Mobile, tap the three dots to open the menu and choose 'Edit Activity'
3. Tap Name and edit the activity name, tap Done
4. Tap the left-facing arrow in the top left corner of the Edit Activity page to save the changes and go back to the activity overview
5. Observe the "An error has occurred." message, and confirm that the activity name remains unchanged
6. View the activity in the Garmin Connect web interface
7. Click the pencil icon next to the activity name, edit the name and click the tick icon to save the changes
8. Observe that the changes are saved without error. Confirm that the new activity name is also visible in the Garmin Connect Mobile app.
Additional information:
I am able to edit the activity name fine with activities that are recorded without Flexirunner, but are recorded with other data fields that implement FitContributor (e.g. Stryd Power).
However, I am unable to see that it is a bug in my data field. The FIT contributed fields seem to work as expected, and as far as I can see, are coded correctly. I first appealed for information in the above mentioned thread before filing this bug.
Other users have reported the issue with another data field of mine, which shares some code with Flexirunner (Running Economy, https://apps.garmin.com/en-US/apps/2...d-2438f0b996ed). It wasn't specified whether they used the iOS or Android GCM app.
Source code for Flexirunner is available here: https://github.com/imgrant/FlexiRunner
