Skip navigation
Replies 1 2 Previous Next
  • Currently Being Moderated
    May 29, 2012 6:32 AM   in reply to Onaznam

    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.

     

    -Klaasjan

     
    |
    Mark as:
  • Currently Being Moderated
    May 29, 2012 7:53 AM   in reply to Siduno

    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?

     
    |
    Mark as:
  • Currently Being Moderated
    May 29, 2012 8:07 AM   in reply to chris_jzd

    It should be enough be simply re-adding all articles with the v19 tools

    installed. I think there are no feature-differences between these two

    versions.

     

    —Johannes

     
    |
    Mark as:
  • Currently Being Moderated
    May 29, 2012 8:14 AM   in reply to Johannes Eckert

    Excellent, Thanks Johannes!

     
    |
    Mark as:
  • Currently Being Moderated
    May 29, 2012 8:19 AM   in reply to Klaasjan Tukker

    I have checked the help document and none of those apply to use. We are using v19 and it still happens.

     
    |
    Mark as:
  • Currently Being Moderated
    May 30, 2012 12:08 AM   in reply to Siduno

    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

     
    |
    Mark as:
  • Currently Being Moderated
    May 30, 2012 6:02 AM   in reply to PadraicWoods

    Hi,

    a fix was deployed about an hour ago for this issue.

    Please note that apps need to be rebuilt to benefit from the hotfix.

    Apologies for the inconvenience.

     
    |
    Mark as:
  • Currently Being Moderated
    May 30, 2012 6:14 AM   in reply to Christophe_Jossic

    and do we NEED the new viewer builder 2.0.3, will there be an announcement, a change log or something? or will apps from viewer builder 2.0.2 work?

     

    —Johannes

     
    |
    Mark as:
  • Currently Being Moderated
    May 30, 2012 6:38 AM   in reply to Johannes Eckert

    Johannes,

    I tested while still on 2.0.0 as well as 2.0.3 and got the correct behaviour after purchasing a subscription

     
    |
    Mark as:
  • Bob Bringhurst
    4,649 posts
    May 29, 2007
    Currently Being Moderated
    May 30, 2012 8:25 AM   in reply to Christophe_Jossic

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    May 30, 2012 12:41 PM   in reply to Bob Bringhurst

    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?

     

     

     

     

    --

     

    Beste Grüße,

    Johannes Henseler

     

    NORDSUEDDESIGN Büro für digitale Kreation

    PORTFOLIO nordsueddesign.de

    BLOG frischmil.ch

    Alfterstraße 16

    50969 Köln

    +49 177 629 63 55

    UMSATZSTEUER-ID DE244595644

     
    |
    Mark as:
  • Bob Bringhurst
    4,649 posts
    May 29, 2007
    Currently Being Moderated
    May 30, 2012 2:12 PM   in reply to Johannes Eckert

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    May 30, 2012 2:25 PM   in reply to Bob Bringhurst

    thanks Bob, thats what I think/do all the time.

     

    —Johannes

     

    (mobil gesendet)

    Am 30.05.2012 23:12 schrieb "Bob Bringhurst" <forums@adobe.com>:

     

    **

       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

     

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 14, 2012 2:42 AM   in reply to Johannes Eckert

    Hi Everyone!

     

    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.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 3:01 AM   in reply to Onaznam

    Hoping for some feedback from other publishers here. Is anyone else still encountering the above issue or has 2.0.3 addressed it for everyone?

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 20, 2012 8:36 AM   in reply to Onaznam

    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

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 22, 2012 10:38 AM   in reply to Bob Bringhurst

    What do we do for customers that have not updated their app? There should be a check on launch that requires them to update the app.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 24, 2012 12:59 PM   in reply to dhoferer

    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!

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 24, 2012 1:18 PM   in reply to pablo4242

    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.

     

    If this doesn't solve your problem, please write to me at roche@adobe.com<mailto:roche@adobe.com> with your product id's and I will help investigate.

     

    Thanks.

     

    // James Roche

    // I was born lucky

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 24, 2012 2:00 PM   in reply to jamesroche

    It Sees like the Publishing Day was the Problem. We have Positive Feedback of our subscribers. But Tanks for your Support.

     

    Best Regards

     

    Dominik

     

    Von meinem iPad gesendet

     

    Am 24.06.2012 um 22:18 schrieb "jamesroche" <forums@adobe.com<mailto:forums@adobe.com>>:

     

    Re: After purchasing the Auto-Renewable subscription, the latest issue did not become available

    created by jamesroche<http://forums.adobe.com/people/jamesroche> in Digital Publishing Suite - View the full discussion<http://forums.adobe.com/message/4517277#4517277

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 25, 2012 8:34 AM   in reply to jamesroche

    After setting the publishing dates of the two renditions again it worked.

    Seems that there was something clogged in the publishing pipeline.

     

    So the reason was not the Viewer Builder.

     
    |
    Mark as:
  • Currently Being Moderated
    Jun 25, 2012 9:30 AM   in reply to jamesroche

    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:

     

    1. Folio Title
    2. Product ID
    3. Publication Date

     

    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:

     

    <publicationDate>2012-06-13T10:23:37Z</publicationDate>

    <publicationDate>2012-06-12T22:00:00Z</publicationDate>

     

    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.

     

    Thanks.

     
    |
    Mark as:
1 2 Previous Next
Actions

More Like This

  • Retrieving data ...

Bookmarked By (0)

Answers + Points = Status

  • 10 points awarded for Correct Answers
  • 5 points awarded for Helpful Answers
  • 10,000+ points
  • 1,001-10,000 points
  • 501-1,000 points
  • 5-500 points