Publish Error: "localized property XML should have a valid language associated with it."

On the third screen of the Package Wizard, where you define the installation file, at the bottom there is a dropdown menu to define the LANGUAGE of the binary file. It must be defined, and should be consistent with your detection logic.

Since this appears to be the Korean version of Firefox, that value should be set to "Korea".

Thanks for your support, but it seems still have the same error, my setting have changed as below:

Package Name: Mozilla Firefox 32.0.3 (Korean)

Description:  This package does not require a previous version exist to be applicable.  This version addresses bug fixes and feature enhancements.

System reboot may be required for the upgrade to be successful.

Classification:  SecurityUpdates

Bulletin ID:   MFSA 2014-73

Product:   Firefox

Vendor:   Mozilla

Article ID: 

Cve ID:   CVE-2014-1568

Severity:  Critical

Package Source: Firefox Setup 32.0.3.exe

Publish Location:  https://download-installer.cdn.mozilla.net/pub/firefox/releases/32.0.3/win32/ko/Firefox Setup 32.0.3.exe

Binary Language:  Korean

I also confirmed Firefox Setup 32.0.3.exe is Korean without problem.  So I'm very confused

Can you please export your modified package, without binary, and attach the resulting CAB to a reply?

Sorry for the late reply. pls help check below CAB:

This would be immensely more helpful if you would EXPORT this package to a CAB file (without the BINARY FILE), and post the CAB file as an attachment.

That way I can inspect the package in the Package Wizard, which will be exponentially faster than trying to manually parse this XML from a forums post. :-)

One additional question: Have you actually installed the Korean Firefox on a Korean-language instance of Windows and visually verified all of the registry keys, values, pathnames, filenames, and version numbers?

Oh, sorry for the miss.

I have attach the CAB file

So.. I have good news... and bad news.. depending on your perspective.

I was able to successfully publish your package. There's nothing wrong with the *package* as relates to the publishing operation.

So, if you could post a screenshot of the actual error message you're receiving, possibly I can get a better handle on what's happening.

So, I attach the error message to you.

Same error as before. Is there anything need to modify in target update server for language?

Thank you.

I'm inquiring internally as to possible environmental causes for this error message.

As noted, it published without issue on my system, so it's not anything with the package.

That's very weird.... I just have no idea how to start the investigation.

Anyway, thanks so much for your kindly support.