I got the same error when simply coping DisplayStrings.strings file from the sample MoveMe to my resources folder. Have you figured out why causing the error?
It could be as simple as a missing ;, or extra " in the file somewhere. Apparently it can be as complicated as perl version problems if you've installed your own copy of perl.
The problem with this error is that it could mean anything. It could mean you just left out a ;, or it could be something more complicated.
(I'm posting here because this is the first entry I found in google!)
The problem is the type of the list you want to read. I guess you just took the MoveMe example and copied the *.strings file? So your file settings are wrong and the compiler tries to read the file with some sort of extra compatibility. Just press the Apple key + i and you will get to the menu where you can setup the type of the list (in my case it was simply "text") or whatever you have.
(I'm posting here because this is the first entry I found in google!)
The problem is the type of the list you want to read. I guess you just took the MoveMe example and copied the *.strings file? So your file settings are wrong and the compiler tries to read the file with some sort of extra compatibility. Just press the Apple key + i and you will get to the menu where you can setup the type of the list (in my case it was simply "text") or whatever you have.
For me, I mess up the DisplayStrings.strings in MoveMe example and try to copy a new one back. And I got that message "Copystrings failed with exit code 1".
I follow your suggestion by right-click>get info the file and set the file type to just text. And it works. The Placard shows the word "Welcome".
It could be as simple as a missing ;, or extra " in the file somewhere. Apparently it can be as complicated as perl version problems if you've installed your own copy of perl.
I agree with you.
I had the same error and finally resolved the error.
I was using a ".strings" file that had data in wrong syntaxes I fixed them and its working now
No, set the File Type to "Text" doesn't help much, if there's an error in the file, it will still be there, even no error reporting.
I just meet the same problem, and I found a nice solution.
My solution is to use the following Regular Expression to verify your text line by line, if there's any line not matched, there must be a problem.