Hi all,
My app works perfectly fine locally and I can't figure out why it won't work when deployed. My data is very small (~200 rows, 5 columns) and shouldn't be a size issue. Here are my logs - the error has persisted for a few days now. Any help would be greatly appreciated!
If you go into your shinyapps.io control panel, does it show the app as having a running instance? If so, try killing that instance and then redeploying.
Getting closer I think! I had a running instance, stopped it to set the application status as "sleeping" and re-deployed. Also, changed the startup timeout to 300 seconds. This time, it started loading and I got to a screen that said "Please wait" with a moving bar until finally getting and error message 1.
The logs look identical to those originally posted.
You could try fully deleting the version currently installed and then reinstalling, but that's a long-shot. There may be something funky specific to your code causing this. Does your application load files from a remote server, scrape data from a web site or something else requiring external access during startup?
The problem with deleting and reinstalling is that I'm pretty sure I need the startup timeout to be higher than 60 seconds, and I can only figure out how to change that setting from the dashboard once the app is already deployed.
I'm not sure there's anything in my code causing this, the application is pretty basic in that it reads in a dataset of latitudes and longitudes and plots them on a leaflet map.
I'm also receiving an error in my R console when deploying which is separate from what the logs show
Error in func(fname, ...) : app.R did not return a shiny.appobj object.
I've never seen this myself, but apparently there are at least a couple of ways other people have encountered it. One is using a single file (rather than separate UI and server files) and omitting the line shinyApp(ui = ui, server = server) from the bottom of the file. I doubt that's the issue since it runs for you locally, but maybe? Another user eliminated the error message by setting their working directory to the directory containing the app before deploying it.
