I found this on page 26 of the pdf Adobe Publishing Process for iPad Apps that seem the origin of the problem:

If you publish a retail folio as public, it does not appear in the viewer library until Apple approves the in-app purchase and makes it available. However, the Distribution Service does not look to see whether the published folio is actually available. This creates a situation in which your customers can purchase a subscription and not be

entitled to any new content until the pending folio becomes available.

But for the apple approval you must set "retail and public" as also Adobe write in the same pdf

• Make sure the published folio statuses of the paid issue are set to “Retail” and “Public.”

I have this problem also with another magazine already avalible from the past year. Many of the readers of our magazine complain because after buying the subscription the latest issue is not avalaible but the subscription start with the next one.

In this case the app is rejected from Apple with this motivation:

We found that your app did not achieve the core functionality described in your marketing materials or release notes, as required by the App Store Review Guidelines.

After purchasing the Auto-Renewable subscription, the latest issue did not become available for download/reading. Please see below for the steps to reproduce the issue:

Apple only supports the subscription for a fraction of the time listed. I'm not sure if there's an exact science to it, but we've seen some subscriptions last only a few minutes. Please try to purchase again and let us know if you continue to have problems.

For what it's worth, I don't see any problems with the folio listed in your account.

Let me know what you find when you re-purchase the subscription in the sandbox.

Hi James, if I test again to purchase the subscription after tap on "buy" I recive this message: You're already subscribed this article.

I have two iPad and this happened on both. I read the only solution is test on another iPad but these mean I need to find someone who lends me an iPad, make a new mobileprovision files, make a new version of the app... any other suggestions?

If you publish a retail folio as public, it does not appear in the viewer library until Apple approves the in-app purchase and makes it available. However, the Distribution Service does not look to see whether the published folio is actually available. This creates a situation in which your customers can purchase a subscription and not be entitled to any new content until the pending folio becomes available.

Only workaround is to publish the folio as private while its getting approved by Apple and convert it to public once it is approved.

But the question now is: If is in private status Apple can check to approve the in-app purchase? this not may cause the rejection?

Apple's default behavior for subscriptions is to entitle customers to all issues between the start date and end date of the subscription, like a print subscription. When you sign up for a print subscription on November 15, you wait awhile and get the December issue when it comes out. But when people subscribe on a mobile device, they expect something to happen right away. That's why Adobe tries to make the most recent folio available. With an iTunes subscription, the person who subscribes on November 15 should get the November 1 issue. The glitch in the system is when you publish an IAP folio that Apple hasn't yet approved, that unavailable folio counts as the most recent folio. Users who sign up for a subscription while the published IAP folio is in review don't get the most recent folio.

It's possible to send the in-app purchase to apple for the approval in a private state and when you receive the notification "your app is in review" change in that moment the status in pubblic? off course is high risk tactics, if in that moment you can't access to the Adobe dashboard Apple will reject the in-app purchase...

I installed the v20 and selected in a new app version only for this and the result is the same in the sandbox: the "buy" choice remain after purchase the subscription.

The app was rejected by Apple for this problem and after this I created a new in-app autorenewable subscription but the first one, rejected, remain because no "delete" button is available. This may cause the problem?

Today in iTunes Connect create a new in-app and auto-renewable subscription with a new id, rebuild the app with v20 tools and the new in-app purchase ids, delete the free issue and the in-purchase issue in the adobe dashboard and upload from my original indesign files again (the free with date for pubblication yesterday the other with today date), tested all in the sandbox and... everything works fine, after the subscription purchase the button became "download". I was happy and I sent the new app to Apple again (fourth time) for the approval. After only few hours later Apple start the review (this was amazing because it usually takes at least 5 days). One hour later I receive the "reject" state again

After purchasing the Auto-Renewable subscription, the latest issue did not become available for download/reading. Please see below for the steps to reproduce the issue:

1. Launch app

2. Tap Subscribe

3. Select any of the options for subscribe, for example, 3-month subscription as shown in the screenshot 0496

4. Go through In App Purchase

5. After going through the In App Purchase, app updates the library

6. After updating the library, the latest issue, in this case 327 - Maggio 2012, is not available for download. It still has "Buy" button as shown in the screenshot 0497

Now the question is: why on my 2 ipads worked well but apple find again the same error?

Where's the problem? I really need help from some Adobe experts, the "Gold support" don't really support me at all... I wrote a long email with all the details and the answer was one line and after my answer they disappeared ...

In this case unpublish folio and change publication date manually from folio producer and then republish it.

Now I have the same problem on all our 4 magazine after update the apps to v20 tools!!!!!

When I purchase the subscription at the end of the process I have a "buy" button instead "download" ALSO IF I ALREADY PURCHASE THE SINGLE ISSUE!

No problems on the single purchase, only with subscriptions.

This is a HUGE problem that a very bad effect in our work. Now are 10 days since I asked for help to Adobe, also to Gold Assistance, but until now I don't receive any concrete answer to resolve this issue.

Isn't a problem related with the date (all are in the past) or reditions.

Can be a shared secret problem? I check and my shared secret is correctly show in the Adobe dashboard users preferences in all 4 accounts I use for the 4 magazine.

I asked here in the forum if I generate a new shared secret what would happen to our readers who have already purchased a subscription, but I don't receive any answer.

Sorry I'm not a software code expert, I'm a graphic designer who read the manuals and tries to follow the instructions like the most ADP users, if there're this kind of problem only Adobe employees can help us.

Now I see I'm not the only one and I hope Adobe can investigate deep the problem.

Magnificent. After making us go through all these supposed 'fixes' and 'known issues', it turns out it is a bug after all. I have been saying that since day one. They even wanted me to troubleshoot with them over the phone - but there was no way I was spending another minute helping someone I am paying a shitload of money to in order to fix their own ****. Interesting how it takes Adobe almost two weeks to acknowledge and another week to fix. We should get a refund of our monthly fees for the month of May.

Good to hear that a hot fix is coming very soon. I have exactly the same problem, and my app has been rejected twice by apple because of it. I've subscribed to the thread, and hope to hear something as soon as the hot fix is out.

The status page is still saying "No known issues have been escalated and are scheduled to be fixed in the next hot fix release." If the status page had been correctly updated we would never have released a Sprint 20 app.

As Bob did write earlier, the DPS team is working on a hot fix. If you want to release a viewer, you still can target the v19 viewer in Viewer Builder. If you are on a tight schedule, my suggestion is to use this functionality.

If you already have a v20 viewer in the market and you are experiencing this issue, you can consider downgrading the viewer to v19. I know this will have implications on content authoring.

This happens in a v19 viewer also. Our magazine is in the store with an approved v19 viewer and is causing the same problem. I have sent our development app (with proper UUID to Winston). This needs to be resolved soon!