Thank you! I don't have a device that can recreate this error but I will be looking into this for v0.6!
