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

REALLY IMPORTANT: DO NOT SUBMIT NEW THREADS FOR EVERY BETA RELEASE

On December 31st, I started "round 1" of this new Cydia beta. After some rapid iteration, essentially every remaining issue reported since then has been of the form "I have a thousand repositories installed, and three of them no longer work", but those repositories were extremely broken and should never really have worked. In practice, it was a small handful of repositories that everyone kept reporting issues related to, and almost all of those users had installed a centralized, poorly maintained, massive list of repositories :/.

The hope is that now, after nearly a month, most of the repositories that are still of any value have had a chance to see what was wrong with their configuration and have been updated, and people who insist on maintaining these centralized lists have had a chance to prune entries for broken repositories. Since ~b5, there have been no changes to Cydia to try to support broken repositories, and other than one possible issue (see below), I do not consider "prints an error about a corrupt repository" to be a bug: that's a feature.

Fixed Issues

• In the seventh beta, I made some modifications to Cytore (partly to fix an issue reported by Luca), and essentially redesigned the way APT handles errors (yet in a way that had only minimal impact on the codebase) to try to make it more resilient in a global sense to individually bad repositories (I think this may actually be a better patch for this than I had back on the older version of APT, where I had essentially played whack-a-mole).

• This sixth beta works around a warning given to users who have the same repository multiple times (once using HTTP, once using HTTPS; the new version of APT finds this annoying), fixes the dependency lookup problem that was preventing installation of packages with mixed-case constraints (such as LockHTML), and attempts to mitigate the problem where dpkg(cydo) sometimes starts failing and just returns 2.

• Luca's new jailbreak release should fix the issues with "Restart SpringBoard"; as he supports more versions of iOS and more versions of the firmware, this issue will cease to be a problem. I have thereby removed it from the notes below as it has nothing to do with Cydia, but in a way this is a change that people should know about.

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

Known Issues (Comprehensive)

• Repositories containing only a Packages.gz (no uncompressed Packages and no Packages.bz2) and some other condition (probably a lack of hashes in the Release file) might no longer function; I consider this a bug. This supposedly happened with a real repository, but I have been failing to replicate this issue in my test attempts :/.

• 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.

• Sometimes Cydia crashes while doing a refresh, but this has only been reported by a few people; the one person who was giving a good report is a heavy user, and only seemed to get very intermittent crashes. I wired up a copy of Cydia to just refresh in a loop, and it took a half hour before it crashed, and when it did the issue did not feel like something "new".

Old Issues (Not Blocking Release)

• 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 .

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).

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 I've been using this new version of dpkg and tar at least occasionally now for months--to end up wedged into a position where dpkg can't help you as dpkg itself is broken. I wouldn't install this willy-nilly: only install this with active intent.)