Hello, @Agah_Balaban , I have this problem, this is very annoying.
Do you think this going to be fixed somehow in soon?
I sent another message about this issue. Is this not just a tech-problem? This is coming from Netflix or Google have any intention? …
I would appreciate it if you could let me know if there is a possibility that this issue will be resolved. Thank you.
1 Like
Hi. I am experiencing the same problem of “Loading…” as described by others above. I have followed the advised steps of:
- clearing the cache
- deleting and reinstalling the app
- switching off the Netflix “test participation”
- switching on and switching off VPN…
And nothing has worked to change my situation.
I am only using LR for Netflix (learning Spanish, so wanting dual subtitles in Spanish and English), and I have just paid for a new membership today (having unsubscribed a few weeks ago because of the same “loading” issue).
If the bug can’t be fixed, could I please be refunded? Thank you
2 Likes
I messed a bit with Codex(AI) on the Chrome extension and managed to get it working;
I Made a temporary Extension if you want to try it and it worked for me (at your own risk)
I did’nt add any dangerous stuff, but I’m not a coder.
You have to load it “unpacked” in the extension page and tick the “Developper mode”
I could not mod the original extension directly because Chrome detect it as unofficial changes.
Let me know if it works, I just hope they can do a real fix soon. 
What Actually Fixed Subtitles
It’s really netflix who changed the engine a bit…
The real subtitle fix is in pageScript_lln.min.js.
Language Reactor expected Netflix manifest data shaped like:
{
movieId,
timedtexttracks,
audio_tracks,
video_tracks
}
Netflix’s newer Cadmium player now exposes/transforms it more like:
{
viewableId,
textTracks,
audioTracks,
videoTracks
}
So LR was stuck at NO_MANIFEST: it could see the active Netflix player and track IDs, but it could not find the subtitle manifest it needed.
The critical patch added a manifest catcher that does this:
find object with textTracks/timedtexttracks and audioTracks/audio_tracks
textTracks -> timedtexttracks
audioTracks -> audio_tracks
videoTracks -> video_tracks
viewableId/U/J -> movieId
then call LR's original manifest cache function ft(e)
That is why subtitles came back.
Files Changed
Only 4 live files changed:
manifest.json -899 bytes
content_netflix.js -197 bytes
background.min.js +77 bytes
pageScript_lln.min.js +31996 bytes
Everything else is copied unchanged, except backup files I created while testing. Chrome does not load those backup files.
manifest.json
Changed the extension from the signed Web Store extension into a safe unpacked clone:
name: Language Reactor -> Language Reactor Netflix Fix Fresh
short_name: Lang Reactor -> LR NF Fix
version: 5.1.7 -> 5.1.7.2
update_url: removed
key: changed, giving the unpacked clone a stable extension ID
Also narrowed the clone to Netflix only:
kept: content_netflix.js
removed: YouTube, Amazon, LanguageReactor site content scripts
And narrowed web-accessible scripts:
kept: pageScript_lln.min.js
removed: pageScript_lly/pageScript_lla/pageScript_dioco exposure
content_netflix.js
Removed the nonce gate that was blocking page-to-extension messages.
Original logic:
if (!(location.hostname.endsWith(“languagereactor (.) com”) || “localhost” === location.hostname) && t.nonce !== r)
return console.warn(“[LR] Invalid RPC nonce - request blocked (possible security issue)”);
Fixed logic:
const { nonce:e, ...n } = t;
o(n);
Effect: LR’s injected Netflix page script can talk to the extension background again. This fixed the [LR] Invalid RPC nonce blocker, but for a public fixer I’d make this narrower/cleaner because it weakens that guard.
background.min.js
Two tiny changes only silence broken-message errors.
Original:
chrome.tabs.sendMessage(e,t)
Fixed:
try {
chrome.tabs.sendMessage(e,t,()=>{chrome.runtime.lastError})
} catch(e) {}
Original:
chrome.runtime.sendMessage({target:"side_panel"})
Fixed:
chrome.runtime.sendMessage({target:"side_panel"},()=>{chrome.runtime.lastError})
Effect: removes Could not establish connection. Receiving end does not exist. noise. This did not fix subtitles.
pageScript_lln.min.js
Main changes:
10 occurrences:
hoombieeljmmljlkjmnheibnpciblicm
->
dihfaahcppfmheldalbanenkpcdhjbcj
That makes the injected page script point at the unpacked clone ID.
Changed defaults:
userLanguage:!1 -> userLanguage:"en"
lexaDictActive:!0 -> lexaDictActive:!1
Disabled the crashing Lexa prompt loader:
async loadDefaultLexaPrompts_translated(e){ ...network/default prompt logic... }
became:
async loadDefaultLexaPrompts_translated(e){return}
Wrapped redrawUI() in try/catch sections so one broken UI panel does not kill the whole Netflix integration. This is what stopped errors like:
Cannot read properties of undefined
redrawFullDict
activeModal
Netflix player session fallback changed from:
let u = l.filter(e => e.startsWith("watch"));
ve = u[0] && s.getVideoPlayerBySessionId ? s.getVideoPlayerBySessionId(u[0]) : null;
to:
let u = l.filter(e => e.startsWith("watch")), d = u[0] || l[0];
ve = d && s.getVideoPlayerBySessionId ? s.getVideoPlayerBySessionId(d) : null;
So if Netflix no longer names the session watch..., LR still grabs the first player session.
Track matching got fallback logic. Before, LR only matched by exact Netflix track ID:
e.new_track_id === activeTrackId
Now it also falls back to language/type fields:
language === activeTrack.bcp47
rawTrackType === activeTrack.rawTrackType
isNoneTrack === activeTrack.isNoneTrack
isForcedNarrative === activeTrack.isForcedNarrative
Audio got the same style fallback:
langCode_N === activeAudio.bcp47
type === activeAudio.rawTrackType
Added diagnostics:
LRDIAG(...)
localStorage.__LR_NF_DIAG
localStorage.__LR_NF_FETCH_CAPTURE
Those are why we could see NO_MANIFEST, the Netflix URL, active audio ID, and active subtitle ID. Useful for debugging, not needed for a clean public fixer.
Bottom Line
The subtitle fix was not Chrome settings, not Netflix subtitles, and not the background error. It was this: Language Reactor 5.1.7 was looking for Netflix’s old manifest shape, while Netflix Cadmium now hands around a newer textTracks/audioTracks shape. We patched LR to recognize and normalize that newer shape.
2 Likes
I’m also having the same problem and it looks like i’m not the only one who is experiencing the issue. can you please fix this? i have been learning English through your app and now it is not working at all
1 Like
same here only netfix lr is not working…
ㅠㅠ나만 이런게 아니구나…아 랭귀리저러너로 영어공부하는데 이렇게 막히면 안되는데…ㅜㅜ
Hi. I am experiencing the same problem with Netflix only. I have cleared the cache, deleted and reinstalled the app, switched off the Netflix “test participation”, switched on and off the VPN and nothing has worked so far.
1 Like
Hi, @Ada, I am really tired…disabling the “Participate in testing” , this hadn’t change anything.
All contents in Netflix is just “Loading subtitles… please wait”.
I created new account for LR, but the result is same.
Chrome AI says the problem would be fixed within several days because Netflix seems to have made some update or there’s some kind of server-down problem.
I am not tech-person. So I have no way other than just wait and see.
Hope this should be fixed. sigh… (_;
2 Likes
please do something LANGUAGE REACTOR MANAGER
I’m facing the same issue,
I was about to buy the Language Reactor Premium but now i’m facing this issue.
Please fix this issue ASAP,
Language reactor has become unusable on Netflix.
1 Like
Same issue from Italy on Netflix (target language: Japanese). Disabling the “Participate in testing” feature in my settings, as suggested by others on this thread, did not work, unfortunately. Tried uninstalling and reinstalling LR, clearing the cache, changing browser, watching Netflix on an incognito tab, and so forth. Nothing… it’s been like this for a few days now. LR seems to be working just fine on YouTube, though.
1 Like
A few days ago, the trick involving the “Test participation” option on Netflix worked for me. Yesterday, the same problem recurred, and disabling that option no longer fixes it.
The Language Reactor panel gets permanently stuck on the message “Loading subtitles, please wait…”, and other functions of the extension also seem to be experiencing issues.
Developers, we need help!!
1 Like
both LR and appforlearning are not working with Netflix at the moment. the disable testing feature worked for a short period a few days ago but since has stopped working. I imagine this is an issue on the netflix end and hopefully the developers for both companies are sorting through this issue.
1 Like
I am having the same problem. I used Language Reactor yesterday for the first time and wanted to use it today again. But it keeps giving the message “subtitles are being loaded, please wait” (but then in Dutch).
I have restarted the laptop, restarted the browser (Chrome) and cleared the cache, to no avail.
1 Like
Fix it ASAP
developer！
2 Likes
Still not working for me either
same problem here. no subs.
We can’t log in our own account with this version, I sent mail the the devs but I have no answer for now, but it still prove it’s fixable.
Note: the problem seems to be specific for Netflix. I have tried a Youtube video and there the subs work. I don’t know if it works for all Youtube videos of course.
Hello everyone! Thank you for reporting this issue! At this time, the issue is not related to the “Test participation” option. It is related to a change in the manifest format. The team is aware of this issue, and we already have a solution. This issue will be resolved shortly! We’ll keep you updated. Thank you for your understanding! 
12 Likes