1 person found this helpful
1. Unless you have a specific reason for not doing so, always choose the most current viewer version (in this case, v14). Viewers are backwards compatible.
2A-B. See the Companion Guide PDF for details. To enable push, you need to (1) reconfigure your App ID, (2) re-create your mobileprovision files (not your p12 certificates), and (3) create a production push certificate.
Thanks Bob! Giving it a go now.
I think I am closer, but still not there. First of all, I have an "iPad Publishing Companion Guide" pdf from Drop 9 of the prerelease. I cannot find a newer pdf if it exists.
Anyways, I went to the IOS Provisioning Portal and enabled push notifications for my App ID. I followed the steps and generated the two APS certificates, downloaded those and installed them into KeyChain.
I then created the new mobile provisional files and downloaded those.
In Viewer Builder>Certificates I was able to attach the new Mobileprovision files. But when I tried to attach the APNS Certificates they are greyed out and I can not select them. I'm not sure why.
There is an option called "Enable Push Notifications" or something like that. Did you select it?
An updated version of the Companion Guide PDF is in the Downloads section of the prerelease site. We're trying to find a better way to make it available.
I have enabled push notification (for my Dev & Distri) app. My app is still not submitted, I am testing. I have publish public folio in my app. But I don't know why I haven't the red badge that tell that a new file is available. Even if i restard my Ipad. When I open my app, I've got the message telling me to download the new file.
So I don't know what I missed when creating my both Dev & Distri push notification...
Here is some screen shot.
Keychain : ? The date is still OK. So I've dowload the both .P12 push not.
Apple dev :
And I've enable Push not. when creating my app in the Viewer Builder.
Any idea ??
I wasn't able to test push on my development app either, but it works fine on the actual app. Don't be concerned about push notifications failing to appear in the test environment.
Well, test environment is for testing therefore I can not agree that we should leave that subject while having developmnet build. If it is not working correctly in real life it means submitting new app to Apple just because we were unable to test it. Moreover I am sure we tested PUSH when having VB 1.4 developmnet builds!
By the way - we are also unable to test PUSH now.
Yes it is true, it is annoying to not been able to test now, because if it doens't work when my app is submitted it will be a big problem for me and my clients will not appreciate at all (that readers haven't push not. when new folio is available).... Don't like to stay in "potentially working" situation. I'd like to be sure.
Do push notifications work in a Single Issue app?
No, Adobe push notifications activate badges only when a folio is made public. You can't send push notifications for updates.