Unable to deploy : error in force(code)

Posit Professional & Hosted Products shinyapps.io
1

Hi,

I'm unable to deploy since friday 17/11/2023.

Is anyone facing the same issue ? I tried to deploy an older version of my app, it failed too

I've deployed this app several times before, and it works fine localy

----- Deployment error -----
Erreur dans force(code) : Could not upload file.
Appels : <Anonymous> -> withStatus -> force
 
----- Error stack trace -----
5: rsconnect::deployApp(appDir = "C:/Users/james/Desktop/V1_version de publication", 
       appFileManifest = "C:/Users/james/AppData/Local/Temp/5ba9-5454-720f-e6ea", 
       account = "xxx", server = "shinyapps.io", appName = "xxx", 
    ...
4: withStatus(paste0("Uploading bundle for ", assetTypeName, ": ", 
       application$id), {
       python <- getPythonForTarget(python, accountDetails)
    ...
3: force(code)
2: stop("Could not upload file.")
1: (function (e) 
   {
       cat("----- Deployment error -----\n")
    ...
Erreur dans force(code) : Could not upload file.
Appels : <Anonymous> -> withStatus -> force
Exécution arrêtée
2

I tried today, with same result but with a different error message :

----- Deployment error -----
Error in uploadCloudBundle(client, application$application_id, bundlePath) : 
  Could not upload file.
Calls : <Anonymous> -> uploadCloudBundle
 
----- Error stack trace -----
4: rsconnect::deployApp(appDir = "C:/Users/james/Desktop/V1_version de publication", 
       appFileManifest = "C:/Users/james/AppData/Local/Temp/5cb8-f4a5-b397-b490", 
       account = "xxx", server = "shinyapps.io", appName = "xxx", 
    ...
3: uploadCloudBundle(client, application$application_id, bundlePath)
2: stop("Could not upload file.")
1: (function (e) 
   {
       cat("----- Deployment error -----\n")
    ...
Error in uploadCloudBundle(client, application$application_id, bundlePath) : 
  Could not upload file.
Calls : <Anonymous> -> uploadCloudBundle
Execution halted
3

I've encountered the same issue. Did you ever find a solution, James?

4

It seems the issue was related to my network connection, which was unstable or not strong enough. The message disappeared as soon as I chose another network. I hope this helps, even though it may sound like a very simple solution