Hi - we’re aware of this issue introduced in v1.2.5 for users with certain output paths. Look out for v1.2.6 later today with a fix.
Hi - we’re aware of this issue introduced in v1.2.5 for users with certain output paths. Look out for v1.2.6 later today with a fix.