[justasking7000]

I'm sorry that just isnt enough. I'm talking about critical payments stuff within the app.

You're telling me this was the best route for 10k+ apps that are dependent on this for processing payments.

Literally zero warning.

[rstupek]

You are assuming the installs number correlates with actual users which it likely doesn't. As several people have pointed out this isn't a google maintained extension. If something is this critical to your business it's on you to make sure it works for you.

[justasking7000]

It was already working. The extension had been functioning for months already.

My entire point is that if you're a huge organisation like google. And if you offer a critical feature that users then integrate deeply into their product.

This least you could do with your enormous wealth is send a note out giving a heads up about this damaging change.

What's so hard to understand here?

[rstupek]

You're misrepresenting that it's google's feature which you were using when it clearly states its from Stripe.

[imanrahmati]

(Firebaser here) What damaging change?

- You can continue to use the old extension (you won't get updates by Stripe nor Invertase and in the future Stripe may introduce breaking changes)

- You can clone the open source repo and maintain it yourself

- Or you can install the Invertase extension with the same exact config and you'll continue to have maintenance and upgrades.

We expect in a 3rd party platform these things happen (out of our control) so we've prepared multiple routes for you.