Keyboard Extension crash on start

Question

brenboh OP

Created Feb ’17

Replies 4

Boosts 1

Views 2.3k

Participants 5

I am developing a custom keyboard extension and recently I have been experiencing a crash when the extension starts.

The crash happens when the keyboard is trying to load, an expception is thrown but not from my code and then the default keyboard is shown.

The crash doesn't happen every time it loads but if I keep switching keyboards after a couple times it will crash again.

I have also started a fresh project that only contains Apple boiler plate keyboard code and it still crashes in a similar manner.

Exception Type:  EXC_CRASH (SIGQUIT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note:  EXC_CORPSE_NOTIFY
Triggered by Thread:  0


Filtered syslog:
None found


Thread 0 Crashed:
0   dyld                           0x00000001001c7ec8 gdb_image_notifier(dyld_image_mode, unsigned int, dyld_image_info const*) + 0
1   dyld                           0x00000001001c7b58 notifyGDB(dyld_image_states, unsigned int, dyld_image_info const*) + 60
2   dyld                           0x00000001001c0c84 dyld::notifyBatchPartial(dyld_image_states, bool, char const* (*)(dyld_image_states, unsigned int, dyld_image_info const*), bool, bool) + 1012
3   dyld                           0x00000001001cb70c ImageLoader::link(ImageLoader::LinkContext const&, bool, bool, bool, ImageLoader::RPathChain const&, char const*) + 140
4   dyld                           0x00000001001c1358 dyld::link(ImageLoader*, bool, bool, ImageLoader::RPathChain const&, unsigned int) + 228
5   dyld                           0x00000001001c23cc dyld::_main(macho_header const*, unsigned long, int, char const**, char const**, char const**, unsigned long*) + 2572
6   dyld                           0x00000001001bd044 _dyld_start + 68


Thread 0 crashed with ARM Thread State (64-bit):
    x0: 0x0000000000000000   x1: 0x000000000000009b   x2: 0x000000016fd80960   x3: 0xfffffff0001fc088
    x4: 0x0000000000000303   x5: 0x0000000000000000   x6: 0x0000000000000000   x7: 0x0000000000000dd0
    x8: 0x00000001001c7ec8   x9: 0x0000000000624510  x10: 0x00000001876a4110  x11: 0x000000000000001b
   x12: 0x0000000000000001  x13: 0x00000001001efbb8  x14: 0x000000016fd804d8  x15: 0x00736b726f77656d
   x16: 0xffffffffffffffe1  x17: 0x0000000000000010  x18: 0x0000000000000000  x19: 0x000000016fd80960
   x20: 0x000000000000009b  x21: 0x0000007cd5615875  x22: 0x00000001001ed000  x23: 0x000000000000009b
   x24: 0x0000000000000000  x25: 0x00000001001edc08  x26: 0x0000000000000018  x27: 0x000000000000008e
   x28: 0x00000001001f50d8   fp: 0x000000016fd80460   lr: 0x00000001001c7b58
    sp: 0x000000016fd80440   pc: 0x00000001001c7ec8 cpsr: 0x60000000

Anyone else experiencing this issue?

Boost

Answer 1

ANE7258 OP

Jul ’17

I've got the same problem but can't figure out a solution. Could you fix it ? Anyone else?

0

Answer 2

chaozhuyin OP

Oct ’17

Have you had any workaround for this?

0

Answer 3

chrismillet2 OP

Nov ’17

I am experiencing this crash as well, and my crash logs look almost exactly like yours. I believe the issue is related to the extension taking too long to load, in my case potentially due to too many Cocoapods included in my project. I haven't solved the issue but this is where I am focusing. Reason for this assumption came from this WWDC video: https://developer.apple.com/videos/play/wwdc2017/413/ which indicates that with the new dyld, they'll begin crashing apps immediately if load times are too long.

0

Answer 4

abdullahajmal OP

May ’24

Having the same issue. Did you find a solution for this?

0