alphensebezorger
I don’t believe OsmAnd can be blamed for this routing issue. Before today, there actually was a mapping error at this location. The reported detour was caused by this mapping error, not by a bug in OsmAnd or the routing engines.
Before today’s edits, the northern end of the bridge connected to two cycleways (1), which were both tagged with foot=no, effectively creating a dead end for pedestrians crossing the bridge. The footways and stairs added today should have solved the issue.

I used Overpass Turbo (2) to study the situation before today’s edits.

I feel the related Github issue for OsmAnd (3) can be safely closed, because the mapping error explains the observed detour.

(1) https://www.openstreetmap.org/way/532093510/history and https://www.openstreetmap.org/way/532093511/history
(2) https://overpass-turbo.eu/s/1bQQ
(3) https://github.com/osmandapp/OsmAnd/issues/12947
