You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The proxy caching system is only checking the if there is a cache for the Shopify store. This does not take into account other variables such as whether the access token has been changed. A great example is if the store removes your app access and decides to re-install the app at a later date. The access token would be different and therefore should also be checked during the getChachedAPI function.
I changed the function to also check to see if the cached access token is the same as the config access token.
if (!cached || Shopify._cachedAPIs[shop].access_token !== apiConfig.access_token) { cached = Shopify._cachedAPIs[shop] = new Shopify.API(apiConfig); }
This is an issue I have been dealing with for about a year and finally forked the package and found the fix.
Let me know if you need further explanation on why this should be implemented. Cheers
The text was updated successfully, but these errors were encountered:
The proxy caching system is only checking the if there is a cache for the Shopify store. This does not take into account other variables such as whether the access token has been changed. A great example is if the store removes your app access and decides to re-install the app at a later date. The access token would be different and therefore should also be checked during the getChachedAPI function.
I changed the function to also check to see if the cached access token is the same as the config access token.
if (!cached || Shopify._cachedAPIs[shop].access_token !== apiConfig.access_token) { cached = Shopify._cachedAPIs[shop] = new Shopify.API(apiConfig); }
This is an issue I have been dealing with for about a year and finally forked the package and found the fix.
Let me know if you need further explanation on why this should be implemented. Cheers
The text was updated successfully, but these errors were encountered: