Hmmm interesting - When I added the binary to the app summary page, it never gave me the option to check the option about IDFA after… does it automatically pop up as a window, or where do I locate that?
Ahhh it worked! I never saw that pop-up window the first time I hit submit for some reason, but now I see it with the IDFA stuff, thanks guys!!
Hi, today i try to publish an app for iOS, i upload my app for distribution with application loader 2.9.1, i choose the build to publish and when i try to submit for review i see this message:
You must submit your builds using Xcode 5.1.1 or later, or Application Loader 2.9.1 or later. After you’ve submitted a build, select it in the Builds section below.
any suggestions???
I have used corona sdk and application loader to upload my build to itunes connect successfully. When I go to the ‘prerelease’ page at itunes connect, I see my build showing up.
I Click + to add a build before submit the app.
I clicked it and selected the build that I just uploaded. However, after I clicked on ‘Submit for Review’ the page said:
“You must submit your builds using Xcode 5.1.1 or later, or Application Loader 2.9.1 or later. After you’ve submitted a build, select it in the Builds section below.”
Any suggestions???
Hi, I am still getting “Missing or invalid signature” second day already. Is there any solution for this problem?
@hayk, it’s possible that you might have a normal “Missing or invalid signature” error. Are you’re certificates/keys good? Are you using the right provisioning profiles? Do you have a file called “Icon” possibly with hidden characters at the end? Any folders name res or resources? Are you saving your built app to your project folder?
Can you post the entire message?
Rob
Hi Rob, my error was not connected with those issues, it seems that there is a problem when you generate new distribution certificate.
Then you need to either use public build 2393a or the latest daily build.
Rob
Hello Dear’s,
Hello raye, erik.g.haugen, nipon.ph:
Can you please let me know what happens to your apps. Because i too have the same error “Buold xxxx does not contain the correct beta entitlement”. I submitted my app 1 week before and now i realize this error. Should my app will be approved or rejected due to this error. Please inform me i am worried about this.
Thanks.
Hi iamsameer,
the status of my app is still “Waiting for Review”.
René
Hi All! I got a Non-public API usage and I’m wondering if it might stay forever. There is a very new build that hasn’t this problem. BUT our 5 of 7 apps are not compatible with this new build and it is lots of effort to make them compatible. Might there be another solution than updating Corona SDK?
Non-public API usage :
- The app references non-public symbols in App: MPMoviePlayerContentPreloadDidFinishNotification
Unfortunately, no. These are Apple mandated changes. We cannot go back to old builds and patch them.
Rob
I just tried uploading a new version of an app we made but I’m getting the error message
" Missing or invalid signature - The bundle ‘XXXX’ at bundle path ‘XXXX’ is not signed using an Apple submission certificate."
I am using the distribution certificate for this app and I’ve made sure it is still valid and up to date.
Also I have to manually add the CFBundleShortVersionString to the info.plist after making the production build, when will this be done by Corona by default? And might this be the cause because some checksum/hash gets invalidated by doing this?
My Corona version is “Version 2014.2393 (2014.8.5)” which I think is the latest one.
That means that the app build has been accepted and it’s now up to Apple to start reviewing it. A build should get rejected automatically within 5 minutes or so if something’s wrong with it.
There is a 2393a build for SDK users that addresses this. A later daily build would be a good choice. However if you’re submitting an Enterprise built app, the changes in 2393a wouldn’t be impacted since you’re building directly with Xcode.
For SDK users, this error frequently indicates that their is either an invalid file name some where along the way (UTF-8 letters in the path, spaces, etc.) but I thought we had patched those or from invalid files or folders in the folder with your main.lua, such as a file named “Icon” that comes from pictures or colored folders, folders name res or resources. Also if you have the .app that corona builds put in the folder with your main.lua (or any child sections) it will give this error.
Is there any more of the error message you can share?
Thanks
Rob
I can’t really share any more of the error message as everything else that’s said in the E-Mail is just irrelevant to the issue (basic ‘hey we found an issue’ E-Mail from Apple). The app itself is a iPhone + iPad application btw.
I just replaced all files that had contained a space in their name with an underscore but after uploading a new binary the same error still occurs… How is it possible that the name of a file can invalidate a build and why isn’t there anything build in to Corona that fixes this? I’ve never had any issue like this when building apps through XCode itself but only with Corona.
Also how safe is it to use a daily build? We haven’t had the best of luck when updating to a new public version of Corona (we’re focussed on apps, not games fyi) and I don’t want to go through any time consuming issues related to a bad daily build.
Greets,
Allan
Are you using Corona SDK to build your app (not Enterprise)?
Are you editing your plist file in your app folder?
Rob
Just to let you know: my App status has been changed to “Ready for Sale” – hooray!
It has been in review from 11.09. to 19.09.
Regards
René
Here’s my little story so maybe someone who knows more than me (all of you) can help.
I uploaded the lite and full version within 1 hour of each other Monday Sept 8th, the full version got kicked back at me for the CFStringVersion, and Arm64 errors. I waited and tried to fix and waited to apple to solve their issues. My app successfully uploaded Friday, Sept 12th was released late Saturday night for sale, we have a had a good number of sales and I received an email that the app is not working. Which was not super helpful since everything checked out on my end, and works great here. So I am thinking that Apple changed something to how they take apps or something with iOS8 and that screwed it up. But then I think why would apple release an app that does not work at all? Maybe it was just the user? Any one have any ideas or helpful suggestions.
I did try to upload a new version this morning and got the CFStringVersionShort error again, but when I tried to add that into my code, It flipped the simulator vertical while keeping my app horizontal, so there is band of space on the bottom of the simulator.
Is there an actual fix to CFBundleShortVersionString errors I’m getting on the Uploader ? I’m using current daily build and have CFBundleShortVersionString in iphone/plist ?
I’m getting somewhat stuck with this.