Closed mcm1957 closed 7 months ago
-- removed as irrelvant for problem --
(was a protectsion problem at windows)
@mcm1957 This is something else/different ...
see PR https://github.com/ioBroker/ioBroker.vis/pull/806 which seems to fix this issue.
fixed with 1.5.2 and later
Describe the bug
Installing vis 1.5.1 as UPDATE works as expected. INstalling vis 1.5.1 without a previous vis installation fails
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Direct installation of 1.5.1 should woirk
Screenshots & Logfiles
Failing installation of 1.5.1 at a system without vis reports:
Versions:
Problem is reproduceable