Everything works great use it to monitor my works messages and check every 5 minutes however it’ll randomly stop till I bring up the browser on my phone.
Is this a phone issue? I have the browser set to unlimited battery/background use and it’ll run just fine in background for roughly 40 minutes then just stop or even just skip a good 20-40 mins check once or twice then skip another 20-40 minutes.
@elii the screenshot appears to be from chrome’s extension’s console. from what i know, mainstream chromium based browsers do not support running extensions on the phone. it is possible that there are limitations with the browser you using. what browser is this?
the best option for local monitoring is to use the browser extension for pc or the desktop app.
the problem could most likely be because of how kiwi browser works but can’t confirm. do you keep the browser and app open and unlocked for the whole duration?
Unfortunately the way my works web page works is I can only be logged in on one device at a time and it’s a pain to swap from PC to phone.
The phone browser is constantly left open but often gets pushed to the background/unfocused app and told to have unlimited background resources. Phone does lock but from what I understand with the unlimited background resources the browser should be continuously running.
Still need to try a different phone browser to see if it fixes the issue but found a little more error log.
Uncaught (in promise) Error: Only a single offscreen document may be created.
Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
Refused to run the JavaScript URL because it violates the following Content Security Policy directive: "script-src 'self' 'wasm-unsafe-eval' 'inline-speculation-rules'". Either the 'unsafe-inline' keyword, a hash ('sha256-...'), or a nonce ('nonce-...') is required to enable inline execution. Note that hashes do not apply to event handlers, style attributes and javascript: navigations unless the 'unsafe-hashes' keyword is present.
i am not sure about this. is there a way to verify this?
these are logged when pages are being checked for changes. unsafe scripts in the pages are blocked. this doesn’t show any problem with the extension itself.
