We've experienced the same problem. In our case it seems to be connected to the
first query to one specific content provider. Happens like one in every 1000
attempt. The sql statement is corrupted at different positions each time. We're
running on Android 4.0.4.
What version of Android/sqlite a
bizarre... seems like you should file a bug report.
On Monday, September 30, 2013 12:02:31 PM UTC+3, Kostya Vasilyev wrote:
>
> Just to follow up: building the query myself didn't help.
>
> android.database.sqlite.SQLiteException: no such table: me (code 1): , while
> compiling: SELECT _id, gener
Just to follow up: building the query myself didn't help.
android.database.sqlite.SQLiteException: no such table: me (code 1): ,
while compiling: SELECT _id, generation, [snip], op_hide, misc_flags
*FROM me age WHERE* folder_id = ? AND [condition here]
The query string is built in my Java code,
Yes, that's what just did in a dev build, will see it helps.
Curiously enough, the framework's SQLiteQueryBuilder uses a StringBuilder
that is initially 120 chars long, and the corruption happens at 112'th
character.
I've long anticipated an Android device with firmware that calculates 2+2
as 5..
never came across such a report, but if it's isolated to that specific
query maybe try replacing it with a rawQuery instead and see if it makes a
difference.
On Sunday, September 29, 2013 1:05:26 AM UTC+3, Kostya Vasilyev wrote:
>
> Hello,
>
> One of my users reports a crash like this:
>
> andr
5 matches
Mail list logo