Joe Cheng

When it does happen, hitting Reload a second or third time doesn't fix it? We only saw it happen once or maybe twice at a time.

OK, great. We suspect the browser is caching. Can you try: 1. Holding down Shift while reloading 2. Using the Firefox developer tools to see what response is coming back...

On the server, `reactive()` is not the correct function here, rather you want `observe()`. I think you'll find these videos helpful: https://www.rstudio.com/resources/shiny-dev-con/reactivity-pt-1-joe-cheng/ https://www.rstudio.com/resources/shiny-dev-con/reactivity-pt-2/

OK, I looked a little more closely. First off, in your UI, you should not have two outputs with the same ID (`NS(session_id, "msg")`). Second, rather than two different tabs...

I still stand by my solution over your approach, but what you're describing sounds like a JavaScript error is being thrown? Do you see an error in the browser's JavaScript...

@wch Is this something we need for v1.2? (i.e. in the next week)

Tricky issue! `ignoreInit` is meant to ignore the initial call of the observer itself, not of the UI it’s referring to. But it is unintuitive indeed that it would work...

I wouldn’t use the real ID to make those input IDs unique, I’d make them unique using a random value that has no relation to anything. Back to the larger...

You can add `freezeReactiveValue` to your `renderUI`: ```r output$ui_out

Oh, I understand what you're doing now. OK, that's a good question. This is the first thing that came to mind, it's not easy but it does work--as long as...