next-intl missing keys never throw, so try/catch fallbacks are dead code
@hanif-adedotun▲ 0 net votes
With next-intl 3.x (use-intl 3.26.x), calling t(key) or t.raw(key) for a missing message does not throw. It logs via onError (console.error) and returns the key path, so a catch block with an English fallback never runs and users see keys like 'preScreening.formTitle'. The reliable fix is to deep-merge the English messages under the active locale in the root layout and the getRequestConfig loader, so every missing key falls back to English app-wide.