There can be many reasons for similar results in v19. Possible solutions are listed in the help document mentioned above.
One main reason is either 'hidden' future folios or incorrectly use of publication dates with renditions for iPad3.
Current Problem: Our plan was to push a Sprint 20 viewer update to the iTunes store today. With that in mind,I've built an entire folio using Sprint 20 tools.
Possible Solutions: If I have to downgrade my tools so that I can target a live Sprint 19 viewer, what happens to the Sprint 20 folio I've created? Do I need to re-create every article using the Sprint 19 Tools, or can I simply open all of the articles and re-add them into a new folio with Sprint 19 Tools installed?
Our app is in production, this is critical. None of our subscription customers can access content! Can someone from Adobe please
- post the estimated time/date for a fix
- confirm if V19 works or not
- explain how quality control didn't catch this critical bug
Johannes, if your subscription app has been experiencing the problems mentioned in this thread, download the 2.0.3 version of the Viewer Builder, rebuild your app, and submit it to Apple.
Until your app gets approved, the workaround that you can communicate to customers is to force quit the application and launch again. When the app is approved, this workaround will no longer be necessary.
Ok, so just for the record, what is viewer buildinger 2.0.3 changing then?
And what does rebuilding mean? Clicking through the wizard or recreating a
new app with the same assets?
NORDSUEDDESIGN Büro für digitale Kreation
+49 177 629 63 55
I would delete Viewer Builder and then download the newest version. Then I would edit the existing app by clicking through the wizard. And then download it and submit it to Apple. I'm not sure if it's necessary to click through the wizard or just download a new version, but I would do it just to be safe. But it isn't necessary to create a whole new app.
thanks Bob, thats what I think/do all the time.
Am 30.05.2012 23:12 schrieb "Bob Bringhurst" <firstname.lastname@example.org>:
Re: After purchasing the Auto-Renewable subscription, the latest issue
did not become available created by Bob Bringhurst<http://forums.adobe.com/people/BobBringhurst-+Adobe>in
Digital Publishing Suite - View the full discussion<http://forums.adobe.com/message/4452047#4452047
During our testing with Apps developed using Viewer Builder 2.0.3 we still encountered the same error where after purchasing a subscription, the button doesn't change to download. It still remains 'Buy'.
I have asked each app to be tested for subscriptions at least ten times, using ten different test accounts. On average 3-5 tests return the same above error. This makes it impossible for us to update the Apps we created using Viewer Builder 2.0, since the error still exists.
Any advise or further testing on Adobe's part?
Hope to hear something soon. This is really getting on my nerves.
We have the the same problem, even after the update. I´ve tested it on iPad1, iPad2 - it works and the "download" appears. On the new iPad - logged in with the same account - there is still the "buy" button.
We need a bugfix very urgent
The problem still exists!
Our app was build with Viewer Builder 2.0.3 but customers who subscribe are not able to download the recent issue if the customer uses an iPad 3.
We use renditions for iPad and iPad with Retina Display.
This must be fixed once and for all!
Please make sure your renditions have the exact same publication date. The way to ensure this is to set each manually, and then update the folio with the 'Uodate Content' checked. The publication date is a time/date field, and setting it manually is the only way to ensure that the files are precisely the same.
// James Roche
// I was born lucky
It Sees like the Publishing Day was the Problem. We have Positive Feedback of our subscribers. But Tanks for your Support.
Von meinem iPad gesendet
Re: After purchasing the Auto-Renewable subscription, the latest issue did not become available
I've received a number of notes from users with the same problem. For renditions to function, the following fields must be precisely the same:
Many users see their confusion in the publication date requirement, because our UI only shows the date but not the time. If you are creating multiple files for renditions, it is a requirement to manually set the publication date so it is consistent. If you rely on the default date, you will have problems with subscriptions because the timestamps are different. Here's an example of one of the users' accounts I've just investigated:
These dates appear as the same in the Folio Producer UI, but are clearly not the same. The fix for this issue is to manually set the dates to the same value, and update the content with "Update Content" checked.