summaryrefslogtreecommitdiffstats
path: root/m4
diff options
context:
space:
mode:
authorGravatar Nikias Bassen2019-01-27 05:06:51 +0100
committerGravatar Nikias Bassen2019-01-27 05:06:51 +0100
commitf2ebaf2b564ca4b9e875d1b6c724bea2087b9489 (patch)
treefc0624fe8c03184b0a50cbbeb1eb2d078c34c435 /m4
parent3100d735cf8887df1c1dc1946bc9d7ea20b27d34 (diff)
downloadlibideviceactivation-f2ebaf2b564ca4b9e875d1b6c724bea2087b9489.tar.gz
libideviceactivation-f2ebaf2b564ca4b9e875d1b6c724bea2087b9489.tar.bz2
ideviceactivation: Check ActivationState for success if lockdownd_activate() returns no result
On older devices it might happen that lockdownd does not return any result, neither success nor failure, when invoking lockdownd_activate(). This results in the code to assume the operation failed. Instead of relying on the return value of that function we query the actual ActivationState to see if it is not "Unactivated" anymore to determine if the activation was successful.
Diffstat (limited to 'm4')
0 files changed, 0 insertions, 0 deletions