I promised an update as soon as I had one, and checked in on this first thing this morning. Unfortunately we were rejected again. We understand the importance of getting this resolved quickly and we are opting for the fastest path to approval, which means a targeted change to the content viewer. I sat with the engineer just now and the change is complete. We need to do a verification on the resulting viewer, then we'll re-submit to Apple.
In case people are concerned about their own custom viewers being rejected, this issue is specific to the Adobe Content Viewer. It is not an issue in any custom viewer you may create.
I'll keep everyone updated as I have new information.
Neil
I aprpeciate the additional info, Neil. Thank you.
As an aside, when considering the various platforms to get our content to the iPad and other tablets, the ease with which we can test is a heavy consideration. The Mag+ system, for example, is slick and doesn't seem to get hung up with the approval issues Adobe is having. I recognize the difficult position Adobe is in with Apple's approval policies, but it seems Adobe is a big enough player to ensure their Content Viewer app is a high priority to Apple's approval team. And if that's simply not the case, Adobe needs to develop a different system for on-device testing.
But again, my main reason for posting is to thank you, Neil, for shedding additonal light on the matter. It helps.
Thanks,
Chris
If you are a Professional or Enterprise Edition customer then yes, you can create a custom Adobe Content Viewer using Viewer Builder and use that to preview v19 content today. We specifically added this feature so pro and enterprise customers do not have to wait for the ACV to be approved by Apple before experimenting with new features in a given release.
Neil
That is the best news I have heard all day, or week or whaterver it has been.
The frustration at not being able to show my clients the progress we have made on a major project has been a b---ear.
Thanks much for keeping us informed as this saga has unfolded.
Good job Neil (and you too Bob)
Doug
Thanks Neil!
Thanks for keeping us in the loop. I know it takes some extra bit of effort to convey this information publicly...but even small updates like this can be extremely helpful in our own conversations with customers (both internal and external).
Hopefully the re-submission sails through App Review!
Mike
I hate Apple for such behaviour.. such monstrous company as Adobe should wait when it's majesty Apple will start reviewing it's content viewer. I am 100% sure that the only purpose of it is to delay Adobe and show how bad Adobe is.. clients waiting, clients angry. If Adobe were 'frendly' company it would be done in 30 minutes after submition (rather than 1 month). I don't how what's going on behind the scenes but such huge companies should have extra priority, now it looks like Adobe is in queue with 1000s rubbish apps made by kids... 'oh this farty app is not cool enough.. who is next? Adobe? oh, let's look closer at current app.. pressing the button..blurp..cool, Adobe can wait'
Good afternoon everyone. Apologies for the delay in posting today's update, I was stuck in meetings. We are still in review.
Note that I will be away for the next week, so Bob has graciously agreed to take over posting updates on this thread while I'm out. Hopefully when I'm back no updates are needed!
Neil
Looks like we are having some problems.
I did the update and works fine.
After that, I asked to my client do the same. There was an update, she downloaded it and did'nt work.
So I deleted mine and downloaded it again, and the same error ocurred to me.
Minutes later appeared an update at App Store to me, asking me to update the Adobe Content Viewer, so I did and than it worked.
But my client, it isn't still working.
Any clue to solve that?
North America
Europe, Middle East and Africa
Asia Pacific