Successfully!

Error!

Uploading iOS Certificate

  • Last update:  2023-06-07
  • Overview

    This article introduces the preparation before packaging the app. If you need to generate an iOS version of your app, follow the operations below.

    Obtaining a Certificate

    For details about how to obtain an iOS certificate with an enterprise developer account, see:

    1. Applying for an iOS Enterprise Developer Account

    2. Obtaining iOS Certificate

    Note:

    1. FanRuan App OEM only supports obtaining iOS certificates through enterprise developer accounts, but does not support certificates obtained through personal or company developer accounts.

    2. If the iOS certificate does not include the push notification function, the same function of FanRuan app cannot be used.

    Configuring a Certificate

    Logging into FanRuan Market

    Log into FanRuan Market, go to User Center, find App Packaging > iOS Enterprise Certificate under User Information.:

    Note: When going to the page, if you do not purchase the service, you need to contact our sales personnel to purchase it first.

    Uploading a Certificate

    Go to the App packaging page, select iOS Enterprise Certificate, upload xx.p12 and xx.mobileprovision files, and enter certificate password.

    After uploading, click Check Certificate to automatically read bundle id and expiration date.

    If bundle id contains a wildcard, the input box will prompt: The current certificate bundle id is xx.xx.*, and the * wildcard can be customized.

    In this case, you can manually edit bundle id. The * can be replaced with any combination of numbers, uppercase and lowercase letters, and periods. After modification, verification is automatically triggered.

    Note:

    1. If the modified bundle id does not comply with the rules, it will prompt: Certificate verification failed, appID/bundle id format error.

    2. If the certificate verification fails, it will prompt: Certificate verification failed, error code: XXX. For details, see App OEM Error Code List.

    Saving a Certificate

    Click Save, the configured iOS enterprise certificate is shown in the following figure:

    Replacing a Certificate

    iOS enterprise certificate is valid for three years, and the Profile file is valid for one year.

    The unique identifier of the app is the AppID, which is generated by the Profile file and can only be used for up to one year.

    When the app expires, it will be unavailable to you, so it is necessary to use the latest certificate or Profile file to repackage the app and distribute it to end users for updates.

    After repackaging, as long as the Profile file corresponds to the same AppID, the newly generated app can be updated and overwritten on the original app without uninstalling and reinstalling.

    Applying for a New Certificate

    You can refer to sections “Exporting a .p12 Certificate” and “Exporting a .mobileprovision File” in Obtaining an iOS Certificate to Reapply for a New Certificate.

    Note:

    1. Do not revoke the certificate easily (valid for three years). After revoking the certificate, you cannot use any apps related to the certificate.

    2. Before revoking the certificate, you should ensure that all end users using the certificate have updated the app to the one packaged with the new certificate.

    3.You can apply for up to two certificates at the same time.

    4. It is recommended to create a new Profile file (associated with the same AppID) three to six months in advance before the Profile file expires (valid for one year), and use the new file to package and distribute the new app to end users for updates.As the Profile file is valid for one year, you are advised to create a new Profile file (associated with the same AppID) three to six months in advance before the expiration date,

    Uploading the Certificate

    Log into FanRuan Market, go to the App Packaging page, click Apply for certificate modification, and enter certificate expired replacement as the replacement reason . FanRuan personnel will review and provide feedback within one work day.

    Note: It is recommended to adopt version update control. For details, see How to Achieve Version Self-Management. When the app needed to be update, the user side will automatically prompt that there is a new version and force updates.


    Attachment List


    Theme: Fine Mobile
    Already the First
    Already the Last
    • Helpful
    • Not helpful
    • Only read

    Doc Feedback