This was fixed in yesterdays update 1.4.0 (135) or do you still have this issue?

Reply to this note

Please Login to reply.

Discussion

Not sure. It was from a note from a couple days ago. Will try again