none
store submission showing language varients not found in the app manifest

    Question

  • after updating some visual studio nugget packages I noticed that the multilingual app toolkit was no longer the default editor for xlf files. I reaplied the toolkit and when I made my next submission to the store some languages were listed twice. For example where I had only German before, I now have both "German" and "German (Germany)".  I see duplicates like this for de, fr and es but not for en (default) and nl.  Any thoughts?

    My languages are called out in the app manifest as follows (and matches my resource file and xlf files):

      <Resources>
        <Resource Language="en" />
        <Resource Language="nl" />
        <Resource Language="de" />
        <Resource Language="es" />
        <Resource Language="fr" />
      </Resources>

    Monday, March 17, 2014 11:33 AM

Answers

  • You are not supposed to ship neutral cultures such as "de" or "es". Always use a concrete language instead, such as "de-DE" or "es-ES". Otherwise you will end up with multiple entries in the store, as soon as one of your references does ship with a concrete language version (which most modules do, becuase it is the recommended and correct way).

    Details on this are available in my answer in this topic:

    https://social.msdn.microsoft.com/Forums/en-US/19a81da7-eedd-4a5f-80b8-af0319c0496c/visual-studio-adds-an-additional-language-when-generating-appx-with-bundles?forum=windowsstore

    • Proposed as answer by Lukas F Wednesday, March 23, 2016 9:32 AM
    • Marked as answer by Ed Alexander Wednesday, March 23, 2016 1:10 PM
    Monday, January 4, 2016 5:07 PM

All replies

  • I see a similar effect but do no know its cause yet. I have the resource ru in the app. In the Store I see ru and ru-RU. This is not the app default, which is en and appears once correctly. I filled in the details twice for the time being. I don't use xlf files. I have upgraded Nuget packages but no reason to connect the two.
    Monday, March 17, 2014 1:27 PM
  • Thanks for the reply... en is good for me also (singular).

    Also, thanks for the info that you are not using xlf files.  Sounds like the problem is on the store side or related to the update of visual studio nugget packages.  At least I can stop chasing a fix in Multilingual pack. 

    I wonder If Microsoft is trying to tell us to use de-de instead of de when we only want to support a single variant for a language?

    Regards,

    Ed

    Monday, March 17, 2014 1:34 PM
  • There are three known ways this can happen:

    • You have both a Windows 8 package and a Windows 8.1 package: One of them references en, the other references en-US.
    • You have an appxbundle, and the resource packs call out both kinds of support in the manifest.
    • You don't have an appxbundle, but the manifest still calls out both locales separately as supported.

    The dev center provides listings for the union of languages declared in your uploaded packages, so you can duplicate the listing or figure out where the one you don't want is coming from in your packages and remove it from the manifest.

    Monday, March 17, 2014 5:02 PM
  • I am indeed creating an app bundle but the manifest lists only as above (base en, es, de, nl, and fr).

    I have unzipped the bundle and was not able to find a reference to de-De or other errant entries.  I also compiled (rebuilt) using MSBuild from the command line and found no pertinent warnings or errors.

    Any hints as to where to check next?

    Monday, March 17, 2014 5:12 PM
  • I´d also would like to know that. Same problem here :-(

    lh

    Tuesday, March 18, 2014 4:44 PM
  • Have you had any luck figuring this out?  I just tried to make another update and now see an additional three languages listed...
    Saturday, March 22, 2014 7:24 PM
  • After opening a support case with the Microsoft store folks (Taylor) I have been told that the arm package contains references to other languages... I can't see how this could happen and am unable to locate these references so far...

    Does anyone have any clues? 

    When I upload an app bundle to the store only the desired languages are listed  on the packages screen.  Descriptions however is a much larger list including many variants not found in my manifest resources.

    I have been trying to create a new release for weeks now and completely stumped.

    Monday, April 7, 2014 5:36 PM
  • I have found the extra language variants are listed in the following package file:
    myapp_x86_arm_bundle.appxupload
    \myapp_x86_arm_bundle.appxbundle
    \AppxMetadata
    \AppxBundleManifest.xml

    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <Bundle xmlns="http://schemas.microsoft.com/appx/2013/bundle" SchemaVersion="2.0">
    	<Identity Name="[myapp]" Publisher="[.....]" Version="2014.407.2200.2039"/>
    	<Packages>
    		<Package Type="application" Version="1.2.0.29" Architecture="arm" FileName="[...]_1.2.0.29_ARM.appx" Offset="57" Size="21027124">
    			<Resources>
    				<Resource Language="EN"/>
    				<Resource Scale="100"/>
    			</Resources>
    		</Package>
    		<Package Type="resource" Version="1.2.0.29" ResourceId="split.language-de" FileName="[...]_1.2.0.29_language-de.appx" Offset="21027270" Size="23836">
    			<Resources>
    				<Resource Language="de-de"/>
    				<Resource Language="de"/>
    			</Resources>
    		</Package>
    		<Package Type="resource" Version="1.2.0.29" ResourceId="split.language-es" FileName="[...]_1.2.0.29_language-es.appx" Offset="21051195" Size="24366">
    			<Resources>
    				<Resource Language="es-us"/>
    				<Resource Language="es-es"/>
    				<Resource Language="es"/>
    			</Resources>
    		</Package>
    		<Package Type="resource" Version="1.2.0.29" ResourceId="split.language-fr" FileName="[...]_1.2.0.29_language-fr.appx" Offset="21075650" Size="24329">
    			<Resources>
    				<Resource Language="fr-fr"/>
    				<Resource Language="fr-ca"/>
    				<Resource Language="fr"/>
    			</Resources>
    		</Package>
    		<Package Type="resource" Version="1.2.0.29" ResourceId="split.language-nl" FileName="[...]_1.2.0.29_language-nl.appx" Offset="21100068" Size="18834">
    			<Resources>
    				<Resource Language="nl-nl"/>
    				<Resource Language="nl-be"/>
    				<Resource Language="nl"/>
    			</Resources>
    		</Package>
    		<Package Type="resource" Version="1.2.0.29" ResourceId="split.scale-140" FileName="[...]_1.2.0.29_scale-140.appx" Offset="21118989" Size="152135">
    			<Resources>
    				<Resource Scale="140"/>
    			</Resources>
    		</Package>
    		<Package Type="resource" Version="1.2.0.29" ResourceId="split.scale-180" FileName="[...]_1.2.0.29_scale-180.appx" Offset="21271211" Size="211615">
    			<Resources>
    				<Resource Scale="180"/>
    			</Resources>
    		</Package>
    		<Package Type="application" Version="1.2.0.29" Architecture="x86" FileName="[...]_1.2.0.29_x86.appx" Offset="21482907" Size="20655001">
    			<Resources>
    				<Resource Language="EN"/>
    				<Resource Scale="100"/>
    			</Resources>
    		</Package>
    	</Packages>
    </Bundle>


    How do I determine why these languages are being added?



    • Edited by Ed Alexander Tuesday, April 8, 2014 12:58 PM privacy
    Tuesday, April 8, 2014 12:54 PM
  • Just uploaded another package to the store with the same issue... causing a bunch of extra work... Does anyone know what determines the language codes in AppxBundleManifest.xml?
    Wednesday, May 7, 2014 7:39 PM
  • Does someone found already a solution of these duplicates, when you submit the package to the store?
    When I have 3 resource files (en, de, es), this "produces" 5 different types:

    en
    de
    de-de
    es
    es-es

    Therefore it's a lot of duplicate work for submitting the app to the store!

    I build the same app for Windows 10 UWP, but in this case no duplicate languages are shown.

    Best regards,
    RoP

    Monday, December 21, 2015 6:37 PM
  • You are not supposed to ship neutral cultures such as "de" or "es". Always use a concrete language instead, such as "de-DE" or "es-ES". Otherwise you will end up with multiple entries in the store, as soon as one of your references does ship with a concrete language version (which most modules do, becuase it is the recommended and correct way).

    Details on this are available in my answer in this topic:

    https://social.msdn.microsoft.com/Forums/en-US/19a81da7-eedd-4a5f-80b8-af0319c0496c/visual-studio-adds-an-additional-language-when-generating-appx-with-bundles?forum=windowsstore

    • Proposed as answer by Lukas F Wednesday, March 23, 2016 9:32 AM
    • Marked as answer by Ed Alexander Wednesday, March 23, 2016 1:10 PM
    Monday, January 4, 2016 5:07 PM