https://cydia.saurik.com/api/share#?source=http://apt.saurik.com/beta/cydia-arm64/&package=cydia

DO NOT SUBMIT NEW THREADS FOR EVERY BETA RELEASE DURING THE ROUND (IT SCATTERS FEEDBACK)

Unlike even Substrate, Cydia is a "critical component", in that if I push a global upgrade to Cydia and it no longer works (such as crashing on startup, which is effectively unrecoverable), I have to go watch Elizabethtown on loop for a week, to truly let sink in the opening line. Even if it fails for only 1% of users... that's tens of thousands of people.

As somebody once said: there's a difference between a failure and a fiasco. A failure is simply the non-presence of success; any fool can accomplish failure. But a fiasco?... a fiasco is a disaster of mythic proportions; a fiasco is a folktale told to others that makes other people feel more alive because it didn't happen to them.

As of this most recent, thirteenth beta, I have run out of refresh/loading crash reports submitted by users (with the exception of an "old issue" I was reminded of, and have added to the list below; this issue should not affect users upgrading Cydia, as it is something that only comes up during the initial install and jailbreak process).

I'm still somewhat concerned about some issues being reported by people where the new version of APT freaks out and stops showing them any packages, but I'm not sure the extent to which this is a rare corner case; I'm thinking this latest beta might be something that can be released as a final build to all users (finally).

If you run into this, please install CrashReporter from Cydia and use Yalu 10.2 beta7 (which makes crash logs work correctly), then post the symbolicated crashlogs (from /var/mobile/Library/Logs/CrashReporter) to this thread.

PLEASE LEAVE SUCCESS STORIES: this build seems to be working out well enough that "works great for me" would be really useful to see from people, to avoid misunderstandings due to "well, no one was actually testing it" ;P.

Changed Issues

• The fourteenth beta fixes an issue reported in this thread where Cydia was failing to substitute high-level package names for package identifiers in the progress output, due to a really stupid mistake I made in beta 10 (and now I'm concerned there will be a regression, but we'll see).

• The thirteenth beta is supposed to be exactly the same package as the twelfth beta, but some consider it to be cursed. (As evidence of this: for some reason, the binary is actually markedly different. My surprise and confusion at this revelation is probably only surpassed by your boredom and annoyance while reading this change entry.)

• In the twelfth beta, I fixed something I broke in the sixth beta: the script that sets up the virtual firmware package was failing for multiple reasons, which led to a handful of users being unable to install packages that had a dependency on specific firmware version ranges.

• We do not speak of the eleventh beta.

• In the tenth beta, I fixed what seems to be the only remaining "Cydia crashes during refresh" issue (which turned out to be a bug in APT that is probably happening to people occasionally on Debian and Ubuntu; while I've fixed other bugs in APT this week, some of them crashes, this is the only one I bet is happening in production on Linux).

• In the tenth beta, I also re-fixed an issue I had found with the progress feedback display in a different way that seems to have more reliably solved the issue some users reported of not being given a "Return to Cydia" button after adding a repository. This change also made the title bar stop flashing (an issue only in some beta versions).

• Luca's new Yalu 10.2 jailbreak (not Cydia, as this had nothing to do with Cydia) fixes the issues with "Restart SpringBoard", which now supports all 64-bit devices other than the iPhone 7 (which at this time I believe still requires using the older, non-functional, Yalu 10.1.1 b3 jailbreak).

• For information on the eight and ninth betas, consult the recent thread on Round 3.

• For information on the sixth and seventh betas, consult the recent thread on Round 2.

• For information on the first through fifth betas, consult the older thread on Round 1.

Known Issues (Comprehensive)

• Recently, I've seen people starting to report an error "too many open files" when they have a large number of repositories; I don't know if the number of open files has only recently been limited on iOS 10 or what is going on, but that's my current thesis (and something I am still looking at); if you are getting this with a small number of repositories, that would be important to find out.

• Someone reported that upgrades of Cydia always show "Restart SpringBoard" momentarily before the (totally expected, if unfortunate) behavior where it gets killed by Launch Services. That choice of button was a (minor) bug: it should have shown "Close Cydia"! I've fixed that in my build locally (post beta fourteen), and it will come out in either the fifteenth beta (if there is one) or the final release.

Old Issues (Not Blocking Release)

• Users who have cached web requests stored in Cydia's cache folder (which most often happens in the unsupported state users end up in if they try to do an iOS upgrade of a jailbroken device, but I'm concerned this can happen in other ways as well) can sometimes find Cydia unable to start, as these files cannot be parsed on different versions of the firmware; and, rather than report an error, Apple's code just hits a breakpoint and aborts the program.

• People are reporting the update badge doesn't work; I'm thinking this actually hasn't worked in a while, and honestly I never found this functionality useful (as Cydia does not and never did do work in the background, so it is essentially always telling you things that used to be true the last time you used Cydia...), so I've moved this into this "old issues" section.

• After upgrading or modifying or reinstalling or in any way touching Cydia itself, the next time a package installation finishes, Cydia will immediately exit as if it had crashed: what is actually happening is Launch Services has noticed the Cydia application has been updated, but it is awkwardly still running, so it "helpfully" kills Cydia (and as of the massive Cydia update from last year, it no longer runs as root and is no longer immune to Launch Services pulling shenanigans).

• The Changes panel is supposed to elide "the entire catalog appears out of nowhere the first time you do a Refresh", but this apparently only works if Cydia is shipped pre-loaded with a catalog (which all jailbreaks for years have been doing, but Luca's no longer does).

• It is possible to "escape" the installation sequence by bringing up the task switcher and then killing Cydia; this allows people to make modifications concurrently to an installation or stress code that might rely on code or data which has just been uninstalled or modified :(. (FWIW, while I consider this a serious functionality issue, the fact that this lets you avoid "Restart SpringBoard" on iOS 10 is sort of useful, though I honestly don't know what you would do then as even manually restarting backboardd over SSH wedges the system... the only really correct thing to do right now on iOS 10 is to reboot.)

• On some peoples' devices, dpkg always returns "2". This has been the case for years, I have absolutely no clue why this happens, and it makes me very very sad. Thanks to this jailbreak coming with a (dangerously insecure-by-default) SSH daemon, ashikase (who ran into this problem, by chance) was able to give me a copy of the corrupt status file, and I have added some mitigations for this.

• Cydia shows an older style of icon in the app switcher on iOS 7 .

• Some people really really really hate that you can't dismiss the keyboard of an empty search in Cydia by tapping on the screen: as this is, in fact, slightly different behavior than other interfaces (such as the App Store), this should likely be fixed at some point (and there was a patch floating around which may or may not have been helpful for it).

Quasi-Issues (Don't Worry ;P)

• This version of Cydia is probably a performance regression from previous versions as APT 1.14 is probably slower than my hacked-for-speed APT 0.7.25 (though the upstream developer has paid close attention to many of my patches and has been working on making it possible for me to upgrade: going forward, I believe the drift is small enough that we will be able to just merge my changes, which I think is really great). It is also not clear to me that a 64-bit build of Cydia can ever be as fast as a 32-bit build of Cydia running on a 64-bit device (due to memory bandwidth limitations: 64-bit processes are larger, heavier, and generally slower than 32-bit ones). However, realistically, I don't consider this a serious problem: if nothing else, it is possible that the parts of Cydia that were limited by memory bandwidth a long long time ago aren't anymore due to new hardware.

• The 32-bit version of Cydia is using a different version of APT from the 64-bit version of Cydia (which sounds more ludicrous than it is); I am going to work on fixing this (and originally, when I was working on this weeks ago, was going to wait on releasing any of this work until I had this solved, but the iOS 10 jailbreak has made the 64-bit build of Cydia actually a priority to release: I honestly don't know why yet, but it fixes the "you can't click anything" bug).

• There was possibly a behavior change while removing repositories as of this beta: now the refreshing process always happens with a progress controller dialog. If this is true, the old behavior was probably better, but this would have been a side effect of fixing two bugs; given that it is harmless, I am going to treat it more as a feature request.

Non-Issues (You Should Know)

• So, this is not a bug, but someone is going to complain as if it were a bug, so I need to make it clear here: if you have a Substrate extension loaded into Cydia that was specifically designed to target Cydia, that extension will probably stop working (in what is likely to be a reasonably harmless way: it will just "not load") as Cydia before only ever needed 32-bit extensions, but now also uses 64-bit ones.

• This new version of Cydia is possibly much more particular about corrupted or invalid repositories than previous versions. I'm going to say that it is not a serious issue to me unless having a single broken repository causes Cydia to load no packages at all: the correct behavior is the broken repository should be the only one whose packages disappear. (This is something I'm concerned might happen, because APT is generally really bad at this; my hacked up copy of APT 0.7 was really really good at this, and I brought forward many, but maybe not sufficient, fixes.) That said, I'm interested in repositories that used to work but no longer work, but do not guarantee that I will consider Cydia/APT at fault (one example: repositories with a Release file that is missing the indentation before the hashes now generate an error and fail to load; unless this is extremely extremely common I just want to see them fixed).

• I certainly do not consider it an issue with Cydia, but for the record: it turns out that "Limitless" is installed as a separate application but is attempting to reuse Cydia's state folders (which is really annoying), and so if you are running into weird "lock" errors (or potentially other state issues), you should try to uninstall Limitless, reboot your device, do a "reinstall" of Cydia, and potentially delete all of your Cydia state folders. The entire reason Cydia moved to a separate set of state folders from the system-wide APT state last year was to guarantee there would never be these kinds of conflicts and to set up for this year's major APT update, and then... :(.

(To be clear: if it isn't on this list, I don't care how long you have personally experienced the issue... I don't know it is happening; it is possible I did at one point and forgot, but I generally try to clear all known bugs every year when I do the major Cydia build updates. Seriously: you could swear it has happened to you every single day for the past six years, but that doesn't help anyone else as I don't know it is an issue and so it can't get fixed.)

(If you install this and something seriously bad happens, the previous version of Cydia is 1.1.27, which can be easily downloaded and installed manually; arguably of greater concern, though, is that this is also updating dpkg and tar, so it is possible--though I think very unlikely as tons of users have now been using this new version of dpkg and tar for the past month--to end up wedged into a position where dpkg can't help you as dpkg itself is broken. Regardless, I wouldn't install this willy-nilly: only install this with active intent.)