I have a simple shiny app that is doing some data manipulation for some people who have no experience using R. Since this app isn't going to be used by a large amount of people and has some sensitive company data being manipulated by it, I was thinking that storing it locally would be a great option.
I began to do some research and stumbled upon photon. With that being said, I followed the steps found on their github(in their presentation found at this link: https://www.user2019.fr/static/pres/lt257916.pdf).
When attempting to create the app, I am hit with the following warning message:
Warning in normalizePath(path.expand(path), winslash, mustWork) :
path[1]="C:\Users\tylerfrields-re\Desktop\Savings_Allocation_Shiny/electron-quick-start": The system cannot find the file specified
After recieving this message, the commands continue to run all the way to the point of packaging the app, but the app doesn't seem to package. I have all the dependencies installed, so was wondering if anyone could help me resolve the issue. Any help is greatly appreciated!
Quick update: There is now an app there, but the issue is that the app contains nothing. It will run, but it is just a blank white screen. I'm unsure why this is occuring.
Related
I have been trying to deploy my shiny app to shinyapps.io but I just can't seem to figure it out. Everything works fine locally but not when I try to deploy. I keep getting the following error: The application failed to start (exited with code 137). I checked my logs and it says that I am out of memory.
See below:
All my packages get loaded and then once it comes to my data it stops and says that.. When I look at the metrics and go to the memory usage section it says I'm using less then 25 MB. My instance size is set to large (1GB). I don't understand why it's saying I'm running out of memory. I would appreciate if anybody can give me guidance or tell me something that I may be missing.
Shiny application needs resident memory. I guess because of connecting cloud service. I can't tell you one thing, but there are some things that are typically consume. R interpreter can feel heavy and Shiny throws in another 10 MB just loading the library. I think it's helpful to you. shiny homepage about performance
In my Shiny App, I have a Data.table implemented through the package data.table.
My Shiny app working absolutely fine on the local Server, however when I deployed it to Digital-ocean, I frequently get error as below :
DataTables warning: table id=DataTables_Table_1 - Ajax error. For more information about this error, please see http://datatables.net/tn/7
It is not that, I get this error every time, however quite frequently, and failed to repeat my experiment to regenerate that error. Appear like, this error comes up randomly?
I searched over the Internet, however, failed to get any concrete suggestion how to circumvent this problem arising on the Shiny application.
Any help will be highly appreciated.
Thanks,
Since you claim you deploy the shiny app on DigitalOcean and the app works well locally, I suspect the DT version on your server is not the latest.
You can check the version of DT by adding something like outputText("dt_version") to ui.R and output$dt_version <- renderText(packageVersion("DT")) to server.R.
If not, please install the developing version of DT via devtools::install_github('rstudio/DT') and try again (I bet you are using shiny-server, please remember to restart the server to ensure the newly installed package being loaded).
while publishing app on web getting error called: check your log or contact the app auther.please find above image links
ERROR: An error has occurred. Check your logs or contact the app author for clarification.
if anyone can help me to resolve this error I'd be grateful.
There are multiple reasons for this error. Rstudio has provided multiple reasons (link below) but most common are:
Environment variables not the same in shiny web vs. local (make sure working directory is set to ~/, start a new rsession and run only the ui.R, server.R or app.R and see if you can preview in local before publishing.)
Update libraries to latest versions and hopefully you are not using the libraries that are not yet available in CRAN.
https://support.rstudio.com/hc/en-us/articles/229848967-Why-does-my-app-work-locally-but-not-on-shinyapps-io-
I'm in a difficult situation to figure out how to publish shiny app online.
Can't find any solution in the older questions.
The app works locally perfect but its impossible to put it online.
when I run the log, show just this:
Error in serverInfo(server) : server named 'rpubs.com' does not exist
on the part
"Markers": Line 14 - Paths should be to files within the project
directory. Error in sheets_fun(path) : Evaluation error:
path[1]="database.xls".
The file *.xlsx is already in the same folder of the *rmd.
Could any one help me I have no idea how to solve this issue. I'm now in two weeks trying to solve this.
that is to grab a job, and I will appreciate a lot if anyone tell me how to make it works
The shinyapp I built earlier was running fine in my old laptop. Recently I got a new laptop with Windows10. After setting up everything, I tried to run the app but it the browser opens and closes immediately with the error :
Listening on http://127.0.0.1:5004
ERROR: [on_request_read] connection reset by peer
I have also set chrome as default browser....
I deployed this app in shinyapps.io it is working fine there.
I tried few more simple apps in Rstudio but the same issue coming. Looks like the issue is more related to some setting in Windows10. Can someone help me please.
Thanks in Advance.....
Without details on the specific code, I'd share my personal experience with the same error for your reference. In my case, I used RStudio to create a shiny app that save data to a local directory on my computer, while I told R to output files to directory "response", I hadn't created such directory under the working directory so came the error. Simply creating the sub directory named "response" solve this right away. Or for moving your project files to different places in the future, you can just check whether the folder exists, if not, create one shall save you a lot of time.