Skip navigation
LC_Polka
LC_Polka Calculating status...
Currently Being Moderated

Viewer builder / Push certificates failure

Jul 19, 2012 12:59 AM

Tags: #push #builder #viewer #cs6 #certificat #csr

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

611 Views   7 Replies   Latest reply: LC_Polka, Jul 19, 2012 10:40 AM
 
Replies
  • LC_Polka
    Currently Being Moderated
    1. LC_Polka,
    Jul 19, 2012 6:44 AM   in reply to LC_Polka
    Report

    In addition : I've been able to complete the procedure an get the Viewer builedr compilation downloadable both as ipa and zip when not enabling the push notifications. Meaning the trouble obviously comes form the push certificates and their (weird) relation with mobilprovision certificates. Anyone experiencing this issue ?

     
    |
    Mark as:
  • Martin Lér
    Currently Being Moderated
    2. Martin Lér,
    Jul 19, 2012 7:51 AM   in reply to LC_Polka
    Report

    What exact error did you get from Viewer Builder?

     

    regarding CSR - i would recomend to prepare new CSR for each step (with different names), sometimes i had hard times with correct exports of p12 files, instead of developer certificate i've exported distribution one or vice versa. Then i help myself with new keychain, where i import certs from Apple one by one, export and clean keychain.

     

    Regarding mobileprovision relation - you need to recreate mobileprovision files after push certificates are created/enabled.

     
    |
    Mark as:
  • LC_Polka
    Currently Being Moderated
    3. LC_Polka,
    Jul 19, 2012 7:58 AM   in reply to Martin Lér
    Report

    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)

     

    Capture d’écran 2012-07-19 à 16.54.43.png

     
    |
    Mark as:
  • Martin Lér
    Currently Being Moderated
    4. Martin Lér,
    Jul 19, 2012 8:00 AM   in reply to LC_Polka
    Report

    Yeah, my favourite one, saw few times . Be very careful what you are exporting, i would suggest to create new keychain, import push certs from Apple there and export p12 push certs from this new keychain - one by one.

     
    |
    Mark as:
  • LC_Polka
    Currently Being Moderated
    5. LC_Polka,
    Jul 19, 2012 8:26 AM   in reply to Martin Lér
    Report

    Rrright. I'm going to dive back in the swamp of certificates. Creating new keychain mean ad dedicated keychain done especiallty for the Apple process ?

     
    |
    Mark as:
  • Martin Lér
    Currently Being Moderated
    6. Martin Lér,
    Jul 19, 2012 8:31 AM   in reply to LC_Polka
    Report

    Yes, add dedicated keychain.

     
    |
    Mark as:
  • LC_Polka
    Currently Being Moderated
    7. LC_Polka,
    Jul 19, 2012 10:40 AM   in reply to Martin Lér
    Report

    IT WORKED.

     

    To sum up :

     

    - new CSR for each step, with a different name Don't delete them.

    - name the certificates accordingly to the Apple relating profile (in my case they were two names : one for production, one for distribution)

    - no * ou / or _ in the password of the p12 certificates

     

    :-)

     
    |
    Mark as:
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