Expiring offline token requirement causing issues with dev apps running locally

Hi there,

I would like to share an issue we are facing with the newly added requirements for Expiring offline tokens.

Background context

We have a few apps that existed before the change that don’t use expiring offline tokens. When running the apps locally, we create a new app on our partner portal so that devs can run the app before pushing changes to staging and production. Additionally, we have a service that manages API calls to the Billing API between the apps. Due to the need of testing billing, we have to select public distribution for the developer apps since it causes API errors when calling the Billing API when public distribution is not selected.

The issue we are facing

For newly created apps in the dev dashboard that are running our existing apps locally (which don’t have expiring offline token logic implemented) the API keeps returning the following:

[API] Non-expiring access tokens are no longer accepted for the Admin API. Start using expiring offline tokens: https://shopify.dev/changelog/expiring-offline-access-tokens-required-for-public-apps-april-1-2026

Is it possible to move this gate to the app submission step rather than blocking it in the API? We have no intention of submitting our dev apps at any point and this is causing us major issues in our app development process whenever we have a need to create new apps on the partner portal for development purposes.

I appreciate that this is creating some issues for your dev process. The enforcement of expiring tokens happens when requests are made to the Admin API. It’s not a one-time check during the app store review process. By enforcing during API requests it allows us to ensure that apps are meeting the requirements even after they’ve made it through app Store review.

Are you using a Shopify app template for your apps? All of our app templates and libraries use expiring tokens by default and have for several months.