-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
shinyapps.io issues #29
Comments
Ricky, is that while running the app, or publishing on shinyapps.io? |
There is a discussion about the error message here: Did you install any packages from GitHub? If they are still in development phase that version will not yet be on CRAN. I suspect when you upload an app to shinyapp.io it will create a new server partition for you with R installed, then install all of the packages required for your app from the CRAN. If it can't find the package it will give this error. |
Hello all, I have tried many times to get my .rmd file uploaded to Shinyapp.io, but it simply won't upload. I was able to get a detailed output of what's wrong and it seems to be something with Knitr, but I have no idea what to do with that.... here is the output:
I have tried to type warnings() into my console, but it doesn't produce anything. |
It looks like you have a developer's version of knitr. Try installing the older version: require( devtools )
install_version( "knitr", version = "1.25", repos = "http://cran.us.r-project.org" ) |
That fixed it! However, I am now getting the same error as Ricky. Likely because my waffle package does come from github: https://github.com/hrbrmstr/waffle. Does that mean that there isn't a way for me to deploy my file? |
This R Studio discussion board says you should be able to:
How did you install your GitHub package? |
I removed the package and then re-installed using the devtools::install_github() option and it's now working! |
The only thing that may have been installed, was htmltools, but it kept prompting me to install, but would say it couldn't install. I restarted and the and it stopped promting to install. Not sure if it was installed afterall or not. The version I have is 0.4.0. |
FINALLY! Thanks @castower ! That helped! |
@RickyDuran glad that helped, it was such a frustrating error! To clarify all of my steps to solve my problem for anyone else that may read this: First, I uninstalled and reinstalled knitr using:
As a note, I did leave
in my file and it didn't cause any problems. Next, to stop the error message that was produced by my waffle package:
I also uninstalled and re-installed, but this time instead of using the first install option that was listed on the GitHub page:
I selected the devtools::install_github() option:
During the download from install_github() it indicated that it was importing the repos info. As noted in the linked R Studio Discussion Board, this is key so that shinyapps can find the necessary info. By default, it only searches CRAN and not GitHub. I found some helpful readings on this here: rstudio/rsconnect#88 and in section 2.4.0.1 here: https://docs.rstudio.com/shinyapps.io/getting-started.html#managing-r-versions |
Thank you both for sharing your steps! |
And just to note that Shiny Apps are fairly cutting edge. As I mentioned in the lecture notes, R has figured out a way to replace full-stack development of web apps, which requires six or seven different languages and a live server, with these translational shiny widgets and render functions, and integration to a server through shinyapps.io. You can see the progression to the frontiers and wilderness of open source development. Core R --> very stable and predictable Popular packages (dplyr) --> often easier to use and poweful, usually very stable and reliable but syntax is distinct from Core R Custom niche packages --> usually cool, but sometimes have issues with dependencies Fully customized platform development (shiny apps) --> usually some work making sure all of the part are playing nicely together |
I'm migrating the shinyapps.io issue to a new ticket.
Originally posted by @RickyDuran in #27 (comment)
The text was updated successfully, but these errors were encountered: