{"section":"known-issues","requestedLocale":"en","requestedSlug":"checkout-shipping-step-does-not-advance-to-payments-step-in-argentina","locale":"en","slug":"checkout-shipping-step-does-not-advance-to-payments-step-in-argentina","path":"docs/en/known-issues/Checkout/checkout-shipping-step-does-not-advance-to-payments-step-in-argentina.md","branch":"main","content":"## Summary\n\nIn Argentine stores, some postal codes leave the shopper stuck on the shipping step: the address is auto-completed from the postal code, but the resolved `city` is not an accepted value in the `vtex.address-form` ARG country rules, so the address never validates. Because the `city` field is auto-completed, it is not rendered in the form; the shopper has no invalid field to correct, and no error message is shown.\nThe address is therefore never persisted and the step silently refuses to advance. Only postal codes whose city resolves to a single value are affected — codes that resolve to multiple cities render a `Ciudad` select and work normally.\n\n## Simulation\n\n- In an ARG store, add any available SKU to the cart and complete the profile step.\n- On the shipping step, enter an affected postal code (e.g. `1687`).\n- Fill street and number. No city field is rendered.\n- Click \"Go to payment\" — nothing happens; no error is shown.\n- Control: repeat with an unaffected postal code (e.g. `1688`) — the step advances normally.\n- To confirm a reported case: check that `shippingData.address.street` is still `null` in the orderForm after the shopper filled the form.\n\n## Workaround\n\nThere is no workaround available."}