Invalid Bundle Structure

Solar2D iOS
#1

Hi,

Trying to submit an app whose content is virtually identical to 4 previously accepted apps. Keeps bouncing as Invalid Binary due to Invalid Bundle Structure error. Zero problems submitting other apps:

Invalid Bundle Structure  - The binary file ‘Bundle ID Suffix.app/Bundle ID Suffix.app/Bundle ID Suffix’ is not permitted. Your app may contain only one executable file. Refer to the Bundle Programming Guide for information on the iOS app bundle structure.

There is one executable. Project folder has virtually same files as other 4 apps. build.settings file is identical except:

CFBundleDisplayName = “AppIconName” ,

Corona 1076, Xcode 4.6, App Loader 2.8

Any idea what could be wrong?

Thanks very much for any help,

Lynne

#2

My bad. Build was saved to project folder; resulting zip accepted for 4 previous apps. New restriction.

 

Saved build to empty “Staging” folder. Resulting zip accepted. Waiting for Review.

 

Thanks, Rob and Tom.

#3

I don’t now if this will help you or not, but I made a special folder for all my App Builds (called AppBuilds).  It’s a folder inside my Projects folder.  I also made a short cut to it on my Finder’s side bar (where the Home, Downloads, Desktop, Music, etc. links live).  I have Corona SDK dump all my builds to that folder and from there I have Xcode set to look there by default for when I’m putting them on device.

Works like a charm.

#4

Sounds like a good idea … organized, cleaner, time-saving. Thanks, Rob.

#5

I am experiencing the exact same problem, however trying what has worked for others doesn’t seem to be offering any solution, as I am still receiving the error from Apple’s side once deploying.

Can you possibly put down the exact steps you used to setup the suggested “Build” environment within Xcode. Have played with the settings for “Derived Data”, “Archives” and “Build Location” with Xcode’s preferences.

We have tried deploying from alternate Macs as well, and ensured we are using the latest software - Xcode Version 4.6.2 (4H1003)/Application loader 2.8

Any further suggestions or troubleshooting steps would be greatly appreciated.

#6

Rob may have Xcode info.

My process for creating the accepted app using Corona SDK (assuming all provisioning profiles have been created @developer.apple and Xcode’s Window/Organizer LIBRARY/Provisioning Profiles window refreshed to contain most current profiles):

Corona Simulator 1076, Xcode 4.6, App Loader 2.8

Create an AppBuild folder (outside the project folder for app about to be built).

Open the app in Corona Simulator.

Choose File/Build/iOS.

In the Build for iOS window, select Build for: Device, select your Code Signing Identity for AppStoreDistribution, and point Save to Folder to the AppBuild folder that you created before opening Corona.

When the app finishes building, select option to open Application Loader to upload immediately, or quit Corona and upload later.

Good luck!

#7

My bad. Build was saved to project folder; resulting zip accepted for 4 previous apps. New restriction.

 

Saved build to empty “Staging” folder. Resulting zip accepted. Waiting for Review.

 

Thanks, Rob and Tom.

#8

I don’t now if this will help you or not, but I made a special folder for all my App Builds (called AppBuilds).  It’s a folder inside my Projects folder.  I also made a short cut to it on my Finder’s side bar (where the Home, Downloads, Desktop, Music, etc. links live).  I have Corona SDK dump all my builds to that folder and from there I have Xcode set to look there by default for when I’m putting them on device.

Works like a charm.

#9

Sounds like a good idea … organized, cleaner, time-saving. Thanks, Rob.

#10

I am experiencing the exact same problem, however trying what has worked for others doesn’t seem to be offering any solution, as I am still receiving the error from Apple’s side once deploying.

Can you possibly put down the exact steps you used to setup the suggested “Build” environment within Xcode. Have played with the settings for “Derived Data”, “Archives” and “Build Location” with Xcode’s preferences.

We have tried deploying from alternate Macs as well, and ensured we are using the latest software - Xcode Version 4.6.2 (4H1003)/Application loader 2.8

Any further suggestions or troubleshooting steps would be greatly appreciated.

#11

Rob may have Xcode info.

My process for creating the accepted app using Corona SDK (assuming all provisioning profiles have been created @developer.apple and Xcode’s Window/Organizer LIBRARY/Provisioning Profiles window refreshed to contain most current profiles):

Corona Simulator 1076, Xcode 4.6, App Loader 2.8

Create an AppBuild folder (outside the project folder for app about to be built).

Open the app in Corona Simulator.

Choose File/Build/iOS.

In the Build for iOS window, select Build for: Device, select your Code Signing Identity for AppStoreDistribution, and point Save to Folder to the AppBuild folder that you created before opening Corona.

When the app finishes building, select option to open Application Loader to upload immediately, or quit Corona and upload later.

Good luck!

#12

I have the same problem…

Following the previous posts I have created a new folder (AppsBuilds) out of the project but the problem persists. Any idea / suggestion?

Thanks!

#13

 Can you post the exact error you are getting?

Thanks

Rob

#14

@jalemanyf, Apple and Corona update requirements since this post have wreaked a lot of havoc for me at least. On 7/30/14, I clicked to upload a perfectly working back-to-school app and got bounced due to a requirement to build with latest public release Version 2014.2393 (2014.8.5).

If you aren’t already running that version or later, you must. After updating, your code must run in at least “graphicsCompatibility = 1,” (enter this as first line of code in content table section of config.lua). Or, Corona’s best case preference, run in full Graphics 2.0 (no config specification required).

This has terminally broken my video module … so long, back to school sales.

If public release case is not relevant for you, I’ve read that some people have had trouble when they click upload to store button within SDK presented after distrib app build completes. It’s been suggested to try opening Application Loader outside of Corona and pull it through that way.

Good luck!

#15

Just to clarify…  Apple changed the format of their provisioning profiles a couple of days after we released our public build 2393.  Any newly downloaded profile would not work.  We pushed out a fix for Daily Builds and patched 2393 to a new 2393a (iOS only) that handles this correctly.  Daily build 2401 is the oldest daily build that will work with new iOS profiles now.

Rob

#16

I answer in order:

The exact error message is:

“ERROR ITMS-9000: “Invalid Bundle Structure - The binary file ‘EirEnfermeria.app/EirEnfermeria.app/EirEnfermeria.app/EirEnfermeria’” is not permited. Your app may contain only one executable file. Refer to the Bundle Programming Guide at https://developer.apple.com/library/ios/#documentation/CoreFoundation/Conceptual/CFBundles/BundlesTyoes/BundleTypes.html%23//apple_ref/doc/uid/100000123i-CH101-SW1 for information on the iOS app bundle structure.”

This message appairs twice: exactly the same.

Ibolduc:

Thanks for your answer. I’m using full Graphics 2.0 (So, no config is required).

Rob:

Thanks for the advice. I was generating with the public build 2401. After read your post, I have repeat it with the 2393a with the same result. We can discard this.

It seems I have done badly the name structure and it is repeated the ‘eir enfermeria’ directories inside the bundle. If you tell me how to do it well, I can repeat the profile or anything.

Thanks!

Josep Alemany

#17

Josep,

When you build your app, where is your “Save to Folder” pointing? It must point outside Eir Enfermeria project’s folder. For example, based on Rob’s tip, my builds now point to a desktop folder named AppBuild …

Save to folder: /Users/lbolduc/Desktop/AppBuild

If you’re not already doing that, I’d give it a go and see whether that changes anything.

#18

Ibolduc,

I have already done that (following the sample of Rob, I created an AppBuilds directory outside) but I have the same problem :frowning:

It must be another think.

Thanks!

#19

I think I have write wrong the Bundle ID Suffix  when the App is defined on the iTunes Connect. What do you wrote in the Bundle ID Suffix?

#20

I have a series of apps, so I use the option of defining each app like this …

     com.mycompanyname.currentappshortname

When creating a new app, I give iTunes … 

     Bundle ID Suffix: currentappshortname, (i.e.) app1

Then, specify or confirm pre-suffix name that matches app’s provisioning file

     com.mycompanyname.*

And, iTunes concatenates to create bundleID

     com.mycompanyname.app1

When you’re building your app with Corona, make sure that the selected Code Signing Identity matches your choice in setting up the app’s chosen provisioning profile. The profile associated with the pre-suffix segment of your Bundle ID.