Thank you. (I also have used Hopper plenty btw, great app!)

This fix looks good to me. I feel like we should add a check to this case too:

// Look out for any changes that involve the same named file moving to another directory

(Even though it's not strictly necessary because the old size will be 0 for a directory I think)

For these kind of fixes I also like to update latestMinorVersionForMajorVersion() -- in this case bump SUBinaryDeltaMajorVersion4 case from 1 to 2 so we can tell if a generated patch file has this fix.

edit: The SUBinaryDeltaMajorVersion3 case should be bumped from 2 to 3 too since it supports cloneable diffs.

Let me know if you are able to update this or not.

When building delta updates between my old version (which uses Sparkle 1.27.1) and my new version (using Sparkle 2.7.1), BinaryDelta fails to create the patch between the two versions of the embedded Sparkle framework because a file named SUUpdateAlert.nib is compared to a directory with the same name and path (after the .framework/Versions/{A -> B} substitution) in the old version

In this specific case, please also check the Compatibility section for delta updates. In this instance, an app with Sparkle 1.27.1 only understands how to apply version 2 delta patches (which do not support clones) so you'd pass ./BinaryDelta --version 2 in that case when creating a delta update. Then later use --version 4 (current default) for later updates.

Feel free to also pick up this patch for additional tests for this case:
d339afa

Or I can land these myself afterwards.

Sorry for the very late response, I'm not at home at the moment. I have modified the minor versions numbers, as requested.

Thank you, I think this looks good.

@bSr43 Btw, I downloaded a new version Hopper to try out. If you run defaults delete com.cryptic-apps.hopper-web-4 and on second launch, it seems like Sparkle's "Check for updates automatically?" permission prompt window gets put behind your main app window, with the sheet asking to enter a license. One way to fix that is to defer starting the updater until after that sheet is dismissed. Not sure how that'll behave if there's an update to install too, and if the issue is only present when a license isn't entered.

2.8.0 (Tahoe refresh) and 2.7.3 (security fixes) were also released recently.

Thank you @zorgiepoo, I'll improve that point in the upcoming update.