- This topic has 8 replies, 3 voices, and was last updated 13 years, 5 months ago by
leifinseattle.
-
AuthorPosts
-
leifinseattleMemberGood news and bad news…the good news is that iTunes approved our app an it is now available in the store…Yay!
The bad news is that I’m unable to update it… In the mobione Build settings, I’ve changed the version number to 1.1 (also tried 1.0.1), ran the build (successfully) in mobione.
Then I added the new version in iTunes Connect but when I try to upload it using the app loader I get the following error
“ This bundle is invalid: CDFbundleShortVersionString in the info.plist file must contain higher version than that of the previously uploaded versions. “I’m confused because…well, it does :-\
I thought maybe I needed to append the bundle ID with the version number, but when I did that I got this error:
“Bundle Identifier: com.talriainic.sflrefguide1.01. differs from prior bundle identifier com.talriainic.sflrefguide”
Oddly, however, I get this error ONLY, I don’t get the previous error as well…Does the actual name of the .ipa make any difference?
Do I ever change the Bundle ID when doing an update?
What am I doing wrong? I appreciate any help, thanks…
-LeifFebruary 7, 2012 at 6:42 pm #323077
leifinseattleMemberFollowing the error from the app uploader, I tried to manually change the info.plist file… didn’t work…got the same error…
In any case, should I really need to do that? Shouldn’t mobione update the version number in the info.plist file automatically when you change the version number the build dialog? or am I missing something? do i need to set the version number somewhere else to automatically update correctly in the info.plist file (and hence in the ipa file)
Thanks!February 8, 2012 at 10:39 am #323101
support-michaelKeymasterThe dev team is investigating now. Will provide info as soon as we know more.
February 8, 2012 at 11:19 am #323104
support-lonnieMemberWe believe that we have found the cause of the problem you are experiencing and have deployed and update to resolve the issue. Please try rebuilding and resubmitting your application and let us know how it goes.
Thanks,
Lonnie
Genuitec Mobile TeamFebruary 8, 2012 at 11:45 am #323106
leifinseattleMemberHi Lonnie,
I had the inspired (and simple) idea yesterday to just DELETE the entire ios build folder so that the build would start from scratch and create a new (presumably correct) plist file conaining the new version number.
Not sure if it was what you did, I did, or both…but in any case…the build was successful and the upload to itunes worked fine…
thank you much!
-LeifFebruary 8, 2012 at 11:58 am #323107
support-lonnieMemberGreat! I’m glad it’s working. Thank you very much for your patience.
Lonnie
Genuitec Mobile TeamFebruary 8, 2012 at 1:34 pm #323113
leifinseattleMemberHi Lonnie,
One issue remains…I am unable to download the new build on my phone to test (I’m still awaiting iTunes approval of the updated version)
When I click the link in the notification email…it starts to download, but then an error message pops up saying “unable to download application “SmilesForLife–ref-guide” could not be installed at this time.”…Any idea why?
Application: SmilesForLife-Ref-Guide
Installation URL: http://goo.gl/lFSMr
Sender: mailto:loleary@talariainc.comthanks
-LeifFebruary 8, 2012 at 4:34 pm #323120
support-michaelKeymasterSince this thread is about an appstore-based build I assume the app you are attempting to install is built with an appstore provision profile. Is this correct? If the app is built with an appstore provision profile then it will not install on your device unless it is downloaded from the appstore.
February 8, 2012 at 5:14 pm #323122
leifinseattleMemberI did not realize that…I thought that since my phone was the designated “test device” (which at some point in the process I recall doing) that I could use it to test even after listing my app on iTunes.
Thanks for clarifying
-Leif -
AuthorPosts