Troubleshooting logs and manifest.json

[AmeliaMN]

I'm trying to port a Shiny app I had on shinyapps.io over to Posit Connect. I downloaded the whole package from shinyapps.io, including a manifest.json. I made that into a GitHub repo and connected it through Posit Connect. But, the app is failing to deploy. Are there any pointers for troubleshooting using the log and manifest.json? Here's the portion of the log I think is relevant:

2025-01-30T14:51:28-06:00 ERROR: compilation failed for package ‘testthat’
2025-01-30T14:51:28-06:00 * removing ‘/cloud/lib/x86_64-pc-linux-gnu-library/4.0/testthat’
2025-01-30T14:51:28-06:00 A common cause of packages failing to build from source is insufficient memory.
2025-01-30T14:51:28-06:00 Failed to install R packages.
2025-01-30T14:51:29-06:00 Failed to publish content: Stopping because installation of testthat failed. Check your manifest.json. error_id=7b7e2b9e-f3da-460d-9399-6264ed38cc60

[alex_chisholm]

Hello, thanks for trying out Connect Cloud.

I think one reason the deployment failed is because of the old version of R requested through the manifest.json file (4.0.2) and dependency conflicts. Was this an old deployment to shinyapps.io?

Using your repo, I recreated the app locally, created a new manifest.json file with rsconnect::writeManifest() and was able to get a successful deploy.

Could you give this approach a try and see if you still hit issues? Thanks!

Alex

[AmeliaMN]

Thanks, yes this worked! Although I think the function is writeManifest(), no?

[alex_chisholm]

Correct! Good catch.

For others, here is a guide for dependency management with R deployments on Connect Cloud: Create a manifest.json file for Connect Cloud – Posit Connect Cloud Documentation