Viewing 1 replies (of 1 total)
  • I’ve just released 1.2.0 which fixes this issue.
    This has been tested for both an upgrade path with the (now retracted) version 1.1 and a direct update from 1.0.1:

    • 1.0.1 -> 1.1 -> 1.2.0
    • 1.0.1 -> 1.2.0

    My sincere apologies to all who experienced this issue.

    Kind regards,
    Diana

Viewing 1 replies (of 1 total)
  • The topic ‘Version 1.1 retracted due to upgrade problem’ is closed to new replies.