Astro Pad Pro and Spine


First, let me say that I am very impressed with AstroPad pro. I’m making a good effort to have it replace my Cintiq 13HD, which I was never 100% happy with the screen quality.

I’m having a problem with the Spine app ( a 2d animation app )

Every time I try to add key commands to it ( since no useful ones appear by default ) - AstroPad simply quits on the iPad Pro.



Is there a crash log generated?


Sure is. This is the first part before it just starts listing threads and binaries that were running.

{“app_name”:“Astropad Studio”,“timestamp”:“2017-01-18 11:59:14.67 +0000”,“app_version”:“1.0”,“slice_uuid”:“2a425c72-f100-3e82-9921-3445771a7801”,“adam_id”:1181582576,“build_version”:“2541.1”,“bundleID”:“com.astro-hq.AstropadStudio”,“share_with_app_devs”:true,“is_first_party”:false,“bug_type”:“109”,“os_version”:“iPhone OS 10.2 (14C92)”,“incident_id”:“95604432-29EB-4512-B1B0-B54B746AF535”,“name”:“Astropad Studio”}
Incident Identifier: 95604432-29EB-4512-B1B0-B54B746AF535
CrashReporter Key: bbc47811e095734cc7edf36187e13263f3c5952d
Hardware Model: iPad6,7
Process: Astropad Studio [494]
Path: /private/var/containers/Bundle/Application/4E29C999-1437-4867-B2B4-CD5E970B38E9/Astropad Studio
Identifier: com.astro-hq.AstropadStudio
Version: 2541.1 (1.0)
Code Type: ARM-64 (Native)
Role: Foreground
Parent Process: launchd [1]
Coalition: com.astro-hq.AstropadStudio [452]

Date/Time: 2017-01-18 11:59:14.6284 +0000
Launch Time: 2017-01-18 11:59:06.0768 +0000
OS Version: iPhone OS 10.2 (14C92)
Report Version: 104

Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Triggered by Thread: 0

Application Specific Information:
abort() called

Filtered syslog:
None found

Last Exception Backtrace:
(0x18528d1b8 0x183cc455c 0x18516da0c 0x100065a8c 0x10013df90 0x10013e6ac 0x10013e3f0 0x10015bff0 0x10015bf64 0x100118770 0x10011965c 0x10008f728 0x10008f35c 0x18b170d30 0x100202518 0x18b170cb0 0x18b15b128 0x18b17059c 0x18b1700c4 0x18b16b328 0x18b13bda0 0x100202378 0x1001380e0 0x18b92575c 0x18b91f130 0x18523ab5c 0x18523a4a4 0x1852380a4 0x1851662b8 0x186c1a198 0x18b1a67fc 0x18b1a1534 0x1000c54bc 0x1841495b8)


Did this happen when entering any type of key command? Or a certain/specific keys?
Was this over USB or wifi connection?


This happened as soon as I pressed the button to configure commands. (Edit ahortcuts) I didn’t even get to try and enter a key command.

Over USB.


Thanks for the added details, as well as bringing this issue to our attention.
We’re working on a fix, and will hopefully have this resolved soon.



Just wanted to let you know that we’ve found and fixed the problem. An update will be going out shortly.