Proximity alert location names truncated or corrupt

Adding a proximity alert shows the correct name (although not the correct icon)

But once added, it is truncated or corrupted in various ways

Eventually, after trying to remove all proximity alerts the list looks like this...  suggests it's not parsing the file properly

And the iOS Connect app won't display the list of alerts, just shows the running man icon

I have the same issue with the saved location names being corrupt after saving. It has done this with both typing them on the watch or via the GC app. 
SA

Updated to 13.21, hoping this had been fixed... 

Tested add proximity alerts to the Run activity via the iPhone app

Choose a saved waypoint, and set an alert for 1.00 mile:

View the resulting list of alerts

One Test Place has now become One Test Plac

Add another alert waypoint:

One Test Plac has now become One Test Pla  and  Two Test Place saved as Two Test Plac

Delete the second alert point

One Test Pla now becomes One Test P

@Garmin Kevin  - can you raise a ticket for this ?

Also the waypoint icons don't show correctly on the watch - always seems to show the default blue flag

I can confirm that this is the same when using the Android app. Place names are truncated by one or two characters.

Garmin-Kevin can you create a bug report for this ?   

If you follow the above steps you'll see the waypoint names change throughout each change, even if not directly the subject of that change.

Hard to describe how messed up this is...  just went back to check the proximity alerts, and it now shows:

The One Test Place is now blank, and there's a second entry Up_and_over_, which looks a lot like one of my favourited Strava segment names...   How did that get in there ?   No I didn't add it...   it's not one of my waypoints - its a Strava segment.

If I go in to edit 'Up_and_over_' it shows the title as Weird Thin - which is a truncated name of an old waypoint (Weird Thing) I added then deleted a while back whilst testing this...

Is there a global set of waypoints / routes / segments which are referenced by the proximity alert data per activity ?  And the saving / loading has a bug which breaks the data stored and accidentally references other stored objects ?  How else would a Strava segment get into the proximity alert data ?

If you see my older post (above in the thread) it's clear that the parsing of the alert data is very broken on 10.10 - and it's still got some issues on 13.21

1. May we, if necessary, have permission to email you?  yes
2. May we, if necessary, have permission to view/access your Garmin Connect account?  yes
3. In what country do you live?  UK

Hi Garmin-Kevin,

I have your email requesting videos, uploads of the device contents etc, but could you just try the above steps and see if you can replicate this first just using the Garmin Connect app...

1. Create a couple of test waypoints (I used the Garmin Explore app).

2. In the Run activity settings, set up a new proximity alert, confirm and then go back into the list of proximity alerts, see if the full waypoint name is there ?

3. Add another proximity alert, as per step 2, see if the waypoint names have changed again

Regards,

Grb.

A few more examples of corrupt alert data...   even in the main notifications settings, as below:

Then select 'Smart Notifications'

The title of this section is now '%1 Notifications' - something is broken...

Also, inside of an activity I've got alerts which I can't delete, the first one is now called 'Off' - I suspect this is overflow from another field in the file which hasn't been parsed properly...

The 'Off' alert looks like this ... it has no title

Attempting to remove it...

Doesn't do anything... it's still there:

Garmin-Kevin have you tried replicating the issue I illustrated 14 days ago ?

Grb looks like I am still awaiting a reply to my email to you on Nov. 30th.