[Solved] Can't Install App on iPhone?

Solar2D iOS
#1

For some reason, I am no longer able to install my app on my iPhone. Just a few days ago, everything worked perfectly. Now, however, it doesn’t.

I uploaded the build to TestFlight, and there I verified that my iPhone was included Ad Hoc build.

When I tried to install, it failed. Here is the log file that I pulled from the device: http://pastebin.com/raw.php?i=GSkNKjQk

Any ideas as to what I did wrong?

Thank you for your time.

Edit:

A friend tried and received this slightly different log: http://pastebin.com/raw.php?i=zcnsU9ar

I also noticed that I can’t build for Xcode. Perhaps the issue is my build.settings? build.settings

#2

What happens if you use Xcode’s Organizer and transfer your app to your iPhone?

#3

Are you sure you have deleted the previous version of the app before installing the new one?

Indeed, if you are installing on your own device, going through TestFlight just introduces an unnecessary overhead. TestFlight has its own bugs that emerge from time to time.

Just drag and drop the build onto your device in Xcode Organiser (obviously you need to connect it to the computer with a USB cable first).

#4

I’m on a PC and have been using MacInCloud, hence the need for TestFlight.

My friend’s log (in the Edit section above), though, was obtained by installing through Xcode. I’m starting to think it’s some sort of build/provisioning profile error. I can’t even build for Xcode without getting a “null” alert from the simulator.I’m really unsure at this point. :confused:

And yes, neither of the devices had the app on it before installing. It was a fresh install.

#5

I see.

Your friend’s log contains the following, which seems to be the reason for the failure:

<Error>: 0x2c3000 peruse_package: App info dict loaded from “/var/tmp/install_staging.JLY6vc/91118343107893336.app” did not have bundle identifier

Which looks quite puzzling. Did you use an explicit app ID when creating the provisioning profile?

#6

I built with this provisioning profile, which from what I can tell has an app ID.

Oyqf1AP.png

#7

I got it to work! It was something with my build.settings. Notice the subtle difference between what didn’t work and what did: http://www.diffnow.com/?report=2gdhe

Funny how just missing two brackets caused all this trouble.

#8

Sorry, but I don’t understand how this could matter, bearing in mind all the mess in the logs…

I think it’s just Santa helping you! Merry Christmas!!  :smiley:

#9

CFBundleURLTypes requires an array of dictionaries.

Your first file (without extra brackets) created only an array which made Xcode’s build process confused and most likely caused the bundle identifier (among other things) to be located in a place where it couldn’t be found.

The extra brackets created the proper array of dictionaries and all was well  :).

#10

I don’t think that there is any need to delete the previous version. It should have updated automatically.

#11

What happens if you use Xcode’s Organizer and transfer your app to your iPhone?

#12

Are you sure you have deleted the previous version of the app before installing the new one?

Indeed, if you are installing on your own device, going through TestFlight just introduces an unnecessary overhead. TestFlight has its own bugs that emerge from time to time.

Just drag and drop the build onto your device in Xcode Organiser (obviously you need to connect it to the computer with a USB cable first).

#13

I’m on a PC and have been using MacInCloud, hence the need for TestFlight.

My friend’s log (in the Edit section above), though, was obtained by installing through Xcode. I’m starting to think it’s some sort of build/provisioning profile error. I can’t even build for Xcode without getting a “null” alert from the simulator.I’m really unsure at this point. :confused:

And yes, neither of the devices had the app on it before installing. It was a fresh install.

#14

I see.

Your friend’s log contains the following, which seems to be the reason for the failure:

<Error>: 0x2c3000 peruse_package: App info dict loaded from “/var/tmp/install_staging.JLY6vc/91118343107893336.app” did not have bundle identifier

Which looks quite puzzling. Did you use an explicit app ID when creating the provisioning profile?

#15

I built with this provisioning profile, which from what I can tell has an app ID.

Oyqf1AP.png

#16

I got it to work! It was something with my build.settings. Notice the subtle difference between what didn’t work and what did: http://www.diffnow.com/?report=2gdhe

Funny how just missing two brackets caused all this trouble.

#17

Sorry, but I don’t understand how this could matter, bearing in mind all the mess in the logs…

I think it’s just Santa helping you! Merry Christmas!!  :smiley:

#18

CFBundleURLTypes requires an array of dictionaries.

Your first file (without extra brackets) created only an array which made Xcode’s build process confused and most likely caused the bundle identifier (among other things) to be located in a place where it couldn’t be found.

The extra brackets created the proper array of dictionaries and all was well  :).

#19

I don’t think that there is any need to delete the previous version. It should have updated automatically.