Apple Warning Emails

Apple Warning Emails


1. Your certificates expire in 30 days



The iOS certificates created for publishing your app on your Apple Developer account  are valid for one year only (12 months for the iOS distribution certificate and 13 months for the push certificate). This is why Apple warns you 30 days before about the expiration. 

What consequences does it have?

Your distribution certificate expires in 30 days 
This does not affect your app already published on the App Store. The distribution certificate only needs to be renewed if you have to rebuild the app or send a new version of your app to the store. 

Your push certificate expires in 30 days 
When the push certificate expires, the push notifications will stop being sent to your iOS users. 

Unless your app has to be rebuilt and resubmitted to the App Store, it is not necessary to renew your certificates right after Apple sent this message. It's enough to renew them a few days before the push certificate expires.

How to have your certificates renewed?
  1. Muse mBaaS is in charge of your iOS app publication process - request our team to renew the certificate. Learn more about how to request this here: MB Takes Care - Updating iOS Certificates.
  2. You are in taking care of the iOS publication process yourself - follow the procedure described in our documentation: iOS - Update the certificates in the backend.


2. Potential Loss of Keychain Access



This email can be safely ignored. Apple sends you this warning when your app has been transferred to another Apple Developer account.


3. "The build has Completed Processing"



This informative email means that the build has been sent to the Transporter and has been processed. At this point, the submission can be finalized on App Store connect.


 4. Rejection Email

If Apple informed you by email of the rejection of your app, please read this documentation first: Apple Rejection.

In case the online help didn’t cover the rejection reason mentioned by Apple, please contact our Support.

For an effective resolution of the situation, make sure to copy and paste the full message from Apple, including the screenshots or crash logs attached to the message, if any.



    • Related Articles

    • iOS - Verifications Before Submitting the App to Apple

      Wether you choose to submit your application by yourself or Muse mBaaS to submit it for you, you will need to make sure it complies with Apple's rules and more precisely the App Store Review guidelines. Here is a checklist of everything you should ...

    • Android - Send Google Play a Document Proving Intellectual Property

      Before submitting your application to Google Play, you must ensure that the content of your app or its metadata are not violating the Google Developer Content Policy. Google rejections are often related to Impersonation and Intellectual Property ...

    • iOS - Create your Apple Developer Account (Mandatory)

      1. The Apple Developer Account is Mandatory to Create your iOS Native App The Apple Developer account is necessary so your iOS native app can be generated, tested, and submitted to Apple on iTunes Connect. Apple is very strict regarding the ...

    • iOS - Change Apple Developer Individual Membership to Organization

      Apple's 4.2.6 guideline is very clear about the use of the Apple Developer account: it must belong to the final owner of the app, who must be clearly identified. You can read the 4.2.6 guideline here: ...

    • iOS - Compliance with Apple's 4.2.6 and 5.2.1 Guidelines

      1. Compliance with Apple's guidelines Since the summer of 2017, Apple's rules have been tightened regarding the compliance of the Apple developer accounts. How it impacts Muse mBaaS and You : Apple's 4.2.6 and 5.2.1 guidelines are very clear about ...