New GC Version: 16.2.0.11 - phantoms, empty activities

Same here. Fenix 3 / GCM

Same here. Unknown phantom activities. Fenix5 FW 6.55beta and GMC v3.2.0.1 on Android. It started yesterday. It happens every time after sync in GCM app.

And one more annoying thing: Is it so hard to show the correct image and name of the watch (Fenix3).

default-device.png -> fenix-3.png
AND
Rubber Ducky -> fenix 3

Is it really so hard??!!

Same problem for me, multiple phantom runs. Fenix 3 with Beta 6.55

even worse: all the phantom activities are pushed to Strava...


Have to delete loads of activities on all my platforms...

Same her :-(
Could it be connected to the new insights features?

I did enabled it, but now I have tried to disable it again to see if this helps.
Edit: that didn't help, just got a new Phantom activity...


F3, FW6.55 + FW6.63 (Phantom activities in both versions)
GC 3.2.0.11 on iPhone 6.

-Thomas

Same as everyone else. Saw it on 6.55 and 6.63 betas for fenix FWs.

I am iOS and running latest GCM.

I haven't tried syncing via Garmin Express to see if it would be possible to isolate the problem to the GCM sync versus GC Web...

Only turning off BT on my fenix seems to stop it for now.

Hey, at least I got a Kudos on one of my random activities around midnight.

Hi,

yesterday a new version of GC has been released - Version: 16.2.0.11.
Suddenly, I got some phantoms, empty activities.

It's a bug of GC?

I have Fenix 3 watch with beta FW, but looks like a GC issue, it's first time with this abnormal behaviour of GC.

Please report, especially if you are users of other than F3 watches.

Had the problem with 6.55 beta, multiple erroneous activities, 11 in my case.

just did a 30' run, uploaded directly via wifi once I got back home (no smartphone app involved), found 37 empy/phantom activities + the one correct activity
I have a fenix 3 with the latest beta fw 6.55

Seems like this is an issue with Fenix. I have a vivoactive and am not seeing this. Anyone else with a different device?

Same here, also using a Fenix 3. Anybody spotted any reports of this happening with other devices? I haven't.

It looks a bit like a problem with Connect itself (even if it's specific to the F3); it's being reported with different F3 firmwares and with both Android and iOS, and only started happening several days after the last firmware and Garmin Connect Mobile versions came out.