Function Transaction.set() called with invalid data. Unsupported field value: undefined (found in field waypoints.14.name.key in document paths/nUgNKlkyzH4LJpfpyP9w) - Code:invalid-argument
(Debug information, this helps us helping you, you can remove this if you don’t want to share this data, it should not contain any personal or sensitive information)
Device: samsung - SM-G970F - Android: 12 - WebView: 135.0.7049.111
Screen: 360 x 760 px - 3dppx
What about the 14th waypoint?
Are you sharing the route with us?
Nothing special, I would say:
Here is the link to the route:
UPDATE:
After opening the link I just posted above, I could save the route. 
This of course solved my problem - still, developpers should have a look what caused the problem.
If I see this correctly, you have turned a favourite into a waypoint, right?
Please place the waypoint next to the favourite. Maybe then it will work.
No. I picked all the WP by tapping directly on the map. WP14 was a Lookout POI, as shown in my screenshot. I did not assign or change any of the WPs names manually. Most of the WPs are POIs, some of the SPs I put on the street to enforce a specific road.
Please place the waypoint next to the Lookout.
the Waypoint list has an error at WP 14 (see above), so I think, you have to move thist point. Just a try… 
NOW you can save your route! 
I think this POI is somehow corrupt. If I move WP14, everything is ok. If I add the same POI
as a new SP, the problem reoccurs. Is it the same for you?
Here is the linK to the POI:
Schau Dir diesen Ort auf kurviger.com an:
[object Object]
https://kurviger.com?overlay=location&ovd=osmId%3D6321412704%26type%3Dnode
Can’t confirm that.
You can save this route as well …
For me, two closest lookout POIs (one 1500 to the north and the other 1500 south-south-east from it) create exactly the same problem.
Time to kill the app and retry.
After restarting the app, the problem reoccurs.
That apparently helped to prevent the problem from reappearing.
Thanks @Viola .
Delete the whole thread?
Robin is grateful for any information, so no deletion.
Thanks we’ll have a look and see what we can do to prevent this error. Unfortunately, from time to time there are errors like that that are very hard to impossible to reproduce.
