PixelRayn
- PixelRayn
- JIRAUSER740132
- Europe/Stockholm
- Yes
- No
Deleted Comment:
thank you. was not aware of this
Deleted Comment:
According to the original issue this has not yet been resolved.
Could you please describe the exact steps to recreate the bug/s?
According to the original issue this had been resolved at 26/Jan/17, before the 1.19.2 update was released, therefore this has to be a separate issue.
The other possibility is, that the original issue has not been resolved and is incorrectly tagged as resolved, so which snapshot was this fixed in?