I'm having trouble on my dev environment after Shopify API Upgrade
I am having some strange issues on my
dom-dev environment on Lantern after updating our Shopify plugin API version.
It was working fine yesterday and after deploying this to production, my dev environment now seems stuck in a bad state where it keeps losing the API upgrade. It also keep removing my shopifyCustomer model and seems to be missing all the date now. It seems to work fine in the other dev envs we have though. Not sure what I can do to fix it and any help would be appreciated.19 Replies
Hi Dom,
Looking into this now
Great, thanks!
Were you able to figure anything out for it? I still can't get my customer model to work correctly.
Hi Dom,
We are still looking into it.
k, thanks
When you lose the API upgrade which version are you seeing it revert from?
2025-04
We went from 2024-10 to 2025-04
When I checked just now, it seemed like it stayed in 2025-04 but my shopifyCusomter model is still messed up, saying it doesn't exist in the gadget generated api, and has no data in the table.
It looks like there is an issue with the storage key for that model.
Is there anything in the git diff from the last deployment regarding the storage key for shopify customer?
ah interesting, ok. It doesn't look like it should have changed from the git diff. It was
storageKey:
"ModelField-Oc2PlCyU-03m::FieldStorageEpoch-ediv14y4dzUr" before and after
Is it possible to rollback the env to an earlier state? Do you have backups of dev envs?
I would obviously prefer not to lose the test data there, but really just need to get it working again however we can. It looks like it being broken is also breaking our lantern client npm package build (since it does all envs)I can do that, how many days back?
If we could go back to yesterday morning, I think that would do it.
I can do 5pm on the 9th or 10th
5PM on the 9th would be great
for just
dom-devYes, just a moment
Looks like its working
shopifyCustomer is accessible
Yessss!
Thanks so much
Working great now
Happy to hear!
If it's ok with you I'm going to go ahead and mark this thread as resolved
yep, sounds good
But feel free to re-open with another message
appreciate it
Do you like this answer?