dash-bootstrap-components: 0.8.2 Nav appears to break url pathname callbacks

Hi @tcbegley,

thanks for your quick response. After sleeping a night over the issue I think I found the root cause and it is not connected to the navbar itself directly.

I have 2 callbacks that are triggered by an URL change:

1. The callback responsible for updating the navbar
2. The callback responsible for updating a graph on the “home” page

Essentially what happens is callback 2 tries to update the graph in the “home” page and in parallel callback 1 is triggered and overwrites the “home” page while the graph is still being updated. Result is that it looks like callback 2 is broken when callback 1 is also active.

Well that is really odd - I made a copy of the folder, rebuilt the Virtual Environment with 0.12.2 (using the environment.yml file from the old environment with just that change from 12.0 to 12.2 in) and it now works with your script and mine - I guess that rebuilding the environment sorted out some dependencies that had maybe got messed about. Anyway, it works 😃

Thanks for all the reports. The fix is now part of the latest stable release 0.8.3 (on PyPI, conda to follow soon).

You should now be able to fix with

pip install -U dash-bootstrap-components

You can check which version you have installed with

python -c "from dash_bootstrap_components import __version__; print(__version__)"

I’m going to close this now, but if anyone has further problems feel free to reopen or open a new issue.

confirm as well - I also had the same issue with latest public release, now it’s fixed for me.

dash-bootstrap-components==0.8.3rc1 dash==1.9.0 python==3.8.0

Thanks!

I also had the same issue with latest public release, now it’s fixed for me.

dash-bootstrap-components==0.8.3rc1 dash==1.9.0 python==3.8.0

I just downgraded to the Dash version 1.8 that solved my problem. Maybe it has something todo with plotly/dash-core-components#743

Thanks @matthijsramlab, it does indeed appear this was the problem. I tested against Dash 1.8.0 since that’s what the original post found the issue with, but with Dash 1.9.0 I can now reproduce the problem. Will see what’s necessary to fix.