I think today's version fixed that issue. Let me know if it still happens after you update to 1.05

Reply to this note

Please Login to reply.

Discussion

Will do. Updated through Zapstore.