Sileo has been updated to version 2.4.2 with several bug fixes and improvements.

Sileo has been updated to version 2.4.2 with several bug fixes and improvements.

On Monday, the Sileo team released an update to the Sileo package manager, bringing it officially up to version 2.4.2.

After contacting Sileo Team Lead Developer Amy Weale, we learned that the latest version of Sileo features several bug fixes and improvements, including the following:

– Proper non-root support
– Improved Canister support, now uses v2 API – Search history is now displayed – Custom theme creation – Decompression speedup – Fix installing packages from deb – Overall speedup

The updated version of Sileo is now available for download from the official Sileo repository on almost any public jailbreak and is recommended for all users. This release channel is different from Sileo Beta and Sileo Nightly, the differences between which we discussed in a separate post. Depending on the jailbreak you are using, you may prefer a different build of Sileo.

Sileo has long been associated with the Odyssey Team jailbreaks, but over the years it has expanded to other jailbreaks. More recently, Sileo has become the default package manager for new jailbreaks such as Fugu15 Max and palera1n since Cydia has not been updated to support iOS and iPadOS 15 and later.

Sileo is not only actively maintained today, but is also very popular among jailbreakers due to its fast speed and nice appearance, among other features that make it stand out from the crowd. Sileo is completely open source.

If you’re not already using Sileo, chances are you can add it to your jailbroken device by adding the repository below:

https://repo.getsileo.app/

If your jailbreak is already using Sileo as its primary package management application, you should find the update waiting for you in the Procursus repository. The only jailbreak that Sileo no longer officially supports last weekend is XinaA15.

Have you updated the Sileo Package Manager application to the latest version? Be sure to let us know in the comments section below.

Leave a Reply

Your email address will not be published. Required fields are marked *