Issue with timestamp on x axis -- ggplot/plotly

[suveer.daswani]

Hello, I am writing a simple ggplot and geom_bar command insider a renderPlotly function in my shiny app. The x variable is a timestamp, which in my data is stored as chr "2020-03-10 15:13:22". When I plot this, the x axis labels now read as "50", "100"...this is weird and I have tried multiple ways to overcome this but nothing seems to work. I am basically not being able to see the timestamp label on x axis for each bar. I would appreciate your help.

[dromano]

I haven't used shiny, but am wondering whether changing the data type of your timestamp to datetime might help. You could load the lubridate package and then use as_datetime() to convert the column from character to datetime. Does that help?

[suveer.daswani]

Thank you for your response @dromano. I tried that and it changes the type of the timestamp to POSIXct, format: "2020-03-10 15:13:22". Then when I plot through plotly and ggplot it once again unfortunately reformats the timestamp to "1.5456B" for example and in fact doesn't show the bar. @andresrcs do you have any idea? I hope you don't mind me reaching out. I know you've been super helpful with shiny before
Thank you again @dromano

[andresrcs]

Can you provide a reproducible example (reprex) illustrating your issue? Please have a look at this guide, to see how to create one for a shiny app

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…