SPRINGBOARD, Process detected doing insecure drawing while in secure mode

I have never seen this before, does anyone have any idea on this one?


This came from a crash log, wont post the whole thing, but...



Date/Time: 2017-11-20 12:19:23.8143 +1100

Launch Time: 2017-11-20 06:32:37.3878 +1100

OS Version: iPhone OS 11.1.1 (15B150)

Baseband Version: 4.00.01

Report Version: 104


Exception Type: EXC_CRASH (SIGKILL)

Exception Codes: 0x0000000000000000, 0x0000000000000000

Exception Note: EXC_CORPSE_NOTIFY

Termination Reason: Namespace SPRINGBOARD, Code 0x2bad45ec

Termination Description: SPRINGBOARD, Process detected doing insecure drawing while in secure mode

Triggered by Thread: 0


Thread 0 name:

Thread 0 Crashed:

0 libsystem_kernel.dylib 0x0000000186570bc4 mach_msg_trap + 8

1 libsystem_kernel.dylib 0x0000000186570a3c mach_msg + 72 (mach_msg.c:103)

2 CoreFoundation 0x0000000186a21c74 __CFRunLoopServiceMachPort + 196 (CFRunLoop.c:2613)

3 CoreFoundation 0x0000000186a1f840 __CFRunLoopRun + 1424 (CFRunLoop.c:2969)

4 CoreFoundation 0x000000018693ffb8 CFRunLoopRunSpecific + 436 (CFRunLoop.c:3245)

5 GraphicsServices 0x00000001887d7f84 GSEventRunModal + 100 (GSEvent.c:2245)

6 UIKit 0x000000018ff142f4 UIApplicationMain + 208 (UIApplication.m:3949)

7 HubMobile 0x0000000100c25598 main + 88 (main.m:16)

8 libdyld.dylib 0x000000018646256c start + 4

Replies

The code 0x2bad45ec (“too bad for sec”) indicate some sort of “security violation”, although currently its only being raised in this specific case, indicated by the text “Process detected doing insecure drawing while in secure mode” (in this case “secure mode” means that the screen has been locked). It’s unlikely that this is caused by a problem with your app. It’s currently being investigated at our end (r. 33936538).

If you have a way to reproduce this problem, we’d love to hear about it. In that case please file a bug report with your steps to reproduce and ask for it to be related to the above-mentioned bug. I’d also appreciate you posting your bug number here, just for the record.

Finally, I’ve filed a bug to get this exception code listed in TN2151, which is the best place to learn more about these sorts of exception codes (r. 35851588).

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

I have the same crash in some of the recent crash reports of my app. I couldn't find anything related to this crash in TN2151 you linked. Could you point me to where I can see follow-ups? Thanks.

I couldn't find anything related to this crash in TN2151 you linked.

Right. I’ve filed a bug requesting that TN2151 be updated with info about 0x2bad45ec, but that has not yet happened. In the meantime, my advice from earlier stands: this is unlikely to be caused by a problem with your app.

Share and Enjoy

Quinn “The Eskimo!”
Apple Developer Relations, Developer Technical Support, Core OS/Hardware

let myEmail = "eskimo" + "1" + "@apple.com"

Thanks for your replies,

So far I have not been able to reproduce it but at the same time it is still happening and I am still looking through the crash logs each week to try and find something. It is a large app with a somewhat old code base in objective c. I am thinking there is a possibility that a timer is attempting to draw something when the app is in the background but have not had any success finding anything.

We are seeing this happen for a user who is recording a run using background GPS. It appears to happen almost immediately after the app goes into the background. It's been happening to the same user, and so far this is the only report we have for it. At least one time it happened while the user had Background App Refresh disabled on their phone, and at least one other time it happened with Low Power Mode turned on, but I believe it's also occurred with neither of those settings in play.


I am attempting to gather a sysdiagnose from the user, and will file a radar if we are able to do so!


If there's anything else we can gather that would be useful please let me know.

Are you recieving any push notifications? Also are you attempting to send the data or just record it to file?


I am still trying to nail this one down, so far was looking more toward what I was doing on push notifications, but we are also using background GPS so I wonder if this is related. Might change angles and look into the background GPS.

When sending the app into background, the SDK that is responsible for creating a snapshot image for the app switcher does not finish on time, and the screen will be locked (FaceId, passcode). From there, no drawing is allowed and we get a 0x2bad45ec (too bad for sec) error once we unlock.

Here is a video with reproduction steps:

Note:

  • iPadOS 15
  • Multiwindow same app (Craft Docs in this case)
  • Editing a textfield (in this case with magic keyboard attached)
  • FaceID enabled on device
  • Lock screen and QUICKLY UNLOCK! no time for system to generate snapshot and crashes

https://youtu.be/IcWwHdGyFhQ

Hi

Do we have any solution for this, is it iOS issue OR App issue? I saw in my apps we facing this error a lot. We are seeing many SIGKILL crash for this reason, OR can say 5-6 out of 10 SIGKILL is this. Please help here.