Jump to content

[TOPIC: topicViewTemplate]
[GLOBAL: userSmallPhoto]
Photo

Code Signing Error: Invalid Provisioning Profile
Started by crawfdc47 Jun 22 2019 10:09 AM

4 replies to this topic
code signing provisioning profile certificate build

Best Answer crawfdc47 , 29 June 2019 - 09:53 AM

So, I was finally able to figure out what was causing the code signing error: It turns out that I had not registered my iPhone under the devices section on the Apple Developer portal. After registering the device and adding building permissions for the device to the provisioning profile, I was able to successfully build the app and install it on my iPhone.

 

I overlooked this before because I already had an iPhone registered with my Apple Developer account that I assumed was my iPhone, but actually turned out to be an iPhone I had borrowed from a family member which I had registered with my account a few years ago (if there was a facepalming emoji available, I would insert it here). Apparently, the Apple Development Technical Support Team was not able to identify this as a possible source of my error when I requested technical support though.

[TOPIC CONTROLS]
[/TOPIC CONTROLS]
[modOptionsDropdown]
[/modOptionsDropdown]
[reputationFilter]
[TOPIC: post.html]
#1

crawfdc47

[GLOBAL: userInfoPane.html]
crawfdc47
  • Enthusiast

  • 38 posts
  • Corona SDK

I cannot build any of my apps for iOS (development) due to a code signing error. I have contacted Apple Technical Support about this issue because I initially thought the problem was on their end, but they have since told me they cannot help me because they think the issue relates to Corona's software. The versions of Corona SDK I have used which reproduce the error include 2019.3326, 2019.3480, 2019.3486, and 2019.3490.

 

I noticed an odd behavior occurs when Corona finishes building the apps. After the build is complete, a login prompt pops up asking me to enter my password for code signing the applicable provisioning profile (see attached screenshot). When I enter the incorrect password, the login prompt wiggles side to side indicating it rejected my password as expected. However, when I enter the correct password, the login prompt disappears momentarily and then reappears to ask me to re-input the password. When I re-input the correct password a second time, the login prompt disappears and does not reappear. I then receive a notification that the app has been successfully built. However, I always receive an error message that code signing has failed when I attempt to upload the built app to my iPhone via Xcode (see attached screenshot).

 

Keychain access shows my development certificate and corresponding provisioning profile as valid. My membership status as an Apple Developer is also active as I just renewed my membership, so my certificates are not expired. I have also tried revoking and recreating certificates and provisioning profiles several times within the Apple developer portal, but this does not resolve the code signing issues.

 

This issue has resulted in a significant delay in publishing my apps, so any suggestions about how to resolve or troubleshoot this issue would be much appreciated. I am using a Mac Mini (late 2014 version) running on Mojave 10.14.5 and Xcode 10.2.1 for building.

Attached Files



[TOPIC: post.html]
#2

Rob Miracle

[GLOBAL: userInfoPane.html]
Rob Miracle
  • Moderator

  • 25,925 posts
  • Enterprise

It will save you some work if you check the "Always Allow" button when it asks you for your superuser/admin/keychain access password. After you do that you can try to rebuild.

 

Rob



[TOPIC: post.html]
#3

crawfdc47

[GLOBAL: userInfoPane.html]
crawfdc47
  • Enthusiast

  • 38 posts
  • Corona SDK

Thanks Rob for the suggestion. I tried the "Always Allow" button. The only difference I noticed after doing this is that the login prompt appears only once after Corona finishes building the app, and does not reappear a second time after I enter the password like it was doing before. I am still getting the code signing error when I attempt to upload my built app to my iPhone though.

 

After doing some more research online, it appears that other people are having similar issues with invalid provisioning profiles when building their apps. The problem appears to occur when using Xcode 10, and some people have been able to resolve the issue by reverting back to Xcode 9. Unfortunately, a lot of the other ways people have been able to fix the issue (e.g. automatic code signing) require having a project for your app set up in Xcode, which is not feasible when using Corona SDK for development. Below is a link to the forum I found online with discussion about the error:

 

https://stackoverflow.com/questions/52424462/xcode-10-a-valid-provisioning-profile-for-this-executable-was-not-found



[TOPIC: post.html]
#4

crawfdc47

[GLOBAL: userInfoPane.html]
crawfdc47
  • Enthusiast

  • 38 posts
  • Corona SDK

I tried downgrading to Xcode 9.4.1 and rebuilding my app for development using both Corona 2018.3326 and 2018.3342, which was suggested in the online thread I posted a link to in my previous thread. Unfortunately, this did not resolve the code signing issue though and I am still unable to upload my built app to my iPhone.



[TOPIC: post.html]
#5

crawfdc47

[GLOBAL: userInfoPane.html]
crawfdc47
  • Enthusiast

  • 38 posts
  • Corona SDK

  Best Answer

So, I was finally able to figure out what was causing the code signing error: It turns out that I had not registered my iPhone under the devices section on the Apple Developer portal. After registering the device and adding building permissions for the device to the provisioning profile, I was able to successfully build the app and install it on my iPhone.

 

I overlooked this before because I already had an iPhone registered with my Apple Developer account that I assumed was my iPhone, but actually turned out to be an iPhone I had borrowed from a family member which I had registered with my account a few years ago (if there was a facepalming emoji available, I would insert it here). Apparently, the Apple Development Technical Support Team was not able to identify this as a possible source of my error when I requested technical support though.




[topic_controls]
[/topic_controls]

Also tagged with one or more of these keywords: code signing, provisioning profile, certificate, build