pickerInput doesn't work with shiny v1.11.0

[IvanM26]

pickerInput() is not working with {shiny} v1.11.0.

reprex

I have created a simple app to use as a reprex to showcase the problem. The code can be found in shinyWidgets.inputBinding.error repo. You just need to install the latest versions of {shiny} and {shinyWidgets} packages.

The app has two inputs (one defined with shinyWidgets::pickerInput() and the other with shiny::selectInput()).

On initialization, outputs render accordingly:

The problem happens when pickerInput() selection is updated. The following screenshot shows that the output is not updated:

The following error can be seen in the Console:

reprex Session Info:

Additional Comment

I wasn't able to reproduce the original error in my reprex:

This error led to think that there could be problems with the inputBinding.

Nevertheless, I think the reprex showcases the problem described in the issue.

[ifellows]

Just ran into this, which broke my app. Thank you for posting the issue.

[asbatestw]

I get the same message with virtualSelectInput. Below is a screenshot from the reprex just replacing the pickerInput with virtualSelectInput.

And I do get the original error message.

[TylerPollard410]

I had the same issue with virtualSelectInput after updating to shiny 1.11.0 (Nothing in my app code changed). I also have radioGroupButtons that are no longer reactive as well. Both inputs initialize with correct values but the dependent output no longer updates when toggling the shinyWidgets. I simply changed virtualSelectInput to selectInput and radioGroupButtons to radioButtons and the app is again functioning correctly, but with less appealing widgets.

[Impeergator]

I ran into the same issue with all kinds of inputs of this package.

[jonthegeek]

rstudio/shiny#4243 should fix this. What would it take to get some tests in place to catch this in the future? It depends on the shiny JS, so you'd want to use shinytest2.

[pvictor]

I don't see what kind of tests could have avoided this problem, it's always been complicated to test the JavaScript part of these widgets. If solutions exist, I'll try to find the time to improve this. Glad the shiny team is so responsive.

[jonthegeek]

@pvictor I'll try to put together a PR to show an example (specifically for virtualSelectInput() because that's the one I use and can justify working on at work). I assume it'll be ok to add shinytest2 to Suggests, right?

[pvictor]

Sure it's ok if it can prevent issues like this

[dmacguigan]

Same issue for me here, broke my R package. Thanks @IvanM26 for brining this up.

[jonthegeek]

@pvictor #742 tests virtualSelectInput() enough to avoid issues like this in the future. I did that one in particular because that's the input that broke for me, but the same process should work for most other inputs.