Following up, this has now been resolved in v1.1-30. Thanks to spartanchick316 for sending through some further information!
