[TIMOB-17086] Android: crashOnLastLaunch always returns true in titanium crittercism module
| GitHub Issue | n/a |
|---|---|
| Type | Story |
| Priority | Low |
| Status | Closed |
| Resolution | Not Our Bug |
| Resolution Date | 2014-06-06T18:04:27.000+0000 |
| Affected Version/s | Release 3.3.0 |
| Fix Version/s | n/a |
| Components | Android |
| Labels | n/a |
| Reporter | Allen Yeung |
| Assignee | Ingo Muschenetz |
| Created | 2014-06-06T18:01:40.000+0000 |
| Updated | 2017-03-13T21:31:59.000+0000 |
Description
The crashOnLastLaunch method always returns true, even after a crash in the app. The crash displays correctly on the dashboard, but the value always returns true on a subsequent app launch.
Resolving as not our bug since this is an issue with the custom _logCrashException() we use for crittercism. The API on their side does not correctly hook up the crashOnLastLaunch property with _logCrashException() and they have a task to fix it in a future release.
Closing ticket as this is not our bug.