Issues when migrating Shiny apps from shinyapps.io to connect.posit.cloud

Hello! I'm a long-time Posit user. In fact, I was instrumental in getting and maintaining a Posit contract at my 10k+ person company and driving company-wide adoption.

I am also a Basic tier posit cloud customer. I am having trouble migrating some fairly simple apps from shinyapps.io to connect.posit.cloud.

For three out of four of them, I got errors very similar to this one.

2026-10-13T07:53:51-05:00 * DONE (stringi) 2026-10-13T07:53:51-05:00 A common cause of packages failing to build from source is insufficient memory. 2026-10-13T07:53:51-05:00 Failed to install R packages. 2026-10-13T07:53:52-05:00 Failed to publish content: Stopping because installation of Rcpp failed. Check your manifest.json. error_id=e35cb2da-c539-46c7-bfcb-1799e38f8d6d

They function properly on shinyapps.io and there was no issue deploying them there originally. Any ideas here? Example app in case it's helpful: Car Crashes in Allegheny County (2004-2016)

Looks like this application was deployed to shinyapps.io quite a long time ago and is running on R version 3.4.3. Posit Connect Cloud doesn't support that version of R, so during migration we attempt to use 4.0.5 (the oldest supported R version). Unfortunately, most R packages that run on R 3.4 will not install correctly on R 4.0.

This application will need to be updated to run on a modern version of R. If you still have your original RStudio IDE setup used to install to shinyapps.io, that can be updated to point at Connect Cloud following these steps:

Then you could iterate on the content in Connect Cloud without impacting the application in shinyapps.io. Once it is working, then you could finalize the migration in the UI.

Hope that helps!

thanks
Sam

Ah OK, I thought it might be something like that, but the insufficient memory note in the output had me worried was it was actually some kind of resource thing. Will modernize and redeploy. Thanks for the help and the speedy reply!

I imagine this will cause a lot of forced attrition during the auto-migration next year, but maybe that's part of the plan (to drop old inactive content and force some updates)?

Thanks again.