The current status of this issue is astonishing, and I am very frustrated with AW developers (not support). After the absence of the promised bug fix in 5.2 I was again in contact with support. The dev team basically dropped the ball – they had misunderstood the original problem and started from scratch again. I worked with support to provide further test info to feedback to dev.
As of yesterday, we are now expected to accept that this is not an AW bug after all, but is in fact an Apple bug. After AW dev clarified their understanding (new JIRA BINXI-10361), they have apparently contacted Apple, and Apple dev have assigned a RADAR# to this issue. I have contacted Apple Enterprise Support (and my Solution Engineer at Apple), but they don’t have access to the dev RADAR system and cannot provide any details whatsoever!!
So now we are expected to sit tight and wait for what exactly???
It has taken three months to arrive at this stage!
There are other elements of this situation that I also find hard to accept.:
1. AW support told me that there were only 5 customers validated against the JIRA – why is this so low. And I guess it means the issue is way down the priority list.
2. The fact that Apple registered a new RADAR for AW (instead of validating them against an existing RADAR) suggests that no other MDM vendor had already reported the issue??
3. AW still have not published any customer facing KB article about this behaviour – despite the fact I have repeatedly asked.
The best thing Apple Enterprise Support could advise is that I (we) give them details about how this issue is affecting our environments. The more customers they validate against the RADAR, apparently the higher priority it will be given.