Titanium JIRA Archive
Titanium SDK/CLI (TIMOB)

[TIMOB-24463] CRASH PLSqliteException: Error occurred calling next on a PLSqliteResultSet. SQLite error: 'disk I/O error' for 'select attempts from last_attempt'

GitHub Issuen/a
TypeBug
PriorityCritical
StatusResolved
ResolutionHold
Resolution Date2018-03-28T09:52:14.000+0000
Affected Version/sn/a
Fix Version/sn/a
ComponentsiOS
Labelsn/a
ReporterCaio Perdona
AssigneeUnknown
Created2017-03-07T22:50:45.000+0000
Updated2019-03-12T01:25:50.000+0000

Description

Getting a lot of crashes in APM with the following: CRASH PLSqliteException: Error occurred calling next on a PLSqliteResultSet. SQLite error: 'disk I/O error' for 'select attempts from last_attempt'

Comments

  1. Hans Knöchel 2017-03-07

    Looks like an issue with APSAnalytics. It may or may not be caused by [this line](https://github.com/appcelerator/aps_sdk/blob/master/ios/support/analytics/APSAnalytics/APSAnalytics.m#L181) (private repo) executing the requeueing in a different sync-queue than the one calling it. I saw this a few times in sim-builds, but never took a detailed look into it. As it's really really hard to reproduce, we would either need a reproducible case or try out a new build that uses a different queue. For the second case, you could try to use [this library](https://www.dropbox.com/s/nf4lh1yh0uurtgf/libAPSAnalytics.zip?dl=1) by replacing it in ~/Library/Application Support/Titanium/mobilesdk/osx/<sdk-version>/iphone/Classes/APSAnalytics.
  2. Caio Perdona 2017-03-08

    Thanks for the feedback Hans. Will try that and follow up here...
  3. Sharif AbuDarda 2017-04-05

    Hello, Can you follow up on current status of the issue? Thanks.
  4. Hans Knöchel 2017-07-11

    [~perdona] Any update on my feedback? We want to address possible APSAnalytics issues over the next weeks, so any constructive feedback would help.
  5. Hans Knöchel 2018-03-28

    Resolving due to inactivity. As this didn't rise up again, it looks like its not an issue anymore!
  6. Dominic Maricic 2019-03-12

    Was this ever resolved? This error and several variations of it are the top 5 crash causes of our app. We do use the Axway Analytics module as well.

JSON Source