@danilvoe did you try making the change to index.js that was suggested in the ticket that you linked? It may be a workaround worth pursuing until our developers get a change to fix the issue properly.
@danilvoe did you try making the change to index.js that was suggested in the ticket that you linked? It may be a workaround worth pursuing until our developers get a change to fix the issue properly.