I was advised this was a known problem being worked on and would be resolved in the next version of the app (which seems to be the case). Now running 24.3.1
↧
I was advised this was a known problem being worked on and would be resolved in the next version of the app (which seems to be the case). Now running 24.3.1