Skip to main content
Inspiring
May 27, 2018
Answered

Certificate warning when submitting to Apple Store

  • May 27, 2018
  • 3 replies
  • 1276 views

Even though I have compiled with latest AIR 30.0.0.103 Beta I still have a warning about certificate:

Certificate Expired - The signing certificate "CN=Apple Worldwide Developer Relations Certification Authority, OU=Apple Worldwide Developer Relations, O=Apple Inc., C=US" with serial number 25 used to sign Shapes In Motion.app has expired. Learn more (https://help.apple.com/xcode/mac/current/#/dev154b28f09).

In the release notes of AIR 30.0.0.103 Beta there is nothing under know issues tab. So why is this issue still present?

I am using Flash Builder 4.7 with latest Windows 10 and AIR 30.0.0.103 Beta SDK.

This topic has been closed for replies.
Correct answer chaky

This is solved in official AIR 30 release. I no longer have certificate warning when submitting app to Apple Store.

3 replies

Known Participant
June 11, 2018

I got the same error when submitting an update (Air 29) but it got approved anyway

chakyAuthorCorrect answer
Inspiring
June 10, 2018

This is solved in official AIR 30 release. I no longer have certificate warning when submitting app to Apple Store.

Participating Frequently
May 30, 2018

What do you mean there is nothing under known issues in the release notes?

The issue has been know for a few weeks and I've seen it listed in the last 2 release notes of AIR 30 Beta. The below is taken from the known issues in the release notes

AIR

  • ETC2 with Alpha content having LZMA/JPEG-XR compressions have black dots/lines when renderd on Android
  • Certificate related warning appear on submitting Apps to Apple AppStore.

Link to the full release notes:

https://fpdownload.macromedia.com/pub/labs/flashruntimes/shared/air30_flashplayer30_releasenotes.pdf

chakyAuthor
Inspiring
May 30, 2018

Participating Frequently
May 30, 2018

chaky​,

You're the one reading it wrong. Anything listed under known issues remain to be issues, the date refers to when the issue was initially added to the list of known issues. But I get how you can get confused.

Only when the certificate issue is listed under the list of fixed issues, you'll know it is resolved.