Please note that the only place where we still use Alert, imported from react-native, is in redux-setup.js. utils/alert.js uses the redux store to determine which theme to use. Attempting to use the alert wrapper prior to store initialization results in a You may not call store.getState() while the reducer is executing error. Although we could bypass this issue by using store.subscribe(variableUpdateCallback), the following reasons underscore why it's not an optimal approach:

1. The variable updates with every redux store update, potentially leading to performance issues.
2. We face a require cycle problem.

You can emulate second reason by changing import in redux-setup.js to our alert wrapper and replacing getCurrentTheme in utils/alert.js with something like this:

// ...
let currentTheme = defaultGlobalThemeInfo.activeTheme;
store.subscribe(() => {
  const nextTheme =
    store.getState().globalThemeInfo.activeTheme ||
    defaultGlobalThemeInfo.activeTheme;
  if (nextTheme !== currentTheme) {
    currentTheme = nextTheme;
  }
});
// Remember to swap all `getCurrentTheme()` occurrences to `currentTheme`
// ...

In D8648#255012, @patryk wrote:

Please note that the only place where we still use Alert, imported from react-native, is in redux-setup.js. utils/alert.js uses the redux store to determine which theme to use. Attempting to use the alert wrapper prior to store initialization results in a You may not call store.getState() while the reducer is executing error. Although we could bypass this issue by using store.subscribe(variableUpdateCallback), the following reasons underscore why it's not an optimal approach:

1. The variable updates with every redux store update, potentially leading to performance issues.
2. We face a require cycle problem.

You can emulate second reason by changing import in redux-setup.js to our alert wrapper and replacing getCurrentTheme in utils/alert.js with something like this:

// ...
let currentTheme = defaultGlobalThemeInfo.activeTheme;
store.subscribe(() => {
  const nextTheme =
    store.getState().globalThemeInfo.activeTheme ||
    defaultGlobalThemeInfo.activeTheme;
  if (nextTheme !== currentTheme) {
    currentTheme = nextTheme;
  }
});
// Remember to swap all `getCurrentTheme()` occurrences to `currentTheme`
// ...

Great explanation of your reasoning!!