Previous 1 2 Next 18 Replies Latest reply: Sep 18, 2014 12:57 PM by hepcat72 Go to original post
  • loyking Level 1 Level 1 (5 points)

    Hi gvocca.

     

    Unfortunately the two methods you described didn't work for me.

     

    For what it's worth, I called up Apple support to ask for help. The first support staff gave me the usual bit about restoring my devices despite my protests that I suspect that it's a cloud issue since more than one iOS device is affected.

     

    In the midst of restoring my iPad, I got a call-back from another staff who escalated my case up to a higher level. He helped me go through several steps to isolate the problem but still no go. The good thing is he is going to feedback to the back-end engineers to see if the problem can be looked into.

     

    Hoping to get an answer in the next few working days.

  • hepcat72 Level 1 Level 1 (15 points)

    Yay!  Great  loyking!  I had called and on-line chatted, but gave up when they wanted me to take drastic measures, as they recommended for you.  I'd even submitted a bug report about the issue, as I have for many other issues, but they never seem to do anything about those.

  • gvocca Level 1 Level 1 (0 points)

    Sorry to read it didn't work. In any case you did the right thing, I am going to do the same as soon as I have some time.

    Definitely there is no unique solution, it is not a transient failure there must be a bug somewhere

  • hepcat72 Level 1 Level 1 (15 points)

    Yup, not transient.  It is either a bug or corruption.  But if it was a bug, I would think the behavior would be more consistent, i.e. the same or similar solution would likely work for everyone, which is why I lean toward the corruption cause.

Previous 1 2 Next