Whilst the dashboard was running as a PWApp in Android, I updated a third party UI node in the server, restarted node-red and updated some flows.
At the time of the update the app was showing a page that did not contain the ui node, but such a page showing it had been previously opened, so the node would already have been loaded.
I could see from the ui that the modified flows had been picked up automatically, without my intervention, but when I went to a page containing the third party node I could see that it had not picked up the updated code. Pulling down to refresh did cause a refresh but still the modified node was not picked up.
In #937 @cstns suggested that it may be a PWA caching issue.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Dashboard version: 1.11.1
Node-RED version: 4.0.0-Beta.4
Node.js version: 20.11.0
npm version:
Platform/OS: Android
Browser: Chrome
Have you provided an initial effort estimate for this issue?
Current Behavior
Whilst the dashboard was running as a PWApp in Android, I updated a third party UI node in the server, restarted node-red and updated some flows. At the time of the update the app was showing a page that did not contain the ui node, but such a page showing it had been previously opened, so the node would already have been loaded. I could see from the ui that the modified flows had been picked up automatically, without my intervention, but when I went to a page containing the third party node I could see that it had not picked up the updated code. Pulling down to refresh did cause a refresh but still the modified node was not picked up. In #937 @cstns suggested that it may be a PWA caching issue.
Expected Behavior
No response
Steps To Reproduce
No response
Environment
Have you provided an initial effort estimate for this issue?
I am not a FlowFuse team member