This seems to be more of a Google Maps issue than one with OLC - but I'm really not sure how to condense all of this into an in-product bug report and still be understood. I hope this reaches the right people anyway. :)
Basically, what I'm doing in an Android app is to
1. Generate the plus code for a location,
3. use this URL to create an Intent that will open the Google Maps app on the device.
This generally works fine, but every once in a while, the destination will be in a completely different place than it should be. For example, starting the Maps app for Android with the random plus code 9F4C4R3C+GG as destination, instead starts a navigation to a nearby point of interest named "Moved by GG" (Place ID: ChIJC-gFx1htukcRAwAfwCT0x5s). The fact that both the plus code and the place name end in "GG" is probably not just a coincidence - apparently, the random place name is matched before the destination search string is identified as a plus code?
I assume that the Android app behaviour only works like this if the user's location itself is somewhere nearby. If a random location between those two relevant locations won't do, feel free to contact me for a location that does.