[TIMOB-24060] iOS crashing without any log on SDK 6.0.0
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | Critical |
Status | Closed |
Resolution | Duplicate |
Resolution Date | 2016-11-11T20:42:27.000+0000 |
Affected Version/s | Release 6.0.0 |
Fix Version/s | n/a |
Components | iOS |
Labels | CLI, SDK6.0.0, Titanium, iOS, listView, netw |
Reporter | Caio Perdona |
Assignee | Hans Knöchel |
Created | 2016-10-20T21:41:43.000+0000 |
Updated | 2017-03-24T18:37:42.000+0000 |
Description
Hi guys.
My app has a listView that has 3 sections. Each section has a button to trigger a request that populates the list with specific data.
It was working fine on SDK 5.X.X, but now it is crashing kind of randomly without showing any logs on Titanium CLI using SDK 6.0.0 beta.
Attached is the log report I exported from Xcode, but logs are not symbolicated (it appears only titanium logs are not symbolicated).
Any help on this issue?
Thanks in advance!
Attachments
File | Date | Size |
---|---|---|
PiniOn 01-11-16 13-32.crash | 2016-11-02T07:00:24.000+0000 | 67473 |
PiniOn 20-10-16 19-06.crash | 2016-10-20T21:34:55.000+0000 | 53619 |
PiniOn 28-10-16 18-12.crash | 2016-11-02T07:00:13.000+0000 | 53532 |
PiniOn 28-10-16 19-09.crash | 2016-11-02T07:00:22.000+0000 | 61166 |
Reading the crash data, it looks like something to do with http requests (
Ti.Network.HTTPClient
) or remote images in your list view. - Do you have those? - Does this only happen on device? - Does this work with other iOS versions? - Do you use kroll-thread or main-thread? And please provide a demo-code to reproduce. Otherwise it will be hard to track down your use-case. Thx!Hi Hans. No, I don't have remote images in my listView. This happens on simulator and on iOS 9.3 as well. I'm not sure if I run main-thread. How can I be sure of that? I will build a demo code for since I don't have permission to share the actual code with you, but it is a simple listView with template, populated via a json response from a endpoint in our API. It was working fine until we bumped to 6.0.0. Thanks in advance.
Yes, you said that before. So what we need is the snippet of code that is causing it. Usually you just isolate the issue and recreate a reproducible test-case fir that. You can check whether you use main-thread in your tiapp.xml by checking if you have the
run-on-main-thread
property set totrue
.I don't even have this property on my tiapp.xml. Will write a test-case and send you asap.
[~perdona] any updates? :) actually i'm pretty sure there's dSYM file generated. did you check inside the generated build folder?
@Chee Hi! I'm trying to isolate the issue using the less code possible. Still couldn't reproduce outside the app. Where exactly inside the generated build folder?
[~perdona]
<your project folder>/build/iphone/build/Products/Debug-iphonesimulator/
Yeah, found it. How do I upload it to you guys?
Oh please don't upload it to us. you have to use it in combination with your crash file to symbolicate it. check out this link: https://developer.apple.com/library/content/documentation/IDEs/Conceptual/AppDistributionGuide/AnalyzingCrashReports/AnalyzingCrashReports.html https://developer.apple.com/library/content/technotes/tn2151/_index.html
Thanks Chee. Will update you guys asap.
Guys, I got a fully symbolicated log. Should I upload it to you?
[~perdona] sure, I don't think there's any private information in the log. If there is, you can blanko them somehow.
How can I attach files on comments?
[~perdona] you should be able to attach it to the ticket itself rather than comments. otherwise, you can email to me.
@Chee Kiat Ng Just emailed them to you.
[~perdona] Have you been able to isolate the issue so far? Without that, we won't be able to do anything. Thx!
@Hans Knoechel Actually I haven't. App is crashing in several circumstances, not only on the listView. I thought the logs would be enough and more accurate for you. I tried to isolate the issue, but I couldn't get it to crash in a generic snippet... If you really need it, I can work on that.
I have attached the crash logs. It's going to be mostly guess work, so if [~perdona] you can isolate the issue, it'll be incredibly helpful. We haven't seen something like this from other folks.
Resolving as a duplicate of TIMOB-24139 which has been fixed just today. Just found out that the log
was exactly what occurred in the other ticket as well. Please try the latest 6.0.0 build which will already include the fix. Thx!
Closing ticket as duplicate with reference to the linked issues.