Publishing from MacOS arm64 to shinyapps.io fails with error:
Error: Unhandled Exception: child_task=1679460939 child_task_status=failed: Error building image: Error fetching Rcpp (1.1.1-1) source. unable to satisfy package: Rcpp (1.1.1-1)
1 Like
Verified same error publishing from Windows 11 x64
The error seems related to renv upgrade from 1.1.5 to 1.2.1
Downgrading back to 1.1.5 fixes on Windows but not Mac
1 Like
I am experiencing the same issue with the option
options(rsconnect.packrat = TRUE)
from rsconnect in Ubuntu 24.04.4 LTS.
1 Like
I just bumped into this (using RStudio on Linux Mint), and I use neither renv nor packrat. Will shinyapps.io catch up to the latest Rcpp soon?
1 Like
Hi all,
We're aware of this issue and will have a fix soon. In the meantime, a workaround is to install the prior version of Rcpp locally so that the troublesome version 1.1.1-1 is not sent to shinyapps.io.
Thanks for your patience.
1 Like
We have deployed a change that should correct this. If you continue to experience Rcpp errors of this type please let us know here! Thanks.
2 Likes
In my attempt to publish (see App error -after publishing), I had noticed the issue with Rcpp. There appears to be a discrepancy between how soon packages appear in Rstudio's CRAN and when they are available on Connect Cloud.
My upload attempt made it a little further. Apparently shinyapps does not yet support pak (0.9.3-1).
1 Like
Hi everyone,
I recently encountered the same issue while deploying from Ubuntu 24.04.4 LTS using options(rsconnect.packrat = TRUE). The deployment failed because the environment could not satisfy the dependency for Rcpp (1.1.1-1).
Although Posit mentioned a fix has been deployed, some users might still face discrepancies between local CRAN versions and what is available on Connect Cloud/shinyapps.io.
If you are still stuck, I successfully resolved this by downgrading both Rcpp and fs to their previous stable versions before deploying. You can use the following commands:
# Downgrade packages to satisfy shinyapps.io dependencies
devtools::install_version("Rcpp", version = "1.1.0")
devtools::install_version("fs", version = "2.0.0")
Blink and it changes: pak is now at 0.9.4.
Thanks! This fixes my original issue -- I can deploy across platforms as needed with Rcpp (1.1.1-1) in the manifest. It seems others may have related issues deserving of their own tickets -- good luck! See note from @michal-kinel
In general, packages are available instantaneously or nearly instantaneously (edit: on shinyapps.io it may be up to 60 minutes) after CRAN publication. What happened here is that there are a handful of packages CRAN has published at a differently formatted URL from where they typically can be found. Connect Cloud, shinyapps.io, and at least one other Posit product was not expecting this change on CRAN's side and was failing to find these newest versions of these packages. Unfortunately the foundational Rcpp was one of the packages affected, so it was high impact.
Were you able to publish then @prubin ?
No, the lag in updating pak is blocking me ... and, for all I know, if I make it past pak there will be another package awaiting update. Full disclosure: I did not write the app. I fixed a couple of bugs for someone and am trying to test it on my personal account before handing it back to them. So I don't have a handle on all the dependencies.
pak 0.9.4 is being published on CRAN conventionally in the same way/place they've published packages forever, so issues with it are probably not of the same genre as was faced with Rcpp. If you have error messages and/or a manifest.json you can share, I can investigate further to confirm though.
Thanks! I just published it successfully in my account, so apparently the pak issue is resolved (as is the Rcpp issue).