-
Notifications
You must be signed in to change notification settings - Fork 133
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error in value[[3L]](cond) when deploying to RStudio Connect #998
Comments
Hey, The disable autoload warning is a known bug of shiny : rstudio/shiny#3355 For the other one, this try catch error usually means that Connect can't launch your application. Can you provide more logs ? |
Hi Colin, Thanks, will ignore that warning then. I've attached the application logs and the connect server logs from the latest time I deployed. Is there any other logs I could provide? Thanks |
Thanks a lot. Unfortunately the logs aren't helpful here :/ I've sent a lot of golem apps on Connect, so I don't think it is linked to golem but to your Connect instance. Are you able to send the default shiny app (old geyser data) on Connect? Also, can you share a zip of |
Hi Colin, sorry for the delay. We have a few apps deployed including some of the jump start examples. But I tried deploying the old geyser data and got this error:
Maybe there's something missing from our Connect server. Wonder if it's because we're using the Amazon Linux 2 OS. I've attached the zip of |
Describe the bug
When deploying to RStudio connect the following error appears despite working locally. This has been reproduced on a blank project:
There is also the following warnings above this error:
This warning is shown despite the presence of the
R/_disable_autoload.R
file and the addition ofoptions(shiny.autoload.r = FALSE)
to the app.R file.To Reproduce
Steps to reproduce the behavior:
01_start.R
02_dev.R
golem::add_rstudioconnect_file()
rsconnect::deployApp()
session info
Additional context
Connect server info:
The text was updated successfully, but these errors were encountered: