iOS Build Error

Solar2D Daily Builds and Public Releases
#41

Are you copying the profile to your ~/Library/MobileDevice/Provisioning Profiles/ folder and restarting Corona?

Does Corona present you with the distribution profile to use?

Keep in mind Apple has three types of profiles:

Developer

Distribution (AdHoc)

Distribution (Store)

In their interface, they only show two and when you go into the Distribution one, you can pick for the store or AdHoc, but if you don’t name your profile indicating that it’s AdHoc or Store, there is no way to know because it will just say distribution. I always make sure to explicitly name my profiles:

My Awesome Game (Developer)

My Awesome Game (AdHoc)

My Awesome Game (Store)

that way there is no ambiguity on which distribution profile is which.

Now some people will let Xcode manage the download and storage of the profiles. But when you do, you end up with filenames like:

f3e44b5f-c6d9-41e4-9f14-7d0cf6dee834.mobileprovision

Where as if you, from the developer portal choose “Download”, you get names like:

Alien\_Invasion\_AdHoc.mobileprovision Alien\_Invasion\_iOS\_Distribution.mobileprovision

But you have to be a little command line friendly or know how to use finder to get to ~/Library since Apple tries really hard to hide that folder from Finder. The command line is quite easy to do for this. Download your profiles using the Download folder. They **should** end up in your ~/Downloads folder unless you’ve told your browser to do something else. I’m assuming you’ve not changed this.

Open the Terminal (click on the Spotlight magnifying glass and type “terminal” and hit enter. In the window that opens, type:

cd ~/Library/MobileDevice/Provisioning\ Profiles mv ~/Downloads/\*.mobileprovision . ls -l

This will take you the right folder, move the files you downloaded from Downloads to the right place

and then the ls -l will give you a list of the files that are there.

Close the terminal, restart Corona and all your current profiles should be available to choose. If you named them appropriately you should be able to see them in the directory list and with the more human readable name you used in the developer profile.

Make sure you pick a “For the Store” profile and you should be good to go.

Rob

#42

Rob, thanks a lot for a long reply and help. 

I tried deleting everything in ~/Library/MobileDevice/Provisioning Profiles/ folder and downloading from Developer Console. I have never created Ad Hoc profile but Developer and Distribution profiles. Moreover, I name the profiles as you mentioned in order to prevent confusion. 

I keep downloaded profiles under the folder named “Mobile Provisions”. I tried to delete and install profiles again while writing this reply. Then I restarted Corona, chose the Distribution profile for the build and chose “Send to App Store” option. This time it gives me this:

Corona Simulator wants to access key “Application Loader” in your keychain. To allow this, enter the “login” keychain password.

When I write my password for Mac, it gives me the same “ad hoc” related error.

A few days ago after being unsuccessful to build and upload to App Store, I tried to use Application Loader but I noticed that it asks me to sign in. It was normal as I had to format my Mac after upgrading to Mac OS Beta version.

After logging in to Apple Developer portal it asked me to generate a one-time password for the Application Loader. I did so, downloaded and installed it. 

iOS SDK version is 12.4 

#43

Can you copy/pasted exact messages you’re getting. We would also like to see screen shots of all of these steps. I can’t see your developer portal where you’ve created  the profiles. You can copy/paste or screen shot your ~/Library/MobileDevice/Provisioning Profiles/ folder. Screen shots of where it’s asking for your password and the error you get from it.

You can add screen shots by clicking the “More Reply Options” button beside the “Post” button and it will let you attach images.

Rob

#44

Rob, the screen shots are attached to the post. I tried a few times but could not produce the password asking screen again. I deleted all the profiles from the ~/Library/MobileDevice/Provisioning Profiles/ folder and then added again by clicking on the downloaded profile files. I even created a new app and new provisioning profiles so that it might ask the password again. 

#45

By the way, I tried to use Application Loader to upload to the App Store but I can not select the iOS build from the folder. Is it possible that it is related to the problem?

#46

Can you open up the profile to see the details and provide a screenshot similar to:

Rob

#47

Rob, it is the screen shot for me. 

#48

Rob, I created a new Identifier, then created Profiles for Development and Distribution, then downloaded and installed them. Then I tried to build the app and to choose “Send to App Store”, I got the password asking screen again. I am attaching the screen. When I type the password I use to login to Apple Developer website, the login screen shakes which means the password is not correct. The same thing happens when I use the one-time password I generated for Application Loader. However, when I use my password for the Mac login, it shows me the “Only apps built with distribution profiles can be sent to the App Store” message. 

#49

Are you checking “Always Allow” when you enter the password?

#50

With the last one, I did not but the previous ones I used “Always Allow” option too. 

#51

Just out of curiosity have you launched and run Xcode since the last time it was updated?

#52

Rob, when I click on the downloaded provisioning files, it opens Xcode, so, I think, that should be considered “yes” for your question.

#53

I still haven’t managed to solve the problem. So I wanted to try uploading with the Application Loader. But it says there is no provisioning file inside it: 

ERROR ITMS-90174: "Missing Provisioning Profile - Apps must contain a provisioning profile in a file named embedded.mobileprovision."

Anyone has idea how can I make sure the provisioning file is inside the IPA file? By the way, I created the IPA file by creating a folder and putting Application file and dSYM file generated by Corona Build inside the folder, compressing it and changing the extension to .ipa

#54

I deleted Xcode and re-installed it, delete Corona and re-installed it, it’s still the same error when I try to select “Send to App Store”  :frowning:

#55

Open up your terminal and run this command:

defaults write com.coronalabs.Corona\_Simulator debugBuildProcess -int 5

This will cause Corona to emit build log in much greater detail. I don’t know if it will help or not, but it may give more information to help solve this.

Use a service like pastebin.com to copy the entire build log and paste it in there then post the link here.

Rob

#56

Rob, as soon as I click on the Build button, I get the same error when I try to build and upload to App Store. 

Now I am trying to build with checking “Show in Finder” option, and then will try to convert it to ipa file and upload using Application Uploader. I will provide the build process log when it’s finished. 

#57

I tried Application Uploader but it gave me error again. 

ERROR ITMS-90174: "Missing Provisioning Profile - Apps must contain a provisioning profile in a file named embedded.mobileprovision."

The logs are here: https://pastebin.com/0nLUWyLj

I also tried putting the provisioning file inside ipa file and changing the name to embedded.mobileprovision but it did not help either. 

#58

You should not have to do any hand signing. You should not be putting provisiioning profiles in your own .ipa files. You have something else going on that’s making your provisioning profiles not be recognized.

The log file you posted doesn’t seem to have any errors in it. There were a lot of warnings and this might help filter those out. Add this to the plist section of your build.settings:

settings = { iphone = { plist = { MinimumOSVersion = "9.0" } } }

And regenerate the build log when trying to send to the app store. I need to see it with the errors.

Given that everyone else can successfully do this, it has to be an issue with your certificate/profile setup causing it.

Something else you can do is try and build one of our sample apps and try to send it to the store. This will rule out things in your project that may be causing the problem. I would suggest maybe building HelloWorld. Also look to make sure you don’t have any provisioning profiles in the folder with your main.lua or any children folders.

Rob

#59

Rob, thanks for your help. I have been struggling with it for almost two weeks. It happened after I had to format my Mac. Before formatting it, I remember I had to open another account on my Mac and sign in with the credentials I sign in to Apple Connect account. Do you think it could be the reason? 

#60

When I select “Send to App Store”, it gives the below error message on Corona Simulator Console:

ERROR: Cannot Send To App Store: Only apps built with distribution profiles can be sent to the App Store. Choose a provisioning profile signed with an "iPhone Distribution" certificate and note that the provisioning profile used should not specify any devices (i.e. is not "ad hoc").