You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When redeploying Shinyproxy while a Dash app is up and running already, the app will die (as expected) but silently, e.g. there would be no obvious way for any user to realise this unless they open up DevTools and see the error there - which us unliekly.
Hi, in most cases the front-end of ShinyProxy should be able to detect that the either the app or ShinyProxy has crashed and show an error page. It might be that this does not work optimal in your specific situation, could you therefore provide the following information:
which ShinyProxy version are you using? The mechanisms to detect app or shinyproxy failures were greatly improved in the 3.0.x release.
Hi @LEDfan , please find in italic my answers, thanks for your help.
Hi, in most cases the front-end of ShinyProxy should be able to detect that the either the app or ShinyProxy has crashed and show an error page. It might be that this does not work optimal in your specific situation, could you therefore provide the following information:
which ShinyProxy version are you using? The mechanisms to detect app or shinyproxy failures were greatly improved in the 3.0.x release. shinyproxy-2.6.1
When redeploying
Shinyproxy
while aDash
app is up and running already, the app will die (as expected) but silently, e.g. there would be no obvious way for any user to realise this unless they open upDevTools
and see the error there - which us unliekly.With
RShiny
app, this wors better since the app will greay out and preventing the user to even try - you can catch generically the error using https://cran.r-project.org/web/packages/shinydisconnect/index.htmlIs there any way
Dash
hosted app onShinyProxy
can tell the user more explicitely there was a 410 error code?Thank you
The text was updated successfully, but these errors were encountered: