Azoft Case Studies - Page 9 of 9 - Blog about Technology, Events & People
Azoft Case Studies

4 Steps for Avoiding Data Corruption in SQLite 3.5.9 on Android 2.1

By Alexander Ak on October 17, 2012
When it comes to Android application development, it’s often desirable to ensure the app is compatible with older versions of the Android OS. A customer has recently asked us to make an application while keeping backward compatibility down to SDK version 2.1 (API level 7). While working on that project, we encountered a problem: the built-in SQLite version 3.5.9 had a known bug that appeared under certain conditions. Incidentally, SQLite caused the application to crash due to a "database disk image is malformed" error and the entire database was rendered unusable. We didn't find a solution for this problem on the web, so we created the following workaround after some experimenting.

So, what should you do if you’ve stumbled upon this bug? Wrap database access into a content provider. The rest of this post gives step-by-step instructions on how to implement it in your own project.

4 Steps for Avoiding Data Corruption in SQLite 3.5.9 on Android 2.1

Mystery Bug in MKReverseGeocoder: Investigation by iOS Developers

By July Nikolay on September 20, 2012
When developing software applications, programmers often rely on ready solutions to handle certain tasks within the project. After all, applying a ready solution instead of developing one from scratch is much faster, cheaper and just makes sense, right? Well, not always. Today I’ll tell you about our hunt to find a hidden bug in Geocoder (iOS 4.3 SDK) that occurred while working with geolocation services. Let this be an example of how sometimes it's best to apply our own custom-built solution.