Geo intent points to 0,0 instead of linked address

When I click an address in another app (eg. a text from a friend, contacts link, web page), Android offers an app picker to navigate to that destination with Google Maps, Waze, OsmAnd, or, of course, ABRP!

But when I choose ABRP from the list, ABRP ignores the address I've clicked and instead tries to help me drive to a dropped pin somewhere in the eastern Atlantic:

https://i.imgur.com/ylZeee7.png

There are no chargers for the last several thousand miles of that route, I don't have that much range or water-fording ability!

If I manually copy-paste the address in the “Where do you want to go?” search bar, it comes up with no ambiguity.

Behind the scenes, it's an implicit intent link like geo:0,0?q=<address or lat,lng> that tells whatever app you've chosen - including ABRP - to start navigating to that address or latitude,longitude pair. For some reason, it appears ABRP has chosen to use the 0,0 as the destination, not the query string, and every app I’ve tried ignores that 0,0 even if you’ve clicked a latitude,longitude pair.

Running Android 16 (on a Motorola, basically raw AOSP) and ABRP 7.1.4.