Atom feedLast 5 comments
37 years ago
Ray: Having the same problem. Very frustrating. Luckily, for some reason my released version worked on the iPad itself, but now I can't get it to run in the simulator. Getting no such table, which I'm guessing is an initialization error. Will continue to investigate.
Ray: Having the same problem. Very frustrating. Luckily, for some reason my released version worked on the iPad itself, but now I can't get it to run in the simulator. Getting no such table, which I'm guessing is an initialization error. Will continue to investigate.
38 years ago
Jeremy: FYI, I've just tried it with the SQLite 3.7.0 preview and the same problem occurs.
Also, I'm not using any extra third-party libraries with my SQLite, so the problem isn't your Unicode extension.
Jeremy: FYI, I've just tried it with the SQLite 3.7.0 preview and the same problem occurs.
Also, I'm not using any extra third-party libraries with my SQLite, so the problem isn't your Unicode extension.
38 years ago
Jeremy: I'm having the same problem with compiling SQLite against iOS 4 for the iPad simulator, but in my case it works fine running on an actual iPad (also works in the iPhone simulator and on an iPod Touch).
Same problem with 3.6.23.1, 3.6.23, and at least back to 3.6.21. Compiling against iOS 3.2 makes it work, though that's not really an option for iPhone (as opposed to iPad) apps.
I have no idea what to do about it or how big a problem it really is...
Jeremy: I'm having the same problem with compiling SQLite against iOS 4 for the iPad simulator, but in my case it works fine running on an actual iPad (also works in the iPhone simulator and on an iPod Touch).
Same problem with 3.6.23.1, 3.6.23, and at least back to 3.6.21. Compiling against iOS 3.2 makes it work, though that's not really an option for iPhone (as opposed to iPad) apps.
I have no idea what to do about it or how big a problem it really is...
38 years ago
Pascal: The problem seems to have deep roots, however there is a solution, see the updated post. :)
Pascal: The problem seems to have deep roots, however there is a solution, see the updated post. :)
The archive
March 2011 (1)
July 2010 (1)
October 2009 (2)
August 2009 (1)
July 2009 (1)
March 2009 (1)
December 2008 (1)
October 2008 (1)
August 2008 (1)
July 2008 (3)
June 2008 (1)
May 2008 (3)
March 2008 (1)
February 2008 (3)
January 2008 (2)
November 2007 (1)
October 2007 (1)
September 2007 (1)
August 2007 (1)
July 2007 (1)
June 2007 (3)
May 2007 (1)
April 2007 (1)
February 2007 (2)
January 2007 (3)
December 2006 (1)
November 2006 (3)
October 2006 (2)
September 2006 (2)
August 2006 (1)
July 2006 (2)
June 2006 (6)
The archive
Temporarily remove specific localizations from your iPhone/Mac App
Thursday, July 22th 2010 - 20:23, 1 update Friday, October 15th 2010 - 15:14
Since our translators didn't work as fast as we coders did, we were in need to strip one specific language – Spanish – from an iPhone App – MedCalc - that we'll be shipping next week. And because MedCalc has more than 140 XIB files, the same number of XML files and the double amount of strings files, it would be very tedious to manually delete all Spanish localizations (not to mention to re-add them once the translators are done). So I needed a way to tell Xcode not to include one specific language for now, for which I didn't find a solution.
1 comment
Read the full article... (1 KB)
Rafael: Thank you very much, I was having a huge headache to solve the very same problem!