Viewer builder / Push certificates failure

hello DPS community,
I'm facing a quite bothering issue with the viewer builder : I'm unable to load my push certificates (both development and prod).
Following the guidelines of the Adobe Production Guide, here's what I do :
1 - generate a CSR certificate
2 - generate the Devopment certificate and the p12 file
3 - generate the Production certificate and the p12 file
4 - generate the Push notification APS Production certificate and the APN Production p12 certificate
5 - generate the Push notification APS Development certificate and the APN Development p12 certificate
6 - generate the Development Mobileprovision certificate
7 - generate the Distribution Mobileprovision certificate
My three questions are :
> should I generate a CSR certificate for each and every step of the procedure ?
> is the order of the procedure correct ?
> is there a specific name under which the certificates have to be saved, in order to be correctly recognized by the viewer builder ?
I've scouting through the pages of the forum, and have seen this issue has been raised quite a few times... but couldn't find an answer !
Any help welcome !
(I'm running CS6 on Mac OS 10.7.4)
Regards,
Laurent, Polka Magazine

It says (in french, roughly translated) :
Tag "Apple Production IOS Push Services:" or "Apple Production IOS Push Services:" expected not found in that certificate
and
Tag "Apple Development IOS Push Services:" or "Apple Development IOS Push Services:" expected not found in that certificate
(screenshot in french)

Similar Messages

  • Problems in Viewer Builder with Production Push Security Certificate

    Help! I've been trying for days now to build my iPad app in Viewer Builder, but I get an error message for my Production APNS Push Certificate and I can't get past the provisioning page. I've been on a dozen calls with Adobe, and we haven't yet been able to solve the problem.
    In the last round of tech support, I emailed my aps_production.cer and my .p12 version to Adobe. They say that it's valid and that it works on their end. I was advised to uninstall my Folio Producer tools and Viewer Builder. I did this, redownloaded and reinstalled everything and got stuck in the exact same spot.
    If anyone has had a similar problem and been able to solve it please let me know. I'm at my wits end with this one!

    I've been running into this same problem for DAYS now with an app I'm trying to build, except for me it's the production PNS p12 certificate.
    I've tried creating a new app several (countless, actually) times. Since I never get to the point where I can save it, I've had to create a totally new app at every attempt—is this what happened to you? And it eventually worked?
    I've also installed and uninstalled Viewer Builder a few times now and the same problem occurs.
    BTW, I send my certificate to Adobe and they said that it was valid.

  • Error in Viewer Builder importing PNS p12 Development Certificate

    I am getting an error in the Viewer Builder importing the PNS P12 Development Certificate.
    I have already made the certificate for PNS Production/Distribution and for Development.
    I was successfully able to import the PNS p12 Production/Distribution Certificate.
    When I went to the next field to import the certificate for PNS Development - error says "Not finding expected label 'Apple Development IOS Push Services:' or 'Apple Development Push Services:' in this certificate"
    I followed the same process for both PNS Distribution and Development Certificates.
    Why would one work and one not? The Viewer Builder gives very little feedback?
    Dave

    I've been running into this same problem for DAYS now with an app I'm trying to build, except for me it's the production PNS p12 certificate.
    I've tried creating a new app several (countless, actually) times. Since I never get to the point where I can save it, I've had to create a totally new app at every attempt—is this what happened to you? And it eventually worked?
    I've also installed and uninstalled Viewer Builder a few times now and the same problem occurs.
    BTW, I send my certificate to Adobe and they said that it was valid.

  • Viewer Builder signing failure for distribution viewer

    I'm having the following problem:
    I"m able to download the developer ipa from Viewer Builder with no problems, but when I try to download the distribution build, I get a VB error, "signing failure."
    this indicates to me that there is a problem perhaps with my p12 and mobile provisioning profile, but I've done all that correctly, as far as I know, and tried multiple times to reproduce from Apple's provisioning portal, but nothing works.
    is anyone else having this problem?

    Yes, I've been having this issue since last Friday. But, my ipa isn't working either....

  • SIGNING FAILURE (Viewer Builder)

    We are trying to generate the Distribution Viewer (.zip) from the Viewer Builder and are running into an issue.  This happens at the end of the export process when the link for the .zip is clicked. The developer version (.ipa) works fine.
    I have gone back to the Apple Developer Center and revoked all certificates and created them from scratch, along with new mobileprovision files and private key (p12). The error continues to persist.
    Is there any information you can give us on what may be causing the Signing to fail on the Distribution file?

    iIs there anymore updates on this? I'm having the same problem. I get a signing error when i try to get the ipa and zip. It worked the first time but i had to chnge one thing and have never been able to get past the signing error at the end again.
    I've went through every step multiple times, revoked all certificates and provisions, cleared out the keychain and basically re-did the whole process more times than i can count. Everything matches up as far as i can see but I still get the signing error which is in no way specific to what exactly is wrong with the p12 files. I do other apple development on the same machine and dont have problems publishing.
    So as theres no support system and the company have already paid for a single lisense which at the minute is used on an app we cant access does anyone have any idea how to solve this?

  • P12 push certificates problem

    Hello,
    we're currently facing a problem while trying to download a new viewer ipa/zip: while we've already installed the p12 push certificates through "notifications" panel with no errors -therefore assuming they are valid-, when back to the DPS App Builder the download links are still asking for the p12 certificates :-/ Is there any reported bug/workaround on this?
    Thank you for your assistance.

    App Builder is asking you for the certificates to sign the app, not the certificates for push notifications. They're separate certificates.
    Neil

  • Renewing Push Certificates?

    Hi,
    For newstand apps - do push certificates need to be renewed? Does anyone have information on how to do this?
    Thank you.

    1. No, Apple does not send a notification. If your dev and dist p12 cents expire, your app will be rejected at some point in the submission process--I don't recall when. It might be while building the app. If you don't update your app, expired dev and dist certs don't matter. Users can still use your app as before. You can even submit an app with expired push certs and your app will work fine--except for push, of course.
    2. The distribution app in the store and on users' devices will still work if the distribution p12 is expired, but you'll need to update the cert before you resubmit a new version of the app. That's my understanding. An expired push production cert affects only push itself. If your push cert is expired, you'll get an error message when you click Notify. Users can still subscribe, download, and view articles regardless of push, but they won't get badges or background downloads.
    3. If your dev and dist p12 certs are expired, just update them before you submit a new version. You don't need to rush to do it. For the p12 push cert, I don't believe that you need to resubmit the app. I believe that if you revoke and rebuild the push certs, the change is registered with Apple, and you can click Notify without an error. I'll be testing this soon.

  • Uploading with viewer builder v11

    Is it still possible to upload folio files with viewer builder v11?
    I know, it's prerelease, but for various reasons we have to use this workaround.
    Today we are getting messages saying "communication with server failed".

    @Matthew Laun
    There is one information missing in this conversation: we of course immediatelly built a new app version and uploaded it to Apple.
    We still desperately want to publish our issue as soon as possible, old or new app.
    I cannot believe that our distribution push notification certificate is invalid. If that were the case, I wouldn't have been able to build a new version of the app on wednesday. I also wouldn't have been able to upload it to Apple. That said, i don't believe any of our certificates are invalid.
    If there is a misunderstanding, please explain.
    On the other hand, there seems to be a misunderstanding about the "please update your app"-topic. I know what the message means and I know why and when it is shown. As you can read above, the problem was, that the message didn't show up anymore.
    It doesn't matter any more (maybe it had to do with us changing the product ID back and forth; only thing that comes to mind). We installed the app again and now the "plaese update your app"-message shows again. Which is what we wanted, rather than showing a sandbox-purchase-box.
    And last, i noticed you marked your own answer as "correct answer" again.
    Allow me to note that I am still not convinced. It simply doesn't work.
    And i hope you understand the frustration on our side as this is a highly serious problem for us. We are three days behind publication date and losing trust of our readership.

  • Viewer Builder error: 'Signing Failed'

    What does the View Builder Error 'Signing Failed' mean when I download my developer or distribution apps from Viewer Builder? The dev IPA and dist ZIP files appear to download correctly despite the message, so what is it trying to tell me?
    Ali

    Righty, I turn to page 15 of the 'Adobe Publishing Process for iPad Viewer Apps' PDF as provided by my Adobe reseller. All the screenshots are blurred but no matter, I can probably muddle through.
    The chapter is headed 'Setting up Apple Push Notification Service (Optional)'. At the end of the introductory text is a paragraph reading: 'Important: If you have already created an App ID and certificates, you can configure your App ID to enable push notifications. You don't need to create new development and distribution certificates. However, you do need to create new mobileprovision files.'
    Fine, that's clear. My app exists already: I'm just planning to build an updated version, so naturally I have an App ID. The paragraph has told me that I don't need to create certificates, but I do need new mobileprovision files.
    The first section after this is headed 'Creating a push notification certificate'. OK, I shall ignore this section because, as explained above, I apparently don't need to create any certificates.
    The next section after this is headed: 'Creating a .p12 APN certificate'. Again, my understanding is that I don't need to create any certificates, so I shall ignore this section too.
    Oh... I've already reached the end of the chapter on 'Setting up Apple Push Notification Service (Optional)' and I haven't done anything. How do I create the special mobileprovision files that I'm supposed to need for APN?
    Well, this seems odd, so I flip back to page 6 and the beginning of the chapter headed 'Creating Certificates', seeking clarification. In the introductory text is a paragraph that reads: "If you want to enable the Apple push notification service (APN), create a separate certificate that you can upload to the Adobe fulfillment server. See the section on setting up push notifications for details.'
    So this chapter is telling me that I need to create a new certificate for APN, but no mention of mobileprovision files, yet at the same time tells me to read a chapter that tells me that I don't need to create new certificates for APN and I do need new mobileprovision files.
    I'm afraid I can't make any sense of this, and neither can anyone I send these instructions to. Luckily for us, APN isn't particularly significant for a twice-yearly magazine. But it would be nice to get a handle on it in case we launch a weekly.
    Ali

  • Your Push Certificate has expired

    Hi
    I created two push certificates both set to expire on Sep 5 2013 however when trying to send a notification I get the meesage "Your push certificate has expired. To upload a valid certificate, rebuild your app in Viewer Builder and retry sending the notification."
    Any ideas?
    Thanks.

    Hi,
    I found that the process was slightly different for me than what was described in the guide. On my mac mini running lion it didn't put the certificate under the private key so I needed to select both the certificate and the private key and then export to p12.
    Hopefully this will help.

  • How to open Viewer from other apps? - App 'URL Scheme' has disappeared from Viewer Builder!

    Hello
    The 'URL Scheme' option in the Viewer Builder did let me to specify a url that made other apps open my viewer. But this option has disappeared from the newer version of Viewer Builder. So. How do I do now to let other apps open my viewer?

    Is there a spacial reason that the URL scheme option was taken away from ordinary Multi-issue viewers? It was there in earlier version. I'll explain our situation:
    Our client want to publish corporate information; annual reports etc, with DPS. Not really magazines or newspapers you subscribe to.
    We are making another app where they publish news articles, videos etc. In that app, we want to have a link which opens the viewer with their publications.
    To make this simple thing work, we have to create a 'subscription' to content which is not relly good for subscribing (it is free and announced with push anyway). We also have to tell the client to create Privacy Policys etc for this. A lot of hassle for something we do not really want.
    Any chance that this option will come back in v19?

  • No Folio File field in Viewer Builder?

    For some reason I do not have a field to associate a folio file to a viewer in the Viewer Builder. This greatly impairs the user experience.
    I'm using Indesign 5.5, have downloaded the most recent updates from the DPS site and have cleared the cache of my browser. I've also released an app in pre-release but this is the first one in the new interface.
    The documentation in the DPS help section references the Folio File field in the Basic Settings panel of Viewer Builder but I've navigated through the Viewer Builder and see no place to actually designate the folio to be built into the viewer. What am I missing?
    I can see where folios published to the account will automatically populate the viewer and from a developer standpoint maybe there isn't a need to associate a specific file to build and release the viewer itself, but the app for this viewer (that was successfully built in the DPS VB with confirmation as completed) was rejected by Apple because from their point of view it's an app with no content (no actual folio files for an end user to look at.)
    Thanks!

    Thanks for the response Bob.
    Yes, multi-folio viewer is what I need for a series of digital magazines. Sorry, in pre-release the multi-folio viewer was built and pointed to a folio file as with a single viewer. The new release is fantastic, I'm not nostalgic. Just trying to troubleshoot.
    After your post I assumed then that the viewer must automatically read what's been published and auto-populate the viewer. The problem was that I wasn't seeing the folio in the viewer on my ipad (loaded with iPhone Config Utility) but was seeing it through the generic Adobe Viewer. I checked certificates, settings, etc. in the viewer and everything checked out fine. I then went through publishing options.
    What I found was that when the folio is set to free, it is viewable in the custom viewer we've created. When it is set to retail (we are planning on selling this issue) it is not. Has anyone else experienced this? Have I configured soemthing wrong? I re-checked documentation and don't see any additional settings needed for retail release. Is the viewer expecting some additional info from the App Store to process the display icon of the folio for purchase?

  • Viewer Builder on PC in Future?

    Are there any plans to make the viewer builder available for PC users?  Or is that not ever possible?  I don't have access to a Mac and have no way of building a custom viewer....
    Thanks,
    Greg

    Making the Viewer Builder available on Windows to support building Android/Amazon viewers is on the roadmap, but it keeps getting pushed out for other features.

  • Just needed some clarification regarding the Viewer Builder and actually publishing your App...

    If someone could let me know if my understanding is correct, that'd be a huge help... So I've designed my publication in InDesign and exported the .zip file from the Folio Producer. I've created all of my certificates/splash screens/icons. Lastly, I just recently went through the steps of the Viewer Builder. I'm now at the stage of this process that requires me to purchase the $395 single edition so that I can enter the serial number in the last stage of the Viewer Builder. Now, to my knowledge, once I get the serial number, Viewer Builder will then give me access to an .ipa file and a .zip file. The .ipa file is for me to test on my iPad, and the .zip would be used to distribute to the App Store. I guess this is where I get confused... Let's say after I test the .ipa on my iPad, I don't like some part of my publication. I know how to update my own documents obviously, and I understand that I would have to export another .zip file from the Folio Producer, in turn requiring me to edit the exported folio link in the Viewer Builder. If I had to do that, would I need to purchase another single edition serial number since the original App was edited? Or would the same serial number apply since I'm editing that same App in the Viewer Builder? My next question is somewhat similar. Let's say all of the information is up to date and I go ahead and publish the App to the App Store. However, maybe a month later or some time in the future, I needed to update a phone number or email address--some little detail like that. Again, I understand that I'd have to update the export link in the Viewer Builder, but would I then need to create a new app since my app was already published? Would I then have to purchase another $395 single edition serial number just so that I can update my information? This seems to be the only thing in this whole process that I could use some clarification on so that I don't run into any surprises in the future. Any help would be great, thanks!

    Hi Joshua,
    When you have purchased the serial, you can rebuild your app with your updated content, as long as you use the same bundleID (applicationID), that is tied to your Apple mobile provisioning profile. The serial number is valid for a one year period.
    After you have submitted your app to Apple and it has been approved, please read: http://forums.adobe.com/message/4172167#4172167
    With kind regards,
    Klaasjan Tukker
    Adobe Systems

  • Viewer Builder and Title ID

    This is my first time publishing a magazine using the Viewer Builder.
    Which ID should I use in the first window inside the Viewer Builder, ther it asks for "Title ID"?
    Can anyone help me?
    Thanks
    Leikny

    I ment in the Accont Administration where I give trysilmag12  an application role. What ever, I'm past that "level" now
    Its a Multi-issue App I wont to create, and I have read and watched a lot of videos and iformation, but I have not find exactly information about the Provisioning step in Viewer Builder.
    And I see that I nedd certificats. I have create an developer.p12 anda a distribution.p12 certificate (but if they are right I dont know ...)
    Is it a place where I can find more information or can you tell me a easy way ;-)

Maybe you are looking for