Woocommerce-admin: i18n locale information is not correctly set after Setup Wizard

[masteradhoc]

Prerequisites (mark completed items with an [x]):

• [x] I have have carried out troubleshooting steps and I believe I have found a bug.
• [x] I have searched for similar bugs in both open and closed issues and cannot find a duplicate.

Describe the bug
I installed woocommerce on a fresh wordpress installation.
I did the setup over the new wizard and choose country liechtenstein and also on a separate installation with country switzerland.

My old PR where i submitted the correct i18n informations: https://github.com/woocommerce/woocommerce/pull/27193

Expected behavior
Currency, position of currency, ... should be set based on the i18n predefined setup file.

Actual behavior
Basic US informations get set.

Steps to reproduce the bug (We need to be able to reproduce the bug in order to fix it.)
Steps to reproduce the bug:

1. Install woocommerce on a fresh wordpress site
2. work with the setup wizard and choose country liechtenstein
3. finish the wizard and change to settings
4. check if the currency is $ (then it doesnt work) or CHF (then it would work)

Thanks
Brian

Isolating the problem (mark completed items with an [x]):

• [x] I have deactivated other plugins and confirmed this bug occurs when only WooCommerce plugin is active.
• [x] This bug happens with a default WordPress theme active, or Storefront.
• [x] I can reproduce this bug consistently using the steps above.

[masteradhoc]

@juliaamosova could you also doublecheck this? Thx

[masteradhoc]

@rrennick may you can check and confirm this?

[rrennick]

Hi @masteradhoc,

Thank you for reporting the issue. The new onboarding is being developed in another repository: https://github.com/woocommerce/woocommerce-admin

I am going to move your bug report there so that the right team could take a look further.

[masteradhoc]

Hey @pmcpinto
could you check and confirm this please?

Thanks
Brian

[pmcpinto]

@masteradhoc thanks for opening the issue and creating the PR. We're going to try to take care of this as soon as possible, in order to include it in one of the upcoming releases.