Unable to proceed with purchasing a Shipping Label due to the inability to select a Shipping Carrier and Rates

[pmusolino]

Describe the bug
If I try to create a Shipping Label with the current flow in production (using the Release build configuration), I'm unable to purchase Shipping Labels because I can't open the "Shipping Carrier and Rates" view. The "Continue" button doesn't work.
If for some reason the button is not tappable (wrong Shipping Label config?) I expect to see at least an error.

Screenshots

Setup

• Xcode 16.2.0
• Simulator: iPhone 16 Pro, iOS 18.0

[dangermattic]

Thanks for reporting! 👍

[pmusolino]

CUW: peaMlT-18c

[pmusolino]

Follow-up on this: I discovered that this might be more of a UI/UX problem. In the package details step, it’s mandatory to select a package under the “Package Selected” cell. However, unlike all other fields, this one doesn’t generate an error if it’s not filled in, and pressing “Shipping Carrier and Rates” doesn’t notify you that something is missing. So it seems like something isn’t working, but it’s actually because the selected parcel is missing, and the user isn’t informed about it.

[rachelmcr]

I confirmed that I didn't run into this error on a test store with previous shipping label purchases; my last selected package is pre-filled/pre-selected:

On a brand new store, the package selection screen did generate an error and didn't allow me to proceed until a package was selected:

I'll test again with the store from the original report and see what's happening in that case, but as least from the initial investigation it looks like this isn't a universal or fundamental problem with the legacy experience. It's possibly something specific to this store's configuration (which still means it could be affecting other merchants/stores, but not everyone).

[rachelmcr]

@pmusolino Could you share a screen recording or details steps about how to got past the package selection screen? I tested on the same test store you used, and I still can't proceed past Package Details without choosing a package:

I'm not sure how to reproduce the buggy behavior you're seeing.