Build fails with validation failed in Localizable.strings

I made Localizable.string files and compiled my project (my source code uses NSLocalizedString macro function) but my project doesn't compile because of the Localizable.string file. If I comment all the lines in the Localizable.string file, my project compiles successf开发者_如何学运维ully.

As result, the problem is related with the Localizable.string files. I searched about it on Google, I found that UTF-8 files (Localizable.string) has changed to UTF-16. And though I tried this... this way didn't work, too.

===============================================================

My Localizable.string file contains:

"LOCAL_APP_GRADE" = "Basic"

"LOCAL_APP_LAST_UPDATED_DATE" = "2011/04/20"

"LOCAL_MAIN_MENU_TITLE" = "Main Menu"

In my source code:

NSLocalizedString( @"LOCAL_MAIN_MENU_TITLE", @"" );

Error message:

Copy .strings file Error Validation failed: The data couldn't be read because it has been corrupted.

I'm assuming Xcode 4 here. Double check what it shows for the encoding on each of the Localization.string files in the file inspector. When I was having that error it was due to one of the files being read as Mac Roman instead of UTF-16. Once I changed the encoding the warning went away. What was driving me nuts at first was that the warning was only happening in Xcode 4. Xcode 3 did not give it.

You also have an issue with the formatting of your .string file. All of the lines should end in a semicolon.

"LOCAL_APP_GRADE" = "Basic";
"LOCAL_APP_LAST_UPDATED_DATE" = "2011/04/20";
"LOCAL_MAIN_MENU_TITLE" = "Main Menu"; 

I don't think this is the cause of the warning though. At least I've never seen a warning for it. It usually only manifests itself at runtime when LOCAL_MAIN_MENU_TITLE shows up in app instead of Main Menu. It would be nice if the build process did check for semicolons though. It's easy to miss adding one when editing the files.

Per Apple:

If you run into problems during testing and find that the functions and macros for retrieving strings are always returning the same key (as opposed to the translated value), run the /usr/bin/plutil tool on your strings file. A strings file is essentially a property-list file formatted in a special way. Running plutil with the -lint option can uncover hidden characters or other errors that are preventing strings from being retrieved correctly.

Fire up a console window, go into your project folder, and do:

/usr/bin/plutil -lint ja.lproj/Localizable.strings

(obviously replace the correct language folder name). This will tell you exactly where the problem is!

All of the lines in .strings file should end with a semicolon. It worked for me.

I had the same issue today after importing the localisations from Apple Notes and the cause was really subtle. The standard double quotes had been swapped with slanting double quotes.

Slanting double quote: ”

Standard double quote: "

I've been struggling with this same error, and ended up having a couple similar issues, but with different details. First off, even though it appears that Xcode's internal "builtin-copyStrings" tool should be able to handle either little-endian or big-endian UTF-16 files, it really only handles big endian. My theory is it's running some extra validation step (perhaps using the plutil command line utility) that didn't used to happen in Xcode 3, and that tool barfs on anything but big-endian UTF-16. Not entirely sure though.

The second trick is that you need to make sure your strings files are saved with no BOM (Byte Order Marker). I did some editing of my .strings files in BBEdit, which ended up saving a BOM to the file, and that also appears to make Xcode 4 have a conniption fit. Xcode itself doesn't appear to have any way to remove the BOM from the file, so this has to be done in a text editor such as BBEdit or TextWrangler which can do that for you.

With Xcode 10.1, one missing semicolon stops compilation with this error:

Localizable.strings: read failed: Couldn't parse property list because the input data was in an invalid format

BTW, you can find out if the error is general to your file (an encoding issue) or specific to one or more lines by temporarily removing most of the file content. You can then locate the problem by incrementally adding content back in until the error returns.

Perhaps you have something like: "Bla"="bla";;

Note the duplicate ; symbol. If you have that, it will compile properly but will fail in run time.

Related to this - take care when manually merging strings into Localizable.strings - I managed to copy/paste BOTH strings from a NSLocalizedString() macro, so that the Localizable.strings entry was in this form:

"KEY" = "STRING", @"COMMENT STRING COPIED ACROSS ALSO, IN ERROR";

The bit ,@"xxx" on building caused me to get the error:

Read failed: The data couldn't be read because it isn't in the correct format.

In this case doing a quick search on @" helped identify the places I'd done this.

I had this problem. My fix? Add a newline at the top of the file. Bizarre but it got it working for me.

So instead of at the top of my file having this:

/* comment */
"LOCAL_APP_GRADE" = "Basic"

I had to do:

[newline]
/* comment */
"LOCAL_APP_GRADE" = "Basic"

(Can't get the formatting right - don't type 'newline', just hit return!)

Looks like this is an standard message for error reading the strings file.

In my case it was a (json force of habit) colon instead of equal sign:

"key1" = "String1";
"key2" : "String2";
"key3" = "String3";

Changed it to = and everything worked fine.

My problem was, that I've forgotten ; in one of the lines

Make sure that you have declared string in following format:

"YOUR_STRING_LABEL" = "Your message";

Note: Don't forget Quotation Marks ("), Equals Sign (=) and Semicolon (;) at end.

This may be because the translation file format is wrong. You can download a mac software called Localizable.

This is the download link: https://apps.apple.com/cn/app/localizable-翻译文件工具/id1268616588?mt=12

You only need to drag Localizable.strings file to the software. and it willtell you which line in the file may have a problem.

It is useful .It saved me a lot of time. Now I share it with you, I hope it will be helpful to you.