Skip invalidating previous mobiledevicepiar if previous is valid what… #8
Conversation
… we can check from host (TEST)
|
Pairingfile by idevice pair is slightly different then jitterbug, have o add udid into it if it’s missing |
|
Maybe with plutil -insert UDID -xml "$UDID" $UDID.mobiledevicepair |
Signed-off-by: Macley <[email protected]>
…tterbug part (aka what to do if the pair file isn't goochie)
|
final todo: test and make it proper for the jitterbug part (aka if pairingfile isn't goochie, what then?) |
…f needed the udid key. Remove jitterbug as it's not needed and unzip aswell
^when a user who has paired before, wants to sideload sidestore again 
^when a user didn't connect their phone before running the command (this is actually a requirement in the current ver, but people were just smart enough to always plug it in before running) 
^when a user deleted the provising file on the host or maybe it's properly invalid (removing random data lines makes it hang). We will keep asking so the user can be as slow as they want to be (like how we did it before). Pairing file stays valid in the first situation, only in the last situation it's invalid (which is to be expected as we re-generated it with idevicepair). |
… we can check from host (TEST)