Accepted application charges will now be automatically transitioned into an active state

Retired Boards Appdev Partners Discussion
1

I don’t understand how the activate endpoint is still getting called. I’ve updated my code to remove the call to activate billing, yet the API health dashboard is still showing calls to activate.

Screen Shot 2021-09-15 at 9.14.57 AM.png
Screen Shot 2021-09-15 at 9.14.57 AM.png1886×442 42.3 KB

Here is my return_url php file with the accept_billing call commented out.

Screen Shot 2021-09-15 at 9.12.44 AM.png
Screen Shot 2021-09-15 at 9.12.44 AM.png1448×780 71.9 KB

And here is the old accept_billing function we no longer call that would call activate.json and trigger the health check.

Screen Shot 2021-09-15 at 9.13.03 AM.png
Screen Shot 2021-09-15 at 9.13.03 AM.png1820×356 36.7 KB

The set_user_paid function only updates the database.

Screen Shot 2021-09-15 at 9.53.57 AM.png
Screen Shot 2021-09-15 at 9.53.57 AM.png1704×554 63.2 KB

I am sure that this code is removed. How is it still getting triggered?

On top of that, how can this be a breaking change? We are simply calling an endpoint that is no longer used or necessary. What is the issue and adverse effect? Couldn’t it be ignored?

2

Hi @baberuth22

If you’re still seeing this warning, could you please fill out the API support form under partner support in the [Beta] Report an issue section? We’ll need some additional info such as app name and ID. Thanks!

3

We have also removed all calls to the activate.json endpoint and still see the warning on our dashboard.

4

I talked with another app developer who has the same problem as us. He removed all code calling the old activate endpoint as well.

Worst part is they deactivated my app yesterday because of this. Shopify developer support is the worst.

This is supposed to be our support channel. FML

5

I had this recently. It depends on your setup but in essence, removing the call to activate it without an API version defined will leave these specific charges in no mans land.

So if you have been doing the flow where charge is created, accepted by merchant, then you activate without any API version applied, it will still need activating.

To resolve the deprecation error, the charge needs to be created with a versioned API after the deprecated version. Then when ever a merchant accepts the charge, it’s automatically transitioned.

e.g /admin/api/2021-07/recurring_application_charges.json