AOA (Angolan Kwanza) missing or broken in Admin Region/Currency configuration

What Medusa version and documentation are you using?

v2

Preliminary Checks

• This issue is not a duplicate. Before opening a new issue, please search existing issues: https://github.com/medusajs/medusa/issues

Issue Summary

Environment:

• Medusa v2 (latest create-medusa-app installation)
• Windows 11
• PostgreSQL 18
• Admin running on localhost:9000/app

Issue Description:

We are implementing an Angola-based commerce platform using Medusa and encountered problems related to the Angolan currency (AOA - Angolan Kwanza).

Observed behavior:

1. AOA does not appear properly in: Settings → Store → Supported currencies

2. When trying to create or edit a region, the Admin sometimes throws the following error:

TypeError: Cannot read properties of undefined (reading 'code')

The error appears inside the region editor when currencies/countries are loaded.

3. According to ISO 4217 and Medusa's Currency Module documentation, AOA should already be supported internally.

Expected behavior:

• AOA should appear normally in supported currencies.
• Angola (AO) region should be creatable without Admin crashes.
• Region editor should not fail when handling currencies/countries.
• Admin should properly support Angola/AOA configuration out of the box.

Additional Notes:

• Backend installation is clean and official using create-medusa-app.
• PostgreSQL connection and migrations completed successfully.
• Admin boots correctly.
• The issue seems related specifically to currency/region handling in the Admin UI.
• We were only able to proceed temporarily by using backend scripts/workarounds.

Potential impact: This affects commerce adoption in Angola and potentially other African regions/currencies that may not be properly surfaced in the Admin UI.

Would appreciate clarification on:

• whether this is a known Admin bug,
• incomplete currency support in the UI,
• or a regression related to regions/currencies.

Thank you.

How can this issue be resolved?

Possible Solution

We also attempted to resolve the issue through backend scripts and direct Store updates, but the behavior remained inconsistent and caused additional errors.

What we tried:

1. Adding AOA manually through backend scripts using the Store Module API.

Example approach:

• updating supported_currencies
• setting: { currency_code: "aoa", is_default: true }

2. Creating/editing Angola region through the Admin after injecting AOA.

3. Running clean installations of Medusa v2 with:

• fresh PostgreSQL databases
• fresh migrations
• no storefront
• no custom plugins
• no custom Admin modifications

Observed Problems:

A. Admin Region Editor Crash

When opening or editing regions, the Admin crashes with:

TypeError: Cannot read properties of undefined (reading 'code')

Stack trace points to: region-edit-*.js

The error appears during currency/country mapping inside the Admin UI.

B. Currency Visibility Problems

Even after manually adding AOA through scripts:

• AOA sometimes still does not appear correctly in: Settings → Store → Supported currencies
• or appears inconsistently inside region creation/editing.

C. Store Currency State Becomes Inconsistent

In some cases, after manually updating supported currencies through scripts:

• the Admin UI becomes unstable,
• region editing breaks,
• or currency selectors behave unexpectedly.

D. Fresh Installation Still Reproduces the Issue

We performed:

• completely clean PostgreSQL databases,
• fresh create-medusa-app installation,
• fresh migrations,
• official setup only,

and the issue still appears.

Conclusion

This seems to be an issue inside:

• the Admin currency/region UI,
• currency loading/mapping,
• or handling of undefined currency/country relations.

The problem does not appear to be caused by:

• custom plugins,
• custom storefronts,
• or unofficial modifications.

Expected Behavior:

• AOA should work out-of-the-box as a valid ISO 4217 currency.
• Region editing should not crash.
• No backend workarounds/scripts should be necessary.

Are you interested in working on this issue?

• I would like to fix this issue