Perhaps others can confirm everything I’m sharing below because I’ve only run into this for the first time today with a client’s app. It looks like if you’re generating a new API key to use for location related products (Maps, Routes, Places), Google is requiring your project to be linked to a billing account.
See pricing change info here: https://developers.google.com/maps/billing/understanding-cost-of-use
See new pricing table here: https://cloud.google.com/maps-platform/pricing/sheet/
Apparently you get $200 of recurring monthly credit to offset your costs, but overall it’s a pay-as-you-go system.
I’ve been using keys I generated well before this change, so I hadn’t noticed any interruptions in my test apps, however, I noticed today that it now renders with a “For development use only” watermark. According to this recent thread, the lack of a linked billing account would be the cause.
I wonder if anyone is able to display maps with a newer API key generated in the console (https://console.developers.google.com) that is not linked to a billing account? I just want to make sure I understand this new policy. I’ve been seeing Bubblers experience issues with map display and address search - this might be part of it?