Fire crash on debug run iOS App

ios

(Carlos Frias) #1

Fire 10.0.0.2337
iOS 12.0.1
macOS 10.13.6

Fire crashes when uploading to the device. Te app is uploaded to the device, but when it’s launching crashes Fire and the app in the phone. Later you can open the app (iOS) without problems.

Below are a crashing app and console Fire crash reports.

Fire_2018-10-24-033822_maqui.crash.zip (27.3 KB)
AppBorrame.zip (5.0 MB)


Failed to verify code signature: no code signature found
(Carlos Frias) #2

Can someone help me with this? (I have fallen into oblivion)


(marc hoffman) #3

Curious. the crash log really doesn’t have any actionable info in the stack :(. Does this happen every time? With any app to just the one?

Thread 0 Crashed:: Fire Main Thread  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	0x00007fff64f7420a mach_msg_trap + 10
1   libsystem_kernel.dylib        	0x00007fff64f73724 mach_msg + 60
2   com.apple.CoreFoundation      	0x00007fff3cf3cff5 __CFRunLoopServiceMachPort + 341
3   com.apple.CoreFoundation      	0x00007fff3cf3c347 __CFRunLoopRun + 1783
4   com.apple.CoreFoundation      	0x00007fff3cf3b9b7 CFRunLoopRunSpecific + 487
5   com.apple.HIToolbox           	0x00007fff3c21bd96 RunCurrentEventLoopInMode + 286
6   com.apple.HIToolbox           	0x00007fff3c21bb06 ReceiveNextEventCommon + 613
7   com.apple.HIToolbox           	0x00007fff3c21b884 _BlockUntilNextEventMatchingListInModeWithFilter + 64
8   com.apple.AppKit              	0x00007fff3a4cca73 _DPSNextEvent + 2085
9   com.apple.AppKit              	0x00007fff3ac62e34 -[NSApplication(NSEvent) _nextEventMatchingEventMask:untilDate:inMode:dequeue:] + 3044
10  com.apple.AppKit              	0x00007fff3a4c1885 -[NSApplication run] + 764
11  com.apple.AppKit              	0x00007fff3a490a72 NSApplicationMain + 804
12  com.remobjects.fire           	0x000000010e85c645 +[Program Main::] + 261
13  libdyld.dylib                 	0x00007fff64e2d015 start + 1

(RemObjects) #4

Thanks, logged as bugs://81309


(marc hoffman) #5

On closer inspection, this seems to be a stack overflow inside LLDB (Apple’s debugger), on tread 25, even though the actual crash is reported for Thread 0, which mislead me. We’ll need to investigate.

Would still be helpful to hear if you see this for any app, or just this one.


(Carlos Frias) #6

Fire crash with any app and always.

I just did tests with several projects.

Maybe you want to prepare some log?


(marc hoffman) #7

Reproduced. thanx!


(marc hoffman) #8

What’s your device, an iPhone XS or XR?


(Carlos Frias) #9

I have tried with an iPhone XS and also with a SE.


(marc hoffman) #10

Curious, because additional research since I asked this pretty much confirms that the problem is with lldb not supporting arm64e yet, which the XS has, but the SE doesn’t. Sure the SE fails the same way? I can reproduce your problem with my XS, but (while I don’t have an SE) not with any of my “older” devices, they all work fine…


(Carlos Frias) #11

You are right. Effectively it works with SE.

About XS:

I just did a test on the Mac with XCode 10.0 (10A255) and the debugger works perfectly. I understand that Xcode uses the same lldb as Fire. So why does not it work with Fire, Water or VS?

What do I have to do to develop Apps for XS?


(marc hoffman) #12

Good.

Well. both use LLDB, which is open source, but Xcode and Elements boathouse their own “copy” of it, of course. Xcode’s version of LLDB has been updated to support arm64e, but those changes are not in the open LLDB code yet, so we don’t see them yet. We need to either wait for that or work out what fails and fix it ourself (which is what we’re working on right now).

For now, you can develop for XS, you just cannot debug. You can debug on the SE and in the Simulator, and you can use “Deploy” w/ manual launch to test on XS. Not super convenient, but hopefully not a total showstopper until we’ve figured things out?

Tomorrow’s build will fix the crash and “cleanly” fail sating that arm64e isn’t supported yet, and hopefully we’ll get debugging working soon (but not in time for tomorrow’s build, I’m afraid :().


(RemObjects) #13

bugs://81309 got closed with status fixed.


(RemObjects) #14

bugs://81309 got reopened.


(RemObjects) #15

bugs://81309 got fixed closed with status fixed.