Duplicated issue check
iSpeakerReact version
v3.5.0
Description
Two i18n keys used by the sound practice components are missing from the locale files:
toast.playbackFailed
sound_page.loadError
When these error states occur, i18next displays the raw key instead of a human-readable translated message.
This results in users seeing messages such as toast.playbackFailed rather than a meaningful error message.
Expected behavior
The application should display a human-readable, localized error message when audio playback fails or when the sound menu cannot be loaded.
Reproduction steps
- Open iSpeakerReact and navigate to a sound practice page.
- Trigger an audio playback failure by making the requested audio unavailable.
- Observe the error notification.
- The notification displays the raw i18n key
toast.playbackFailed instead of a human-readable translated message.
A similar issue occurs with sound_page.loadError when sounds_menu.json cannot be loaded.
Does the app show the "App crashed" dialog?
Operating system
Windows
Browser
Chromium (Google Chrome, Microsoft Edge, Brave, Opera, etc.)
Additional info
The affected keys are referenced in the sound practice components but are not present in the locale files.
Relevant files include:
src/components/sound_page/SoundPracticeCard.jsx
src/components/sound_page/TongueTwister.jsx
src/components/sound_page/SoundList.jsx
There is an existing related key, toast.audioPlayFailed, used elsewhere in the application.
The project appears to manage translations through Weblate, so I would like to confirm whether these missing keys should be added directly to the locale files or handled through Weblate.
No files have been modified for this report.
Duplicated issue check
iSpeakerReact version
v3.5.0
Description
Two i18n keys used by the sound practice components are missing from the locale files:
toast.playbackFailedsound_page.loadErrorWhen these error states occur, i18next displays the raw key instead of a human-readable translated message.
This results in users seeing messages such as
toast.playbackFailedrather than a meaningful error message.Expected behavior
The application should display a human-readable, localized error message when audio playback fails or when the sound menu cannot be loaded.
Reproduction steps
toast.playbackFailedinstead of a human-readable translated message.A similar issue occurs with
sound_page.loadErrorwhensounds_menu.jsoncannot be loaded.Does the app show the "App crashed" dialog?
Operating system
Windows
Browser
Chromium (Google Chrome, Microsoft Edge, Brave, Opera, etc.)
Additional info
The affected keys are referenced in the sound practice components but are not present in the locale files.
Relevant files include:
src/components/sound_page/SoundPracticeCard.jsxsrc/components/sound_page/TongueTwister.jsxsrc/components/sound_page/SoundList.jsxThere is an existing related key,
toast.audioPlayFailed, used elsewhere in the application.The project appears to manage translations through Weblate, so I would like to confirm whether these missing keys should be added directly to the locale files or handled through Weblate.
No files have been modified for this report.