Closed audricvigier closed 11 months ago
We have a fix for this in the dev version of renv, but unfortunately can't submit to CRAN because they are still on vacation.
Thanks, I can confirm the error is very informative in today's dev version (branch main commit 5fb52fe )
renv-1.0.1 has been released. Please open a new issue if you continue to have problems.
Hi,
I am developing Shiny apps using the
golem
package, and currently with R 4.2.3 . Before using that R version, I was working withrsconnect
0.16.0 to deploy, but now with 1.0.0 version, which caused the deploys to be impossible because it was using the packagerenv
. My MWE is the Shiny app that is generated upon creating a new golem project, and then executinggolem::add_rstudioconnect_file()
, and then hitting the blue button to deploy. The deploy worked with R 4.1.2 andrsconnect
0.16.0, but not with R 4.2.3rsconnect
1.0.0, I had the following error (I blanked out the server name):I just lost a full day to understand what was causing it, and it turns out it was
renv
, which was thinking wrongly the Shiny app I was trying to deploy (which is also a package as it is a golem, available locally only at this stage) was coming from CRAN. As suggested here , usingoptions(rsconnect.packrat = TRUE)
prior to deploying solved everything. Can you make the error informative to suggest the use ofpackrat
for people working withrsconnect
and/or local packages? Or usepackrat
as the default option, rather thanrenv
?