Adobe Community : All Content - All Communities

Important iOS 8 Message

forums_noreply@adobe.com — Mon, 18 Aug 2014 22:57:27 GMT

Today’s v31.3 release (August 18, 2014) included an update to the v30 and v31 multi-issue viewers that addresses the following major problem with DPS running on iOS 8 beta:

On iOS 8 beta cover icons do not appear, downloaded folios are lost and cannot be viewed, and folios cannot be downloaded after the user launches the app for the first time, quits the app, and restarts it.

DPS customers are strongly encouraged to rebuild their applications to the latest v30 or v31 version and submit an update to Apple as soon as possible, before iOS 8 is released. Failure to update apps may result in DPS apps not functioning properly when iOS 8 is released publicly.

---

Helpful Links:

Digital Publishing Suite Help | What’s new in this release

Digital Publishing Suite Help | DPS Bug Fix Release Notes

Updating your existing Digital Publishing Suite app to Apple App Store | Adobe Developer Connection

v32.1 Released Today With iOS Download Failure Fix

forums_noreply@adobe.com — Wed, 01 Oct 2014 17:59:30 GMT

Hello,

This morning (Pacific time) the v32.1 release was made public. It contains a fix to the download failure issue that surfaced in the following forum discussion:

iPad folio "Cannot connect to server" download problem

This issue only affected v32 apps (v31 apps were not impacted).

The iOS Adobe Content Viewer with this fix is being submitted today for Apple approval, and may take a few days for approval and release.

For additional details on the release please refer to the DPS release notes:

Digital Publishing Suite Help | What’s new in this release

-nate

Apple verifyReceipt Service Down, In App Purchase is Failing

forums_noreply@adobe.com — Fri, 23 Sep 2011 03:52:22 GMT

Hello,

In App purchasing in DPS and non-DPS applications is failing because Apple's verifyReceipt service is down. Until Apple resolves this outtage any attempts to purchase content in a viewer will fail.

Currently there is one post in Apple's Developer Forums on this issue. If you have access to the forums you can view it here:

https://devforums.apple.com/message/541984

At this point the thread only confirms the problem. Hopefully this outtage is addressed quickly.

-nate at adobe