OK, I was barking up the wrong tree. Apparently this is a known problem that has already been fixed. The fix will be available in SDK 37:
OK, I was barking up the wrong tree. Apparently this is a known problem that has already been fixed. The fix will be available in SDK 37: