Closed ellisp closed 9 years ago
I have no experience with shinyapps
. It seems like deployApp
runs the app from a server. I can imagine that this server uses the cran versions of the dependent packages. Maybe this causes consistency problems with the locally installed package versions.
Thanks. I'll follow up with the shinyapps google group; my understanding is that it should be robust to this situation, but the fact that it installs locally but not on the server suggests something's going wrong. Am I right in thinking that you can't upgrade the CRAN version until some of your dependencies are upgraded there?
All this highlights an interesting strategic risk of incompatible R package ecosystems. But in this case perhaps it is just a temporary glitch.
Not sure whether to report this here or for shinyapps but I think it's something about the {treemap} package that is problematic. To demonstrate the problem, I added the line
library(treemap)
and nothing else to one of the basic shiny examples. The code below shows that it deploys to shinyapps fine when I have the CRAN version of treemap on my system, but not when I have the GitHub version. shinyapps works by mimicking your local install on RStudio's shiny server, so this shows that the problem is that it can't build the GitHub version of {treemap} for some reason.This particularly causes the user problems just at the moment because the GitHub version of {treemap} is needed for {d3treeR} to work.
Which returns: