Age | Commit message (Collapse) | Author | Files | Lines |
|
possible crash
|
|
|
|
|
|
|
|
|
|
This function allows creating an afc client upon an already established
connection. This is for example required for the house_arrest service.
|
|
|
|
|
|
|
|
|
|
Reports say it fixes FreeBSD detection.
|
|
|
|
otherwise, the sync in progress screen might keep showing up until you
swipe to cancel on the device
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
This change requests the initial backup files more gracefully as
the device might need more time to prepare the backup data for
bigger backups. Otherwise we cause a crash by attempting to parse
a plist message we did not receive yet when the device is busy.
|
|
|
|
|
|
|
|
|
|
Sending changes from computer to device was broken. This also allows
passing NULL for actions.
|
|
|
|
|
|
|
|
|
|
|
|
The device sends us a DLMessageDisconnect so we need to free the
device_link_service_client. Otherwise when calling mobilebackup_client_free
we get a send error from libusbmuxd.
|
|
|
|
|
|
|
|
Well, and restoring applications is missing too; this will be completed
later.
|
|
|
|
|
|
|
|
|
|
The activation_record was inserted into the request plist and freed at
the end. If the user app then uses plist_free to free the activation
record, it gets an invalid free. By using plist_copy the
activation_record is not touched.
|
|
|
|
|
|
|
|
|
|
|
|
Again, does not clean up too much, but it'll be helpful when
completing the restore part of the mobilebackup API.
|
|
This does not clean up too much for now, but when completing the rest of
the mobilebackup API it will help to provide nice and clean code.
|
|
|