@bhr can you please share the exact error message? Your error message may be different as this was already fixed in 3.1.8.