Titanium JIRA Archive
Appcelerator Community (AC)

[AC-116] assertion failed: 12F70: libxpc.dylib + 71768

GitHub Issuen/a
TypeBug
Priorityn/a
StatusClosed
ResolutionInvalid
Resolution Date2015-05-14T20:12:35.000+0000
Affected Version/sn/a
Fix Version/sn/a
Componentsn/a
Labelsn/a
ReporterSebastian Klaus
AssigneeRadamantis Torres-Lechuga
Created2015-05-08T11:12:15.000+0000
Updated2015-05-14T20:12:38.000+0000

Description

Operating System
  Name                        = Mac OS X
  Version                     = 10.10.4
  Architecture                = 64bit
  # CPUs                      = 8
  Memory                      = 17179869184
Node.js
  Node.js Version             = 0.10.38
  npm Version                 = 1.4.28
Titanium CLI
  CLI Version                 = 3.4.2
Titanium SDK
  SDK Version                 = 4.0.0.RC
  SDK Path                    = /Volumes/Data/Users/sebastian/Library/Application Support/Titanium/mobilesdk/osx/4.0.0.RC
  Target Platform             = iphone
Since using 4.0.0.RC and installing the latest update of Appcelerator Studio my app crashes on device. Simulator works as normal without any errors. The app crashes with
[INFO] :   1   0x100297b88
[INFO] :   2   0x10029817c
[INFO] :   3   0x1000d7284
[INFO] :   4   0x1000d7a38
[INFO] :   5   0x10039d050
[INFO] :   6   0x1003532f0
[INFO] :   7   0x100434d70
[INFO] :   8   0x10043f74c
and starts again with
[INFO] :   assertion failed: 12F70: libxpc.dylib + 71768 [B870B51D-AA85-3686-A7D9-ACD48C5FE153]: 0x7d
I can't provide any code, because I can't reproduce it in any sample app. But it seems, that I'm not the only one with this problem as mentioned here: https://community.appcelerator.com/topic/111/testing-on-the-iphone-worked-before Does anyone has an advice what to do?

Comments

  1. Sebastian Klaus 2015-05-12

    Deleting the app from device helps sometimes. But only sometimes. It's absolutely not reproducible for now
  2. Radamantis Torres-Lechuga 2015-05-12

    [~benutzername] without a test case and steps to reproduce it's very difficult to find this, can you please try to find a test case to reproduce this issue?
  3. Sebastian Klaus 2015-05-12

    it seems, I've got it fixed. I could may have an assertion bug in the following function
       exports.getRowDetailInfo = function (entry, allAttributes) {
           allAttributes = allAttributes || [];
          ....
       };
       
    changed to
       exports.getRowDetailInfo = function (entry, allAttributes) {
           var attributes = allAttributes || [];
          ....
       };
       
    seems to work now without any assertion failure crashes. But I stay attentive and will watch my code better
  4. Eric Merriman 2015-05-12

    Changing ticket type to "bug" and setting unable to reproduce. If this occurs again fro you, please reopen and we will investigate.
  5. Sebastian Klaus 2015-05-13

    The error now occurs again. The weird thing: I commented out all "console.log" and the error appears. If all my "console.log" are active, no assertion failure error appears. What will happen, when the app goes live and logs are suppressed?
  6. Sebastian Klaus 2015-05-13

    uh, I think it was my bad programming... shame on me. Seems, that this is not cool:
       Ti.App.Properties.getString('collection.filter.' + params.categoryId || Ti.App.Properties.getInt('categoryId', 0))
       
  7. Eric Merriman 2015-05-14

    [~benutzername] Vielen Dank für die Informationen. Closing ticket.

JSON Source