Customer account extensions do not render locales when the language is not in its market. So, we might be in the spanish market, which does not have the french language included, in the french language, and I am getting these errors:
The error is consistent, since it does not only affect the extensions developed in-house, but also any third-party extension, as in the InPost extension depicted in the image.
If we add all languages to the market it works again, but this is going against the merchant’s business model.
There is an ongoing issue with previews and the cli on development environment for the customer accounts. Is it related?
In our case, we encountered i18n issues within both the customer account and the checkout pages. Upon investigating our theme, we discovered that interactions with the Cart Ajax API had been implemented without locale-aware URLs.
Resolving this seems to have fixed the incorrect market/language attribution. This makes sense for the checkout—if the cart contains conflicting signals regarding a product’s origin or the customer journey, the system defaults. However, it remains a bit less clear why this specific fix also resolved the issues within the customer accounts.
