Closed nick-youngblut closed 1 year ago
I had to re-deploy the app via the publish button in Workbench. This created http://10.22.20.45/__api__/applications/12
. I then tried using rsconnect::deployApp()
to update the app, but the function created a new version of the app: http://10.22.20.45/__api__/applications/13
. Subsequent runs of rsconnect::deployApp()
successfully update the 13
deployment.
Could you try rsconnect::deployments
to enumerate the known deployments and then rsconnect::forgetDeployment
to remove specific records?
rsconnect::forgetDeployment(appPath = ".", account = "USERNAME", server = "SERVER", name = "DEPLOYNAME")
One note: If attempting to remove records for a document rather than a Shiny application (e.g. index.Rmd
, you'll need to use the filename as the appPath
argument.
rsconnect::forgetDeployment(appPath = "./index.Rmd", ...)
rsconnect::forgetDeployment
deployment fixed the issue. Maybe it would be helpful to provide that hint in the error:
Error: HTTP 404
GET ${URL}/__api__/applications/${ID}
The requested object does not exist.
rsconnect::deployApp()
to initially deploy a Shiny app to a Connect instance hosted on a local server.rsconnect::deployApp()
worked successfully.rsconnect::deployApp()
, I received the following error:rsconnect::application()
shows thathttp://10.22.20.45/__api__/applications/9
no longer exists on that server, butrsconnect::deployApp()
keeps trying to use that API url instead of "realizing" that the app no longer exists and thus instead creating a new deployment.I can't figure out a way to "force" re-create the app on Connect via
rsconnect::deployApp
. The rsconnect::deployApp docs don't seem to describe a way of re-deploying an app after it is deleted in Connect.sessionInfo