This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Connect App Crashes when Adding Gear for the First Time

My apologies if this has been posted already. A quick search didn't come back with anything.

I found what I think might be a minor bug which consistently causes Garmin Connect to crash. It happens when a new activity is uploaded and I try to add gear for the first time. (Subsequent updating of gear works fine)

Garmin FR235 v4.6
Samsung Galaxy S6 (Verizon Wireless)
Android 6.0.1
Garmin Connect 3.6.0.1

Steps to reproduce my issue:
1. Sync/Upload running activity from my FR235 via my phone.
2. Go into the activity and select "Add/Remove Gear"
3. Select a pair of shoes.
4. Click on the icon "<- Add/Remove Gear" to go back to the activity.
5. Watch the spinning icon as the activity tries to reload.
6. App crashes.

I've tried reinstalling the app with no success. It's not a deal-breaker, just a minor inconvenience.

I wonder if others are experiencing this issue, and again, I apologize if this has already been posted.

0 ASmugDill over 8 years ago

4. Click on the icon "<- Add/Remove Gear" to go back to the activity.
5. Watch the spinning icon as the activity tries to reload.
6. App crashes.

Interesting. I got to step 5, and got the spinning icon that doesn't seem to know when to quit, built the app did not crash even after several minutes. Eventually I just backed out of the activity using the ← in the top left corner, and when I went back into the activity, the previously selected gear is shown against it.

I'm using FR235 firmware v4.60, and Garmin Connect Mobile app v3.6.0.1 running on Android 5.0.2.

0 scottj2 over 8 years ago

Yeah, I've gotten so that I just back out of the activity altogether before it crashes. In my case, if I leave the spinning icon going for awhile, it eventually shuts down the app. I'm glad you're able to somewhat reproduce it, without the crash anyway.

A minor inconvenience, but a bug nonetheless.

0 scottj2 over 8 years ago

Quick update: this issue seems to have been fixed in version 3.8.