Update: still the same issues. I looked at their system status for past incidents and it looks like they logged this as a known issue back on December 16th but it also is marked as “resolved” now, which based on all our replies here, is certainly not the case. I’ve attached the screenshot In addition to keeping this thread alive, I think we should all be contacting support directly (through their chat, calling etc) and hopefully they will update this glaring defect in the software/app.
