Weird behaviour with guide points

🚧 THIS IS A TICKET MIGRATED FROM UPVOTY. The original ticket and comments will be available for a limited time over at:
https://abrp.upvoty.com/b/report-a-bug/weird-behaviour-with-guide-points/
———————————————————————————
When planning a route (for another bug report), I witnessed a strange behavior:
When planning a route with a guide point (s. first screenshot, the guide point only changes the route very little; Plan UUID: 0f1eca47-25d6-4658-a151-8cfa3bbf28b2), the resulting plan does not show the guide point (as it shouldn't), but only start and end. The distance for the (only) leg shown in the plan, however, is the one from the start to the guide point.
This happens on Android as well as on PC (Firefox). I've attached two screenshots for the route without and with guide point.

What is even weirder: When I look at the Android-created plan on PC (as it pops up automatically on refresh), it shows the guide point as way point and thus two legs with two correct distances (no screenshot for this).
The same happens when I reverse the roles of PC and Android.