Child Task failed: Error parsing manifest

586 views
Skip to first unread message

Jane Yang

unread,
Feb 3, 2015, 2:21:06 AM2/3/15
to shinyap...@googlegroups.com
Hello,

I am trying to deploy a Shiny app but am running into a few errors. The first is that I get a warning about an absolute path in my file:
>> Question 1: do I need to use the ~ notation in the directories in order for the app to deploy properly on the server? I am loading in an .Rdata file from the data folder within the project directory, which is why I define a working directory.

The second issue is a parsing manifest error. Originally, I had a number of other project-related (but not Shiny-related) files in the folder, but realized it was causing the app deployment to load unnecessary documents. I therefore moved all non-Shiny files out of the project directory, including ke_profile.xlsx. However, this file is being referenced in the error message below with "checksum mismatch."
>> Question 2: why is the Shiny app deployment referencing documents outside of the project directory?

Thank you in advance for your help!
Jane

> shinyapps::deployApp('/VOLUMES/AUSTEN/OAF/KE-expansion')
The following potential problems were identified in the project files:

--------
server.r
--------
The following lines contain absolute paths:
14: wd <- "/VOLUMES/AUSTEN/OAF/KE-expansion"

Paths should be to files within the project directory.
Do you want to proceed with deployment? [Y/n]: Y
Preparing to deploy application...DONE
Uploading application bundle...DONE
Deploying application: 30814...
Waiting for task: 4777268
  building: Parsing manifest
################################## Begin Log ################################## 
################################### End Log ################################### 
Error: Unhandled Exception: Child Task 4777269 failed: Error parsing manifest: Manifest file data/~$ke_profile.xlsx checksum mismatch
> 

Jane Yang

unread,
Feb 3, 2015, 2:46:34 AM2/3/15
to shinyap...@googlegroups.com
Hi all,

Sorry, I just figured out the answer to Question 1 so please ignore that. If anyone has any ideas about resolving Question 2, however, I am all ears.

Thank you!
Jane

--
You received this message because you are subscribed to a topic in the Google Groups "ShinyApps Users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/shinyapps-users/lqdH0PTZalU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to shinyapps-use...@googlegroups.com.
To post to this group, send email to shinyap...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/shinyapps-users/809bafdb-ee60-47be-917c-e2681b7ccf32%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Jane Yang

unread,
Feb 3, 2015, 3:56:29 AM2/3/15
to shinyapps-users
Hi everyone,

Please disregard. For anyone who might run into a similar issue, the answer was that there was a hidden file in the data directory that had ~$ in the filename, thereby causing an error. By deleting that file, I was able to get the deployment to continue. Now running into Error: Unhandled Exception: HTTP 502: Bad Gateway, but imagine that has to do with the server rather than the server.r script.

Thanks,
Jane

Chad Barraford

unread,
Feb 3, 2015, 10:37:00 AM2/3/15
to Jane Yang, shinyapps-users
Hi Jane,
If you retry to deploy your application, it should work. You might have deployed while we were doing a code deploy on our side. Sorry for the inconvenience.

You received this message because you are subscribed to the Google Groups "ShinyApps Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to shinyapps-use...@googlegroups.com.

To post to this group, send email to shinyap...@googlegroups.com.

Nicki Anselmo

unread,
Nov 30, 2015, 3:00:19 PM11/30/15
to ShinyApps Users, jane.ju...@gmail.com
I had a similar parsing manifest error message because the referenced excel file was still open in excel. Once I closed the file in excel, I was able to deploy my app. Thanks Jane for leading me to my resolve this error. 
Reply all
Reply to author
Forward
0 new messages