<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Missing language/locales in automated builds with app-download.js in ArcGIS Experience Builder Questions</title>
    <link>https://community.esri.com/t5/arcgis-experience-builder-questions/missing-language-locales-in-automated-builds-with/m-p/1683639#M22438</link>
    <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We are using automated deployment-workflows with ExB-Dev. Since upgrading to 1.19 our deployed Experiences are no longer translated. Experience are correctly built, including all the widgets- translation files, but the index.html does not list the languages in the downloadLocales array.&lt;/P&gt;&lt;P&gt;Is this a bug or am I missunderstanding the workflow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to the Guide&amp;nbsp;&lt;A href="https://developers.arcgis.com/experience-builder/guide/experience-deployment/#automated-deployments" target="_blank" rel="noopener"&gt;https://developers.arcgis.com/experience-builder/guide/experience-deployment/#automated-deployments&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;BLOCKQUOTE&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;locales&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;property can be used to specify the locales to export. If this is not set, all locales will be exported.&lt;/BLOCKQUOTE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;LI-CODE lang="javascript"&gt;node -e "require('./server/src/middlewares/dev/apps/app-download.js').zipApp('0', 'apptest.zip', 'my_client_id');"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The build process completes successfully and includes all widget translation files. For example, under&lt;BR /&gt;.../cdn/1/widgets/print/dist/settings/translations&lt;BR /&gt;all locale folders and translation files are present.&lt;/P&gt;&lt;P&gt;However, in the generated &lt;STRONG&gt;index.html&lt;/STRONG&gt;, the downloadLocales array is empty. As a result, the Experience loads only in the default language (en-US), and no other locales are available at runtime.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;script type="download-options" id="download-options"&amp;gt;{
				"downloadLocales": [""]
			}&amp;lt;/script&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That does not happen if the Experiences is built / downloaded&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;manually via ExB-Dev manually and selecting "all" for the languages&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AndreasEugster_0-1770804643047.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/148273i00BE0E10F3E0FD8B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AndreasEugster_0-1770804643047.png" alt="AndreasEugster_0-1770804643047.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;calling app-download.js with all the locales defined&lt;/LI&gt;&lt;/UL&gt;&lt;LI-CODE lang="javascript"&gt;node -e "require('./server/src/middlewares/dev/apps/app-download.js').zipApp('0', 'apptest2.zip', 'my_client_id', {locales:['en','ar','bg','bs','ca','cs','da','de','el','es','et','fi','fr','he','hr','hu','id','it','ja','ko','lt','lv','no','nl','pl','pt-br','pt-pt','ro','ru','sk','sl','sr','sv','th','tr','zh-cn','uk','vi','zh-hk','zh-tw']});"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both resulting in an index.html with the populated downloadLocales array.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;script type="download-options" id="download-options"&amp;gt;{
				"downloadLocales": ["en","ar","bg","bs","ca","cs","da","de","el","es","et","fi","fr","he","hr","hu","id","it","ja","ko","lt","lv","no","nl","pl","pt-br","pt-pt","ro","ru","sk","sl","sr","sv","th","tr","zh-cn","uk","vi","zh-hk","zh-tw"]
			}&amp;lt;/script&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally, we’d like to rely on the default behavior of exporting all available locales, rather than hardcoding and maintaining the full locale list in our automated deployment workflow.&lt;/P&gt;&lt;P&gt;If this is unintended behavior, I’m happy to open an official bug report — just looking for confirmation first.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 11 Feb 2026 10:39:10 GMT</pubDate>
    <dc:creator>AndreasEugster</dc:creator>
    <dc:date>2026-02-11T10:39:10Z</dc:date>
    <item>
      <title>Missing language/locales in automated builds with app-download.js</title>
      <link>https://community.esri.com/t5/arcgis-experience-builder-questions/missing-language-locales-in-automated-builds-with/m-p/1683639#M22438</link>
      <description>&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;We are using automated deployment-workflows with ExB-Dev. Since upgrading to 1.19 our deployed Experiences are no longer translated. Experience are correctly built, including all the widgets- translation files, but the index.html does not list the languages in the downloadLocales array.&lt;/P&gt;&lt;P&gt;Is this a bug or am I missunderstanding the workflow?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;According to the Guide&amp;nbsp;&lt;A href="https://developers.arcgis.com/experience-builder/guide/experience-deployment/#automated-deployments" target="_blank" rel="noopener"&gt;https://developers.arcgis.com/experience-builder/guide/experience-deployment/#automated-deployments&lt;/A&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;&lt;BLOCKQUOTE&gt;The&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;locales&lt;SPAN&gt;&amp;nbsp;&lt;/SPAN&gt;property can be used to specify the locales to export. If this is not set, all locales will be exported.&lt;/BLOCKQUOTE&gt;&lt;/LI&gt;&lt;/UL&gt;&lt;LI-CODE lang="javascript"&gt;node -e "require('./server/src/middlewares/dev/apps/app-download.js').zipApp('0', 'apptest.zip', 'my_client_id');"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;The build process completes successfully and includes all widget translation files. For example, under&lt;BR /&gt;.../cdn/1/widgets/print/dist/settings/translations&lt;BR /&gt;all locale folders and translation files are present.&lt;/P&gt;&lt;P&gt;However, in the generated &lt;STRONG&gt;index.html&lt;/STRONG&gt;, the downloadLocales array is empty. As a result, the Experience loads only in the default language (en-US), and no other locales are available at runtime.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;script type="download-options" id="download-options"&amp;gt;{
				"downloadLocales": [""]
			}&amp;lt;/script&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;That does not happen if the Experiences is built / downloaded&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;manually via ExB-Dev manually and selecting "all" for the languages&amp;nbsp;&lt;span class="lia-inline-image-display-wrapper lia-image-align-inline" image-alt="AndreasEugster_0-1770804643047.png" style="width: 400px;"&gt;&lt;img src="https://community.esri.com/t5/image/serverpage/image-id/148273i00BE0E10F3E0FD8B/image-size/medium?v=v2&amp;amp;px=400" role="button" title="AndreasEugster_0-1770804643047.png" alt="AndreasEugster_0-1770804643047.png" /&gt;&lt;/span&gt;&lt;/LI&gt;&lt;LI&gt;calling app-download.js with all the locales defined&lt;/LI&gt;&lt;/UL&gt;&lt;LI-CODE lang="javascript"&gt;node -e "require('./server/src/middlewares/dev/apps/app-download.js').zipApp('0', 'apptest2.zip', 'my_client_id', {locales:['en','ar','bg','bs','ca','cs','da','de','el','es','et','fi','fr','he','hr','hu','id','it','ja','ko','lt','lv','no','nl','pl','pt-br','pt-pt','ro','ru','sk','sl','sr','sv','th','tr','zh-cn','uk','vi','zh-hk','zh-tw']});"&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Both resulting in an index.html with the populated downloadLocales array.&lt;/P&gt;&lt;LI-CODE lang="markup"&gt;&amp;lt;script type="download-options" id="download-options"&amp;gt;{
				"downloadLocales": ["en","ar","bg","bs","ca","cs","da","de","el","es","et","fi","fr","he","hr","hu","id","it","ja","ko","lt","lv","no","nl","pl","pt-br","pt-pt","ro","ru","sk","sl","sr","sv","th","tr","zh-cn","uk","vi","zh-hk","zh-tw"]
			}&amp;lt;/script&amp;gt;&lt;/LI-CODE&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Ideally, we’d like to rely on the default behavior of exporting all available locales, rather than hardcoding and maintaining the full locale list in our automated deployment workflow.&lt;/P&gt;&lt;P&gt;If this is unintended behavior, I’m happy to open an official bug report — just looking for confirmation first.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 10:39:10 GMT</pubDate>
      <guid>https://community.esri.com/t5/arcgis-experience-builder-questions/missing-language-locales-in-automated-builds-with/m-p/1683639#M22438</guid>
      <dc:creator>AndreasEugster</dc:creator>
      <dc:date>2026-02-11T10:39:10Z</dc:date>
    </item>
  </channel>
</rss>

