Can't install app on device using iTunes

Solar2D iOS
#1

Hi all,

I am having an issue installing an app on my iPad.   The app works perfectly in the Corona Simulator, xCode Simulator and I can install it via the xCode Organiser (also works perfectly on my android phone).  When I try install it via iTunes the install starts but gets stuck on “installing”,  the app appears on the device but is greyed out - if I click on it (on the iPad) it changes to “installing” on the device.

The same error appears to occur on an iPhone I tested.  I also tried rebuilding my provisioning profile and this did not help.

I am using build 2147, xCode 5.0.2 and my iPad is running 7.0.4.

I have looked through the console log in xCode Organizer and there are a lot of “warnings” (are these normal?) but the first errors read as follows.  

Jan 19 14:47:32 Craig-iPad installd[60] <Error>: 0x40d000 init_pack_state: Can’t stat /var/mobile/Media/PublicStaging/SliderGame.ipa: No such file or directory

Jan 19 14:47:32 Craig-iPad installd[60] <Error>: 0x40d000 MobileInstallationInstall_Server: Could not initialize package state

Jan 19 14:47:32 Craig-iPad installd[60] <Error>: 0x40d000 handle_install_for_ls: API failed

Jan 19 14:47:32 Craig-iPad atc[2117] <Error>: 0x281000 MobileInstallationInstallForLaunchServices: failed with -1

Jan 19 14:47:32 Craig-iPad atc[2117] <Warning>: ERROR: MobileInstallationInstallForLaunchServices returned nil

Thanks for your help,

Craig

#2

Why do you want to install it via iTunes?

If you want to distribute the app to others, Testflight is the ultimate solution.

#3

Thanks,   just tried Testflight,  seems like it would be great - but unfortunately my app still fails to install…

Any other ideas???

#4

Hi all,

Through trial and error I have found a cause for my error.  It seems that there is a folder limit (?). I went through removing assets until my app installed correctly (thinking it was a coding error),  however I have discovered that it works with X amounts of directories, but if I add in one more directory (to anywhere within the project) the error pops up again.  My current reduced structure which works is as follows (I have only shown the directories as it doesn’t seem to matter if I add in an extra lua file);  (there are currently 32 assets in total including files and subfolders)…

(main folder)

main.lua … etc

|-------ChoosePlayGame

          |---------ImagesPlayGame

|-------Classes

|-------Images

If I add in a ‘temp’ directory anywhere then the same error occurs (apps will not install via iTunes, not a problem anywhere else). I am assuming that if I get this problem when installing via iTunes (or TestFlight) then my app is not likely to be accepted by Apple when I am done.

Am I missing something?  Has anyone else encountered this issue?  Ideas please…

Thanks,

Craig

#5

There isn’t a folder limit that I know of.

It sounds like that “temp” is a reserved filename/directory and using that in your app is overwriting some system directory/file.

Change the folder name to something else and it should work fine.

#6

Hi Thanks. Temp was just an example, the sane problem occurs no matter what folder name I use. . Thanks

#7

Can you list the folder names?

I have gone about 4 levels deep before in other projects with no issues.

#8

resources is a known problem folder.

Rob

#9

mmm…  

I seem to have tracked down the problem…

I have been publishing my apps into a google drive folder so that it will sync with my designer so he can test it on his device - this has not caused any errors in any of my previous apps (only 2 so far) but appears to be the cause behind this issue.  If I publish it into a regular folder (in this case on the desktop) then there appears to be no issue at all - app installs correctly, and works with TestFlight.

Not sure how or why google drive was causing the issue, but I happy to have found a solution.

Thanks for help and advice (I love Testflight!)

Craig

#10

Why do you want to install it via iTunes?

If you want to distribute the app to others, Testflight is the ultimate solution.

#11

Thanks,   just tried Testflight,  seems like it would be great - but unfortunately my app still fails to install…

Any other ideas???

#12

Hi all,

Through trial and error I have found a cause for my error.  It seems that there is a folder limit (?). I went through removing assets until my app installed correctly (thinking it was a coding error),  however I have discovered that it works with X amounts of directories, but if I add in one more directory (to anywhere within the project) the error pops up again.  My current reduced structure which works is as follows (I have only shown the directories as it doesn’t seem to matter if I add in an extra lua file);  (there are currently 32 assets in total including files and subfolders)…

(main folder)

main.lua … etc

|-------ChoosePlayGame

          |---------ImagesPlayGame

|-------Classes

|-------Images

If I add in a ‘temp’ directory anywhere then the same error occurs (apps will not install via iTunes, not a problem anywhere else). I am assuming that if I get this problem when installing via iTunes (or TestFlight) then my app is not likely to be accepted by Apple when I am done.

Am I missing something?  Has anyone else encountered this issue?  Ideas please…

Thanks,

Craig

#13

There isn’t a folder limit that I know of.

It sounds like that “temp” is a reserved filename/directory and using that in your app is overwriting some system directory/file.

Change the folder name to something else and it should work fine.

#14

Hi Thanks. Temp was just an example, the sane problem occurs no matter what folder name I use. . Thanks

#15

Can you list the folder names?

I have gone about 4 levels deep before in other projects with no issues.

#16

resources is a known problem folder.

Rob

#17

mmm…  

I seem to have tracked down the problem…

I have been publishing my apps into a google drive folder so that it will sync with my designer so he can test it on his device - this has not caused any errors in any of my previous apps (only 2 so far) but appears to be the cause behind this issue.  If I publish it into a regular folder (in this case on the desktop) then there appears to be no issue at all - app installs correctly, and works with TestFlight.

Not sure how or why google drive was causing the issue, but I happy to have found a solution.

Thanks for help and advice (I love Testflight!)

Craig