You can modify the languages in the XML, but it seems that it makes no difference!

Really weird, I though it is just internal, but as you said it is displayed in itc and therefore it should be changeable from flash.

You can't change those in iTunesConnect!

These info (as John said) is just for changing the description info within iTunes and is therefore separated from the languages in the app.

It seems that there is an error/bug and (from what I can see what the ipa holds), because language infos are inside the folders if they are selected from within the XML, if not there are still the language sets, but without content.

Hi my app was released a week ago and has the same problem.

http://itunes.apple.com/us/app/house-ball/id443807593?mt=8

Just wondering if there is anything I can do to make English the only language, or is there no way around this bug?

Yeah just realized we have the same problem, has anyone come up with a work around/fix for this? Nothing can be added to the xml to specify language's???

Hi omdesign,

I tried doing that, but when I tried upoading the .zip after I modified, I recieved an error in Application Loader.

This is a shocker.  I was happy to get our app approved and didn't notice that we were offering every language until a colleague pointed it out.  As there isn't a work-around, then we're stuck with this situation until Adobe fixes it.  My problems are; 1. we are all effectively doing false advertising, and 2,  if Apple's attention gets focussed on this it's another reason for them to be restrictive around the dev stacks they'll accept apps from.  I really hope this gets urgent attention at Adobe.

Peter Robertson

I'm having the same problem with my app - and it's a DICTIONARY so I think it's pretty important that it be clear it's only available in English!

Any update on when this will be resolved? I feel like it really need an urgent fix.

Am I the only one who feels like Apple is constantly teetering on the edge of banning apps made with any program other than XCode and things like this might just send them over the edge? Or am I overthinking it?

Adobe, please hurry on this issue. I'd hate to annoy Apple. I've had one user request a refund and leave a bad review. I'd sure like to fix this as soon as possible.

Hi Saumitra,

I tried this and something similar, it does work to use this on an own device, but have you been able to upload it to iTunesConnect?

When I was trying it, I got a codesign error, though everything was ok with the developer infos. I compared them with the original files via the Terminal...

Application launcher always gives me errors with this solution. However, I have been heading in the same direction with a little different Terminal script. When I have time to figure out if the app really gets accepted, I will post it here...

Hi,

I just tried to upload an update v1.1 of my App "Dragon Party" ( http://itunes.apple.com/de/app/die-olchis-ein-drachenfest/id464300466? mt=8 ) to iTunes Connect.

I compiled the IPA as usual (distribution profile, app store mobile provisioning).

I wanted to kill the additional languages and used the step-by-step procedure described above, resulting in my last codesigning step:

/usr/bin/codesign -f -s "iPhone Distribution: Verlag Friedrich Oetinger GmbH" "--resource-rules=./Payload/App_Drachenfest_53_MULTI_AIR30.app/Resour ceRules.plist" "./Payload/App_Drachenfest_53_MULTI_AIR30.app"

It worked like a charm, terminal told me:

./Payload/App_Drachenfest_53_MULTI_AIR30.app: replacing existing signature

I looked into the app and truly, the CodeResources in the payload were updated.

Afterwards i compressed and renamed the app again and installed the IPA on my iPad without any problems.

Then I tried to upload the app using the newest Application Loader 2.4.1 (190).

This is the result:

I don't understand these errors - I used the same Distribution Zertificate and App Store mobile provisioning as usual when I upload my other apps to the App Store.

I now uploaded my v1.1 update to iTunes Connect without first patching the languages and it worked fine, no problems with the Application Loader.

So:

1. My app is fine, the Distribution Certificate and App Store mobileprovisioning profile are valid and match with the ID, the correct name from the keychain was used etc. etc.

2. Proof of this is: I could upload the unmodified app with Application Loader to iTunes Connect

3. But when I change the app content, delete the additional language directories and the resign the app WITH THE CORRECT PROFILES etc., I couldn't upload the app anymore

Any ideas?

Hi Saumitra,

THANK YOU VERY MUCH!

It worked!

I rejected my own update v1.1 and tried again (after deleting all the languages I didn't need, see posts above), using the new codesign string and with an Entitlements.plist file.

Worked beautifully.

And then ... I uploaded the new IPA using the Application Loader ... and the IPA was accepted, my update is now waiting for review.

THANKS AGAIN!

This bug is a bad one, but your workaround rocks!

One more interesting thing: After uploading the IPA I got a warning - have you encountered anything like this before (just curious...):

I didn't get this after uploading the original v1.0 version, and there's almost no difference to the just uploaded version v1.1

Best,

Andrew

I got this msg when I uploaded the app without resigning, too.

So yeah, maybe it's the new Application Loader, it has nothing to do with the resigning process.

Best,

Andrew

Hi,

any update in this issue? Can we expect covering this area in the near future by AIR itself?

Thanks.

Hi Appandrew (and Saumitra),

I went out to the Apple preview of your app and I see all of the languages listed still for version 1.2 of your app.  In the meta data description you have

ATTENTION 1:

This is the English version!

So did the workaround that Saumitra suggested really work?  We need to fix this for a couple of iOS apps we have out there and want to verify.  Hopefully Saumitra is right and I hope Adobe/Saumitra will have an easier fix/solution soon!

Thank you so much,

greg

This workaround fixed our issues. We've submitted updates to all our apps. Thanks everyone!

I place the modified .app file on my desktop. Then I create a text file on my desktop called appname.xcent. Place this in that file:

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">

<plist version="1.1">

<dict>

    <key>application-identifier</key>

    <string>1234567890.com.yourcompany.yourappname</string>

    <key>get-task-allow</key>

    <true/>

</dict>

</plist>

With my modified .app and the .xcent file on my desktop I run this line in terminal.

codesign -f -s "iPhone Distribution: Developer Name" "--resource-rules=/Users/yourname/Desktop/myappname.app/ResourceRules .plist" --entitlements "/Users/yourname/Desktop/myappname.xcent" "/Users/matthutton/Desktop/myappname.app"

After that, I zip the file and send it to Apple. So far it's worked for me. I've done this now to 5 apps successfully.