1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
| Dec 14 10:34:39 iPhone1000 assertiond[62] <Notice>: Submitted job with label: UIKitApplication:com.yeelion.kwplayer[0xa651][62]
Dec 14 10:34:39 iPhone1000 sharingd[57] <Notice>: SystemUI changed: 0x10 -> 0x0
Dec 14 10:34:39 iPhone1000 dasd(DuetActivitySchedulerDaemon)[137] <Notice>: Trigger: <private> is now [<private>]
Dec 14 10:34:39 iPhone1000 dasd(DuetActivitySchedulerDaemon)[137] <Notice>: Foreground app changed\M-b\M^@\M^T-<private>
Dec 14 10:34:39 iPhone1000 kernel(IOTextEncryptionFamily)[0] <Notice>: AppleFairplayTextCrypterSession::fairplayOpen() failed, error -42022
Dec 14 10:34:39 iPhone1000 assertiond(BaseBoard)[62] <Error>: Unable to get short BSD proc info for 487: No such process
Dec 14 10:34:39 iPhone1000 assertiond(BaseBoard)[62] <Error>: Unable to get proc info for 487: No such process
Dec 14 10:34:39 iPhone1000 assertiond[62] <Error>: Process handle (com.yeelion.kwplayer, <BSProcessHandle: 0x10312e040; com.yeelion.kwplayer:487; valid: NO>) is invalid. Returning error {
BKSProcessExitReason = 0;
BKSProcessJobLabel = "UIKitApplication:com.yeelion.kwplayer[0xa651][62]";
NSLocalizedFailureReason = "Unable to obtain valid process handle";
}
Dec 14 10:34:39 iPhone1000 assertiond[62] <Notice>: Deleted job with label: UIKitApplication:com.yeelion.kwplayer[0xa651][62]
Dec 14 10:34:39 iPhone1000 SpringBoard(AssertionServices)[52] <Error>: [com.yeelion.kwplayer] Bootstrap failed with error: <NSError: 0x281ef6430; domain: BKSProcessErrorDomain; code: 1 (bootstrap-failed); reason: "Unable to obtain valid process handle">
Dec 14 10:34:39 iPhone1000 SpringBoard(FrontBoard)[52] <Error>: Bootstrapping failed for <FBApplicationProcess: 0x1494dc500; com.yeelion.kwplayer; pid: -1> with error: Error Domain=BKSProcessErrorDomain Code=1 "Unable to bootstrap process with bundleID com.yeelion.kwplayer" UserInfo={NSLocalizedFailureReason=Unable to obtain valid process handle, BKSProcessExitReason=0, BSErrorCodeDescription=bootstrap-failed, BKSProcessJobLabel=UIKitApplication:com.yeelion.kwplayer[0xa651][62], NSLocalizedDescription=Unable to bootstrap process with bundleID com.yeelion.kwplayer}
Dec 14 10:34:39 iPhone1000 SpringBoard(FrontBoard)[52] <Notice>: Adding: <FBApplicationProcess: 0x1494dc500; com.yeelion.kwplayer; pid: -1>
Dec 14 10:34:39 iPhone1000 SpringBoard(FrontBoard)[52] <Notice>: <FBApplicationProcess: 0x1494dc500; com.yeelion.kwplayer; pid: -1> exited.
Dec 14 10:34:39 iPhone1000 SpringBoard(FrontBoard)[52] <Notice>: Removing: <FBApplicationProcess: 0x1494dc500; com.yeelion.kwplayer; pid: -1>
Dec 14 10:34:39 iPhone1000 SpringBoard[52] <Notice>: Application process state changed for com.yeelion.kwplayer: <SBApplicationProcessState: 0x2811b7cc0; pid: -1; taskState: Not Running; visibility: Unknown>
Dec 14 10:34:39 iPhone1000 SpringBoard[52] <Notice>: Process exited: <FBApplicationProcess: 0x1494dc500; com.yeelion.kwplayer; pid: -1> -> <FBApplicationProcessExitContext: 0x281e94de0; exitReason: (none); terminationReason: (none)> {
stateAtExit = <FBProcessState: 0x2810991c0; pid: -1; taskState: Unknown; visibility: Unknown>;
}
SpringBoard(Security)[52] <Notice>: Trust evaluate failure: [leaf IssuerCommonName LeafMarkerOid SubjectCommonName]
SBDeviceApplicationSceneEntity
Ad-hoc distribution is notoriously tricky. If you've missed one thing, the whole chain fails. Here's what I can think of, off the top of my head, based on the fact that it works for at least one of your users:
1,Are you certain that the mobile ad-hoc provisioning certificate contains the UDID for the users who are seeing it fail?
2,Do those users have an old certificate on their device? (i.e. did you delete the existing certificate before installing a new one? Settings->General->Profiles)
3,Are you certain the code-signed .app bundle contains the UDIDs for those users, inside the file named embedded.mobileprovisioning? (Under the ProvisionedDevices key)
4,Is the mobile provisioning certificate expired?
5,Is your developer code-sign certificate expired?
6,Was the application package renamed by the user before installation?
7,Did you try doing a clean before doing the distribution build?
8,Is your app is unencyypted before resign?
|