Post not yet marked as solved
Glad to see I'm not the only one.
Post not yet marked as solved
Same trouble here. We have three separate and still actively used iOS enterprise apps and have had an Enterprise membership for ten years or more, never had a problem renewing. This time they refused renewal because they said we did not meet the requirements, specifically that we don't have more than 100 employees. That's nonsense. In the ten years of our membership, we haven't gone below probably 250 employees, and now we are at 300 or so. I don't know how they verify that, but it's not right. I called support and two people told me firmly that it is "not appealable." I spoke later on to someone else who seemed to understand my problem and wanted to be helpful. So after that conversation and after sending the documentation to support our claim of > 100 employees, our status went from Refused to "We'll review and let you know..." I guess that's a step in the right direction, but that's all I have seen for three weeks or so.
Post not yet marked as solved
I know this is years old, but I just encountered this problem on a couple of my enterprise apps, and I found that all I need to do is recompile the app in XCode, and then have users re-install it. It has worked fine every time.
I include this for people like me who are just now seeing this problem.
Post not yet marked as solved
There seems to be some progress. As of now, the system is at least not throwing a certificate error, but the iPhone app on the development device is not receiving the notification.Edit: I no sooner posted this and tried again, and it came through. I think we are all clear now.
Post not yet marked as solved
It's still not working for me.
Post not yet marked as solved
This is troubling. My production is still working, so I hope it's not a widespread problem.
Post not yet marked as solved
UPDATE: I attached a packet sniffer to my development machine and determined that the amount of data being returned from the sandbox server compared to the production server is vastly different. I don't know it that really means anything, but it seems to validate the concern that it's a problem with the sandbox server.
Post not yet marked as solved
Glad to see it's not just me. I've been wringing my hands that I might have screwed something up.
