LiveCode Forums.

I am having an awful time getting an app to upload to Apple. I have watched and followed the video from Livecode, but unfortunately, Apple seems to have changed its system for the final Application Loader. It no longer has the status "ready for upload" - which used to be required before any uploads were possible.

I have verified WITH APPLE that all my provision profiles are correct, IDs match, and the signing is just fine. But Application Loader continues to give me:

error in Application Loader
Application Loader unable to Upload Package. Verify your bundle identifier 'xxxx' is correct

I even tried uploading a virtually blank app (hello world) - and it gives me the same error.

1) Does livecode work with xcode 9.1 or 9.2? If not...what xcode does it work with?

2) Here is the procedure I am following:
a) in developer.apple dot com I created a signing certificate - first creating a request, then putting the request into the keychain utility.
b) in developer.apple dot com I created an ID with a bundle identifier: com.mywebname.bob . I put that name in my livecode app. I made sure that everything was lower case.
c) in developer.apple dot com I created a provisional certificate - connecting my app with bundle identifier com.mywebname.bob with my signing certificate
d) I created a project in xcode 9.1 and used the same bundle identifier com.mywebname.bob
e) I downloaded the provisional certificate and then clicked on it to open in xcode 9.1
f) in itunesconnect.apple dot com I created an app and used the same bundle identifier: com.mywebname.bob I completed all the fields except the upload portion. It still has 1.0 prepare for submission as its status.
g) I created a successful standalone with the bundle identifier: com.mywebname.bob
h) I used AirLaunch to create the .ipa file
i)in xcode 9.1 I went to xcode, opened developer tools, application loader and clicked on my .ipa file.

It gave me the error:
Application Loader unable to Upload Package. Verify your bundle identifier 'xxxx' is correct

What am I missing/doing wrong?

Thank you

I have looked at the pfile - and am confused about the url. I want it to upload the file I've chosen in Application Loader - on my desktop... because that's where the files are located. Could this be the problem? If so, what do I change it to?

Hi,
Did you set checkbox "beta" to true ?
Best regards
Jean-Marc

No I didn't. why would I check "beta" to true? This is supposed to be a distribution not a development profile.

Thanks in advance for explaining

OK. The problem was in my pfile. The original one that failed had a hidden character in the ID (represented by a ?) I don't know what caused the hidden character, but when it was removed, everything matched and the file was uploaded. So if you have problems, look at your pfile. btw: The url part of the pfile doesn't matter. Hoorah!

Just a note that AirLaunch isn't intended to be used for uploads to the App Store, it's for ad hoc distribution from your own private server. It's been some years since I uploaded an app there but when I did, Apple expected a compressed app (done via the Finder "compress" contextual menu). I didn't upload an ipa. Has that changed?

Hi Jacqueline,

Just a note that AirLaunch isn't intended to be used for uploads to the App Store

Yes, but we can use AirLaunch to create .ipa file
Last upload i did with success was indeed an .ipa file as expected by Apple
I used ApplicationLoader to upload a beta version to testflight section of iTunesConnect.
@Cusinger I set beta checkbox to true because I upload for TestFlight first

Hi

Looking through this thread, it seems to be the same problem that I am having.

I see that you found a solution however I could not understand what the solution was. Are you about to explain what the solution was and where the pfile is?

In my process. I do a build. I use the terminal to compress it into an .ipa file
Within the build, I have a info.plist file. I cannot see a pfile.

Thanks for any help. Matt

I'm pretty sure he meant plist, I've never heard of a pfile.

I still do not know what he found to fix. 8-/

Apparently he just had to fix a typo, somehow an invisible character was inserted.