Please help me, I can't build for my iPhone using the latest Corona builds

Getting Started Newbie Questions
#1

I’ve been working on my app for several months now and have it almost ready to release. I’ve been building it using 2012.840 on Mac for the last little while and for the most part I’ve been very happy with it, but there is one nagging Corona issue that I was hoping might be fixed by building with the latest daily or stable build.

The issue is that storyboard transitions are periodically misbehaving. Not all the time, but seemingly at random, the current scene doesn’t transition out as the new one transitions in. It is very unpredictable and hard to recreate in a simple example, so before I posted about it I wanted to make sure it hadn’t been fixed in a more recent Corona build.

I first tried downloading the latest daily build (2013.997), but when I built my game for iOS using the same provisioning profile that creates a perfectly functional, installable app under 2012.840, and tried to transfer it to my iPhone using XCode, XCode declared “The application doesn’t have a valid signature”. I also tried to upload it to testflight, which I’m using to distribute to my testers and got a similar error “Invalid IPA: The get-task-allow values in the embedded.mobileprovision and your binary don’t match. Are you sure you created the IPA with the same type of certificate as the one you used to compile it?”

Incidentally, what is the difference between the version of Corona here:
https://developer.coronalabs.com/downloads/corona-sdk
and the equivalent version here:
http://developer.coronalabs.com/downloads/daily-builds
They are different sized downloads, so I know they can’t be the same. How do I as a registered Pro developer find the latest stable build?

I noticed that in the more recent builds of Corona, the build dialog offers an iOS SDK version to build against. As I understand it, iOS is backwards compatible as much as possible, so I didn’t think this would be the problem.

I have iOS 5.1.1 on my phone, but since I’m not using any features of Corona or the iOS more recent than that, I see no reason it shouldn’t still work. Many of my testers are using iOS 5.1.x and some are even still on 4.x!

Thanks in advance for any assistance.

cheers
[import]uid: 131885 topic_id: 34589 reply_id: 334589[/import]

#2

First, build 971 is the latest stable build (well I think 972 had an update that was supposed to be rolled in to 971).

There have been quite a few storyboard fixes between 840 and 971, and even more fixes since then. However there was a note in today’s daily build:

Storyboard: Rolled back to stable storyboard version (from 926) and repatched/fixed any issues since that build.

I would pick up today’s 999 build and give it a try and see if you see improvements. [import]uid: 199310 topic_id: 34589 reply_id: 137566[/import]

#3

Hello,
I am also unable to install on iOS (and I am using build 999).

My situation is different, however. I’m trying to install Ad Hoc onto my iPad. My iPad has version 6.0.1 of iOS. My MacBookPro is running OS X 10.8.2. I just uninstalled an older version of Xcode (3.2.3), rebooted, installed Xcode 4.5.2, and ran it. Then, I ran the Corona Simulator (build 999) .

When I attempted to Build, I was given a choice of two Code Signing Identities, one for iPhone Developer and one for iPhone Distribution (I created both at the provisioning portal). I am currently just trying to get Corona’s Hello World sample code to install ad hoc on my iPad. I’ve been able to build with both code signing identities and both run in the Xcode simulator (version 6.0).

Then, to install the app on my iPad, I drag and drop it into iTunes (version 11.0.1), click the Install button for the Hello World app and then click the Apply button. After all that, I keep getting “Hello World failed to install.”

There is only one thing that I am doing that is clearly inconsistent with instructions (found here: http://developer.coronalabs.com/content/building-devices-iphoneipad). In the instructions, it says to place the provisioning profile in the following location:
/Users/myname/Library/MobileDevice/Provisioning Profiles/

But, there is no Library folder under my name under the Users folder. And when I go to the hard drive’s Library folder, there is no MobileDevice folder. Regardless, I do see the provision profiles when I try to Build using Corona and the instructions imply that the location of the Provisioning Profiles is ok.

I’m pretty frustrated. I’ve spent all day uninstalling software, installing software, restarting the MacBook Pro, trying different configuration. If you have any suggestions, I would really appreciate it.
Thanks,
Michael [import]uid: 104085 topic_id: 34589 reply_id: 137580[/import]

#4

One other thing. I am using an App ID with a wildcard. The Corona build instructions actually recommend that, but is it possible that is causing my problem? [import]uid: 104085 topic_id: 34589 reply_id: 137581[/import]

#5

I also found this at the Apple Provisioning Portal:
Recipients of the application will need to drag the application file and Ad Hoc Distribution Provisioning Profile into iTunes, then sync their iPhone, iPad or iPod touch to iTunes to install

Do I need to manually drag the Ad Hoc DIstribution Provisioning Profile into iTunes or does Corona do that automatically? [import]uid: 104085 topic_id: 34589 reply_id: 137583[/import]

#6

Eureka! Got Hello World to install. Why do I feel like I just reached the summit of Everest?

Not sure which of the following two things did it, but I believe it was one or both of these:

  • When I created my App IDs, I thought I created a wildcard app and I called it “All.” For some strange reason, the Provisioning Portal created a separate Wildcard app. So, I just created a new provisioning profile and made sure that I was using the actual Wildcard App ID. (Then I did all the stuff needed to install the provisioning profile using Xcode. I did have to restart Xcode and Corona in order for the new provisioning profile to show up in the Build window)

  • After I built the app with the new prov. profile, I then dragged it AND the new provisioning profile to iTunes (that was weird because it didn’t seem like you could or should be able to do that. However, if you do it a second time, you get a prompt asking whether you would like to replace it, so it must work). This time, when I tried installing, it succeeded. Yay! [import]uid: 104085 topic_id: 34589 reply_id: 137584[/import]

#7

I love these little conversations I have with myself in public forums :slight_smile: [import]uid: 104085 topic_id: 34589 reply_id: 137585[/import]

#8

Uh oh, just checked again. It may have been neither of the things I mentioned above. They may or may not have been important, but this was definitely required:

I misread the instructions here:
http://developer.coronalabs.com/content/building-devices-iphoneipad

I thought they were saying that you had to Build for Xcode Simulator. But they actually say, you must CHOOSE whether you want to build for the Xcode Simulator or your Device. So, I had been building for the Xcode simulator all along. In my posts above, I got things to work because I accidentally left “Device” selected. When I tried again and consciously chose Xcode Simulator, I had a big fail.

So, to summarize, if you want to Build to run on your iOS device, then choose Device (and not Xcode Simulator) for goodness sakes! Ok, I’m done. Time for a drink! [import]uid: 104085 topic_id: 34589 reply_id: 137588[/import]

#9

Glad you got it solved.
[import]uid: 199310 topic_id: 34589 reply_id: 137621[/import]

#10

Thanks for the storyboard advice, @Rob, I’ll give that a go.

In order to get the build to load on my iPhone I had to regenerate the provisioning profile, re-install it through XCode, re-build the app and it worked.

Cheers. I’ll post about the storyboard bug - which still persists in build 999 of Corona - in a more appropriate forum. [import]uid: 131885 topic_id: 34589 reply_id: 137636[/import]

#11

First, build 971 is the latest stable build (well I think 972 had an update that was supposed to be rolled in to 971).

There have been quite a few storyboard fixes between 840 and 971, and even more fixes since then. However there was a note in today’s daily build:

Storyboard: Rolled back to stable storyboard version (from 926) and repatched/fixed any issues since that build.

I would pick up today’s 999 build and give it a try and see if you see improvements. [import]uid: 199310 topic_id: 34589 reply_id: 137566[/import]

#12

Hello,
I am also unable to install on iOS (and I am using build 999).

My situation is different, however. I’m trying to install Ad Hoc onto my iPad. My iPad has version 6.0.1 of iOS. My MacBookPro is running OS X 10.8.2. I just uninstalled an older version of Xcode (3.2.3), rebooted, installed Xcode 4.5.2, and ran it. Then, I ran the Corona Simulator (build 999) .

When I attempted to Build, I was given a choice of two Code Signing Identities, one for iPhone Developer and one for iPhone Distribution (I created both at the provisioning portal). I am currently just trying to get Corona’s Hello World sample code to install ad hoc on my iPad. I’ve been able to build with both code signing identities and both run in the Xcode simulator (version 6.0).

Then, to install the app on my iPad, I drag and drop it into iTunes (version 11.0.1), click the Install button for the Hello World app and then click the Apply button. After all that, I keep getting “Hello World failed to install.”

There is only one thing that I am doing that is clearly inconsistent with instructions (found here: http://developer.coronalabs.com/content/building-devices-iphoneipad). In the instructions, it says to place the provisioning profile in the following location:
/Users/myname/Library/MobileDevice/Provisioning Profiles/

But, there is no Library folder under my name under the Users folder. And when I go to the hard drive’s Library folder, there is no MobileDevice folder. Regardless, I do see the provision profiles when I try to Build using Corona and the instructions imply that the location of the Provisioning Profiles is ok.

I’m pretty frustrated. I’ve spent all day uninstalling software, installing software, restarting the MacBook Pro, trying different configuration. If you have any suggestions, I would really appreciate it.
Thanks,
Michael [import]uid: 104085 topic_id: 34589 reply_id: 137580[/import]

#13

One other thing. I am using an App ID with a wildcard. The Corona build instructions actually recommend that, but is it possible that is causing my problem? [import]uid: 104085 topic_id: 34589 reply_id: 137581[/import]

#14

I also found this at the Apple Provisioning Portal:
Recipients of the application will need to drag the application file and Ad Hoc Distribution Provisioning Profile into iTunes, then sync their iPhone, iPad or iPod touch to iTunes to install

Do I need to manually drag the Ad Hoc DIstribution Provisioning Profile into iTunes or does Corona do that automatically? [import]uid: 104085 topic_id: 34589 reply_id: 137583[/import]

#15

Eureka! Got Hello World to install. Why do I feel like I just reached the summit of Everest?

Not sure which of the following two things did it, but I believe it was one or both of these:

  • When I created my App IDs, I thought I created a wildcard app and I called it “All.” For some strange reason, the Provisioning Portal created a separate Wildcard app. So, I just created a new provisioning profile and made sure that I was using the actual Wildcard App ID. (Then I did all the stuff needed to install the provisioning profile using Xcode. I did have to restart Xcode and Corona in order for the new provisioning profile to show up in the Build window)

  • After I built the app with the new prov. profile, I then dragged it AND the new provisioning profile to iTunes (that was weird because it didn’t seem like you could or should be able to do that. However, if you do it a second time, you get a prompt asking whether you would like to replace it, so it must work). This time, when I tried installing, it succeeded. Yay! [import]uid: 104085 topic_id: 34589 reply_id: 137584[/import]

#16

I love these little conversations I have with myself in public forums :slight_smile: [import]uid: 104085 topic_id: 34589 reply_id: 137585[/import]

#17

Uh oh, just checked again. It may have been neither of the things I mentioned above. They may or may not have been important, but this was definitely required:

I misread the instructions here:
http://developer.coronalabs.com/content/building-devices-iphoneipad

I thought they were saying that you had to Build for Xcode Simulator. But they actually say, you must CHOOSE whether you want to build for the Xcode Simulator or your Device. So, I had been building for the Xcode simulator all along. In my posts above, I got things to work because I accidentally left “Device” selected. When I tried again and consciously chose Xcode Simulator, I had a big fail.

So, to summarize, if you want to Build to run on your iOS device, then choose Device (and not Xcode Simulator) for goodness sakes! Ok, I’m done. Time for a drink! [import]uid: 104085 topic_id: 34589 reply_id: 137588[/import]

#18

Glad you got it solved.
[import]uid: 199310 topic_id: 34589 reply_id: 137621[/import]

#19

Thanks for the storyboard advice, @Rob, I’ll give that a go.

In order to get the build to load on my iPhone I had to regenerate the provisioning profile, re-install it through XCode, re-build the app and it worked.

Cheers. I’ll post about the storyboard bug - which still persists in build 999 of Corona - in a more appropriate forum. [import]uid: 131885 topic_id: 34589 reply_id: 137636[/import]