Hey @v.rehbinder, this is actually known and reported bug.
It was mentioned in the Known Issues for 1.0.1.