Hi,
I have developed an app which works on safari, loads in chrome and Firefox but the figures do not display. Can anyone help me.
thank in advance
Rims
Hi @Rims,
In my case (Issue with Firefox and Chrome for an app hosted on shinyapps.io), the issue appeared to be related to an error that was visible in the Javascript console (see the screenshots in the thread).
Can you check if you have Javascript errors in your own app please? If so, fixing those errors solve your situation like it did for mine.
Best,
Kevin
here is the link to the app can you please go through it, I have been working on it from last 2 days no success.
I have warnings.
Listening on [http://127.0.0.1:4315](http://127.0.0.1:4315/)
Warning in 1:dim(df1_2) : numerical expression has 2 elements: only the first used
Warning in 1:dim(df1_2) : numerical expression has 2 elements: only the first used
Warning: Error in UseMethod: no applicable method for 'plotly_build' applied to an object of class "character"
97: plotly_build
96: "plotly":::"prepareWidget"
95: func
82: origRenderFunc
81: output$T_stage
1: runApp
Warning: Error in UseMethod: no applicable method for 'plotly_build' applied to an object of class "character"
97: plotly_build
96: "plotly":::"prepareWidget"
95: func
82: origRenderFunc
81: output$M_stage
1: runApp
Warning: Error in UseMethod: no applicable method for 'plotly_build' applied to an object of class "character"
97: plotly_build
96: "plotly":::"prepareWidget"
95: func
82: origRenderFunc
81: output$N_stage
1: runApp
Warning in RColorBrewer::brewer.pal(N, "Set2") : minimal value for n is 3, returning requested palette with 3 different levels
Warning in RColorBrewer::brewer.pal(N, "Set2") : minimal value for n is 3, returning requested palette with 3 different levels
Warning in 1:dim(df1_2) : numerical expression has 2 elements: only the first used
Warning in 1:dim(df1_2) : numerical expression has 2 elements: only the first used
Regards
Rimpi
Hi @kevinrue,
Can you please go through the chrome and help me to solve the issue. I have been scratching my head from last few days, no success
Regards
Rimpi
I think you are starting to ask for too much here. It's fine to ask a few questions about an area that you are stuck on, but it feels like you are abusing Kevin's kindness here.
A good way to diagnose something like this is with a reproducible example. By simplifying your app to the point where you can share it and reproduce this error, you'll likely learn a lot about the specific components causing this issue.
Also, on chrome I am able to load images at https://rimsk.shinyapps.io/Appkin/. They do load rather slowly and return a "NULL" message though.
Dear @Rims
My apologies for ceasing to reply. Unfortunately, I got very busy before the holidays and ended up forgetting about it completely after I came back to work.
Curtis made a good point about minimal reproducible examples (i.e., making the smallest app you can, that raises the same issue) as the best tools to diagnose issues, but also to help others help you.
In particular, you gave a link to you app without giving a link to your source code, which is in itself is already a major barrier for people who would like to help you. Many errors cannot be guessed only from the error message without having access to the underlying code.
That said, even better than sharing the whole code of a specific application (which would require the person to get familiar with a lot of domain-specific code irrelevant to the issue), minimal reproducible examples provide only the source code of the problem (usually with some accompanying code to generate dummy data with having to download anything) which helps the person rapidly focus on the source of your problem.
It might sound like more work, but I can guarantee that it gets you more and quicker replies. See https://stackoverflow.com/questions/5963269/how-to-make-a-great-r-reproducible-example for more information.
Furthermore, more often than not, writing that minimal example is all that's needed to identify the problem yourself, which is an even more satisfying feeling.
With all that said, I've just had a look at the app in Chrome and it seems to work fine now. So either you fixed it, or there were independent updates in R packages or Chrome that solved it.
Best wishes
Kevin