I am trying to deploy an app that has been deployed many times already and am reaching a very strange error about Ubuntu dependencies (I am running from mac, have restarted RStudio, and reinstalled rsconnect).
Here is the error:
> library(rsconnect)
> deployApp("loans_calc")
Preparing to deploy application...
Update application currently deployed at
https://jmaddalena.shinyapps.io/loans_calc/? [Y/n] Y
DONE
Uploading bundle for application: 389328...DONE
Deploying bundle: 2130042 for application: 389328 ...
Waiting for task: 619645026
building: Parsing manifest
building: Building image: 2245978
building: Installing system dependencies
################################ Begin Task Log ################################
[2019-06-04T17:41:34.180698062+0000] Execute script: packages/build/sys.sh
+ set -e
+ apt-get update -qq
E: The repository 'http://cran.rstudio.com/bin/linux/ubuntu xenial/ Release' is no longer signed.
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 619645027 failed: Error building image: Build exited with non-zero status: 100
Sorry you're running into a problem deploying a dashboard to shinyapps.io. We have identified the underlying cause of the issue and are actively working to resolve the problem.
Hi,
I'm experiencing exactly the same problem. Going crazy since early this morning trying to solve this without any luck. I really need to deploy my app asap!
Thanks
There is a hardware failure related to R ubuntu packages. From what we understand this should be fixed the next time CRAN syncs but that is largely outside of our control. This would affect any shiny applications which are dependent on system packages - but applications that are not dependent on system packages should still be building correctly.
We are presently review other options that would allow for a faster recovery.
I am encountering the same issue. I have tried deploying from a Windows OS however I get the same issue, it appears the Shiny app previously deployed retains the Ubuntu package build configuration? I saw on the status of the issue (link provided by @KHaley, thank you!) that this issue will not be resolved shortly -- could you advise on alternate plans for those of use working on deadlines? Would a total app rebuild be necessary? Thank you in advance for your help with this issue.