Best way to debug a shiny app

[Anantadinath]

In my organization we are writing a bunch of print statements and view statement to see what's wrong with the code. Is there any better way to debug a shiny app. Any command or any package or anything would do.

I hate writing and removing those view and print statements.

[andresrcs]

Besides this simple but very effective guide

Shiny debugging and reprex guide

Shiny issues can be challenging to resolve relative to other problems with your code or statistical methods. Shiny apps are often large, complex projects with interacting files. When seeking help from others it is considered polite to: First, do your best to work through RStudio's debugging tools to diagnose your issue on your own. Often those shiny logs and tracebacks are useful to others trying to help out. Second, strive to minimize the effort required to replicate your issue. You can do this with a reproducible example ("reprex"). Shiny Debugging Errors in Shiny code can be difficult to track down. If you don't know where your problem is coming from, you can track it down with some o…

There is reactlog check out this video from rstudio::conf

Reactlog 2.0: Debugging the state of Shiny - Barret Schloerke

[Anantadinath]

thanks for replying on to the thread reading the document helped me a lot.

But reactlog quickly turns messy when you have more than 50 variables. We have stopped using it the moment we crossed 10 modules in our App.

But I think broswer() is the best solution so far. I will stick to it.

Thanks again for replying so quickly.

[system]

This topic was automatically closed 54 days after the last reply. New replies are no longer allowed.

If you have a query related to it or one of the replies, start a new topic and refer back with a link.