I have a shiny app that depends on a GitHub package. I recently updated the GitHub package, so I want to republish the shiny app as well. I have made no changes to the shiny app code at all, and it runs without error in RStudio. But, when I go to republish it, I get these messages in the Deploy tab of RStudio.
Preparing to deploy document...DONE
Uploading bundle for document: 96244...DONE
Deploying bundle: 426681 for document: 96244 ...
Waiting for task: 180459152
building: Parsing manifest
building: Building image: 419646
building: Building package: xtable
################################ Begin Task Log ################################
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 180459153 error: Unhandled Exception: HTTP 599: Connection closed
Execution halted
I am running the latest versions of R (3.2.5) and RStudio (0.99.893) on Windows 7, and I made sure all the packages have been updated.
I searched around for folks reporting similar errors (and solutions) and found didn't find anything helpful.
I'd appreciate any tips.
Links:
Shiny app - if it says "Last modified: 7 January 2016", it's still the old version that I'm trying to replace.
Code for shiny app
GitHub package
Did you update to R 3.2.5? It seems shinyapps.io is not ready for this.
I had these errors yesterday. Roll back to 3.2.4 and it will work.
Note this is confirmed in shinyapps forum:
"Is it at all possible that you are running with R version 3.2.5? If
so, downgrading to 3.2.4 should fix this issue. The error message
should be saying something like: shinyapps.io doesn't support this
version of R yet."
Related
Since yesterday evening I could easily deploy and update my shiny application on shinyapps.io. Today I made few changes, tried to deploy again, and I am getting the following error which I don't know what it refers to:
Preparing to deploy application...DONE
Uploading bundle for application: 1099846...DONE
Deploying bundle: 6170071 for application: 1099846 ...
Waiting for task: 1198780170
error: Processing bundle: 6170071
################################ Begin Task Log ################################
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 1198780173 error: Unhandled Exception: An error occurred (ExpiredTokenException) when calling the AssumeRoleWithWebIdentity operation: Token expired: current date/time 1659692079 must be before the expiration date/time16596
Execution halted
I tried to create a new token on shinyapps.io for the rsconnect package, but it doesn't work. Do you know how to solve this problem? Thanks
UPDATE: I tried to re-deploy it one time and it worked, then I tried again and it's not working again.
I also went on the shinyapps.io website, and tried to delete an old application, and I got the same error. Does it means they're having problems on their side?
Just had the same issue. I went on to my Shinyapps dashboard and re-copied across the token and secret from there to our GitHub repo settings. Re-deployed and all went well.
I've recently been developing an app, and noticed a few days ago I updated R to 4.1.2. After making some changes to the app, I used the Publish button to deploy to shinyapps.io. The deployment console threw the following error and failed:
Error: Unhandled Exception: Child Task 1045191965 failed: Error building image: R version 4.1.2 currently unavailable
Execution halted
Now, I've deployed many times previously, and this was the first deployment since the update to R. I haven't included any code because my app.R is over 1500 lines and it really didn't seem to be related to any of thee changes I made. I was wondering if anyone could help me figure out whether this error is referring to my system or the server I am deploying to. I expect I may have to roll back to the pre-update snapshot and try again, but I'd like to avoid doing that if the problem lies somewhere else.
Rstudio is Version 1.4.1103
Operating system:
Distributor ID: Ubuntu
Description: Ubuntu 20.04.3 LTS
Release: 20.04
Codename: focal
Thanks in advance!
After checking with shinapps.io support, they informed me their server has not been updated to 4.1.2 and to downgrade until they are able to make the upgrade. They were not able to provide an ETA on that. Thanks to the support staff there!
everyone!
I am having problems deploying my Shiny App. When deploying the app, I get the following console output:
Preparing to deploy application...DONE
Uploading bundle for application: 177552...DONE
Deploying bundle: 813581 for application: 177552 ...
Waiting for task: 383835116
building: Parsing manifest
################################ Begin Task Log ################################
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 383835121 failed: Error parsing manifest: Manifest file manifest.json checksum mismatch
Execution halted
Please take into account the following facts:
I've already checked this solution, and it didn't work:
Deploy R app in shinyapps.io- Error:parsing manifest [SOLVED]
Also, I've had saved a previous working version of the app, downloaded it back via the "download bundle" option of ShainyApps, and I get the same message.
What can I do in order to solve this? Thanks a lot! Don't hesitate to ask me for further details if necessary.
Adding to Elias's answer. When you download a Shiny bundle, there is a file included called "manifest.json". Checksum error here.
Delete "manifest.json" and deploy app again.
Maybe it's not a solution, but it's a way of preventing the error. The "trigger" of the error is the fact that I was working on the Shiny bundle obtained using "download bundle" option of ShinyApps. It's possible it has to do with the encoding or the MD5 checksum, but NEVER work on files from the bundle. I can state the aforementioned as I had a copy on GitHub, cloned it, worked on it, deployed the new version, and it worked! Thanks!
I have a shiny app that includes a helper.R file and a data.txt file. It seemingly runs fine locally, but when I go to deploy it on shinyapps.io, I get:
Preparing to deploy application...DONE
Uploading bundle for application: 57723...DONE
Deploying bundle: 250119 for application: 57723 ...
Waiting for task: 71388412
################################ Begin Task Log ################################
################################# End Task Log #################################
Error: Unhandled Exception: Child Task 71388413 error: Unhandled Exception:
Each time the task number changes (I've also had 71387628, 71387509, 71386087, 71375249, 713*****). I'm running r version 3.2.1 (World-Famous-Astronaut) on Platform: x86_64-apple-darwin13.4.0 (64-bit). The data file is 1.1MB, so the file size should not be the issue. The only library I'm using is data.table which is from CRAN.
What might be the issue?
It's just that the upload server that got trashed. The Coursera Data Science Capstone was due to day right around that time, so a thousand or so people all flooded it at once, and it went down. No idea when it'll be back up though.
I am loading one of the example apps from Shiny R into ShiniApps.io`
library(shinyapps)
shinyapps::setAccountInfo(name='xxx', token='xxx', secret='xxx')
deployApp("01_hello")
and then I get this error:
Error: Unhandled Exception: 'NoneType' object has no attribute 'getitem'
The app appeared in the web-page of Shinyapps.io as "undeployed".
Any clue what may be causing this error? the error is the same whether I run R 64 or 32 bit.
I had the same problem today. I wasn't able to successfully deploy a new app (getting the same error), but I was able to redeploy a previous app.
I have tried removing all packages and code from my new app (left only empty shinyServer and shinyUI functions uncommented) and still couldn't deploy.
Restarted R several times. Updated all packages. Nothing helped.
A few hours later I tried to deploy again and it passed without errors.
I know this is not exactly an answer but I suspect it was a server-side error because it failed during the "Starting instances" step of deployment.
So try to deploy it again, hope it works this time.