Hey folks - quick update here. I’ve added the newer address-prefill examples from this thread to the internal issue we’re tracking. This still appears to be actively under investigation, but I don’t have an ETA to share yet.
One thing I’m trying to separate is the exact URL path involved. The documented cart permalink format is /cart/{variant_id}:{quantity}?checkout[...], while the examples here are existing-cart/cart-form or direct checkout paths. If anyone can reproduce this with a dummy documented cart permalink as well, that would be super helpdul narrow down whether we’re looking at one issue or a related path-specific issue.
For Plus merchants, checkout extensibility may be a workable temporary option for shipping address prefill in some builds, but it won’t be a full replacement for every email/phone/address URL-prefill flow.
I’ll keep this thread updated as soon as I have a more concrete answer on our end.
Hey @Akos_Paska - quick update here. We’ve pushed a fix that should resolve the prefill issue.
The shipping-address behaviour in your example may be a separate path-specific issue though, since we haven’t been able to reproduce address parameters failing through /cart/checkout, while your app appears to submit through /cart?....
Could you retest now and, if it’s still failing, share a fresh redacted example showing the exact form action/method and whether the same address works with a documented /cart/{variant_id}:1?checkout[...] permalink? That’ll help me get the remaining case tracked correctly.
