I'm beginning to wonder, after their most recent 'update', if they're even aware that this issue is back...