Browser Extensions Become Unresponsive After Returning from Background

fish

Open the browser and make sure the extensions are working properly. Then put Orion in the background without closing it. After leaving it in the background for a while, reopen it and you will find that all extensions have stopped working. The length of time in the background is not consistent — usually when switching back, the page refreshes automatically and the extensions stop working. Occasionally, the page does not refresh, and in those cases the extensions usually continue to work normally.

This issue shouldn’t happen as extensions should remain functional even when the browser is in the background. Switching between background and foreground should not disrupt the extension’s behavior.

TF 1.3.29 (3)

AnnaCludiaSpeckdeSouza

fish

To add the log when this error occurs, this is the complete log when returning to orion from the background

orion-log.txt

45kB

fish

I think the crux of the problem is this:
[2025-10-03 11:23:07] SceneDelegate: sceneWillEnterForeground [2025-10-03 11:23:07] NewTabViewController ID 24: reloadWebView [2025-10-03 11:23:07] JSAPI: Error: Attempting to use runtime from web extension background context. [2025-10-03 11:23:07] JSAPI: Error: Error executing javascript (executeScript).
If Orion returns from the background and iOS system recycles memory, causing a page reload, the WebView is refreshed. However, the WebExtension context (runtime and content scripts) is not properly re-initialized, leading to failures when attempting to execute JavaScript or communicate via the extension’s runtime.