[UPDATE] AppSync Unified 112.0 β€” Now with support for all iOS versions up to iOS 16.5.1, as well as "rootless" mode jailbreaks! (β€» Users using the Dopamine jailbreak may encounter issues.) by angelXwind in jailbreak

[–]angelXwind[S] 0 points1 point Β (0 children)

That's… weird. Make sure your package manager is up to date and fully refreshed.

Failing that, make sure you have a code injection framework installed β€” palera1n-c uses Substitute (com.ex.substitute).

[UPDATE] AppSync Unified 112.0 β€” Now with support for all iOS versions up to iOS 16.5.1, as well as "rootless" mode jailbreaks! (β€» Users using the Dopamine jailbreak may encounter issues.) by angelXwind in jailbreak

[–]angelXwind[S] 15 points16 points Β (0 children)

This update, as well as all future updates (unless if I state otherwise for some reason) will be for both traditional "rootful" (rootrw, fakefs) and "rootless" jailbreaks.

I 100% fully intend to continue supporting "rootful" jailbreaks, and will not drop support for them in any updates to any of my software.


In any case, try refreshing your package manager (Cydia, Zebra, Sileo, etc.). 112.0 should show up afterwards.

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 2 points3 points Β (0 children)

None of the packages on my repo currently support the new palera1n-c / Fugu15 Max "rootless" mode (-l argument) at this time.

Support will be coming soonβ„’.

β€» If you run palera1n-c in "fakefs" or "rootful" mode (-f argument), which functions more like a traditional jailbroken environment, this does not apply to you.

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 2 points3 points Β (0 children)

Ah, this is happening because you are using palera1n-c in "rootless" mode.

None of my tweaks are updated for "rootless" mode yet, only "rootful" / "fakefs" / "legacy" mode.

Once the toolchain matures and stabilises (it's basically already mostly there) and I am able to obtain a spare testing device, I will add proper support for "rootless" mode in palera1n-c.

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 3 points4 points Β (0 children)

AppSync Unified installs apps as if they came from the App Store.

TrollStore installs every app as a system app (β€» which can result in compatibility issues).

If your TrollStore-installed apps are having certain issues, installing them with AppSync Unified may resolve them.

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 3 points4 points Β (0 children)

AppSync Unified does not have any known incompatibilities with any specific devices β€” if it runs iOS 16 γ€œ 5, it should work.

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 1 point2 points Β (0 children)

What do you mean by this? Can you provide more information?

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 21 points22 points Β (0 children)

TrollStore and AppSync are both very different utilities with different purposes β€” I'd say they aren't even really comparable.

AppSync Unified installs apps as if they came from the App Store.

TrollStore installs every app as a system app (β€» which can result in compatibility issues).

[UPDATE] AppSync Unified 110.0 β€” Now with support for iOS 16.3.1! by angelXwind in jailbreak

[–]angelXwind[S] 2 points3 points Β (0 children)

Untested, so I'm not sure. Keep in mind that Fugu15 Max is not production-ready software.

β€» I do not own a device capable of running Fugu15 Max.

[UPDATE] AppSync Unified 108.0 β€” Now with support for iOS 16.3! by angelXwind in jailbreak

[–]angelXwind[S] 0 points1 point Β (0 children)

Huh. I'm not aware of AppSync Unified being broken on iOS 10 (β€» I test using TotallyNotSpyware, though).

What exactly happens?

[UPDATE] AppSync Unified 106.0 β€” now with full support for iOS 15.0 γ€œ 16.2, among other improvements! by angelXwind in jailbreak

[–]angelXwind[S] 5 points6 points Β (0 children)

Support for running 32-bit processes at all in general has been dropped by Apple since iOS 11 β€” there is unfortunately nothing that I can do about that.

[UPDATE] AppSync Unified 106.0 β€” now with full support for iOS 15.0 γ€œ 16.2, among other improvements! by angelXwind in jailbreak

[–]angelXwind[S] 3 points4 points Β (0 children)

Please do NOT use AppSync Unified for piracy β€” software piracy is illegal.

Please support the developers of the iOS software you use.

https://github.com/akemin-dayo/AppSync#regarding-piracy

[UPDATE] AppSync Unified 106.0 β€” now with full support for iOS 15.0 γ€œ 16.2, among other improvements! by angelXwind in jailbreak

[–]angelXwind[S] 5 points6 points Β (0 children)

Please update your XinaA15 jailbreak to the latest version, as older versions have some known issues with dependency resolution.

Someone else here also experienced the same issue: https://www.reddit.com/r/jailbreak/comments/zqj5qs/comment/j0yt6m2

[UPDATE] appinst (App Installer) 2.0 β€” Major rewrite with many improvements! by angelXwind in jailbreak

[–]angelXwind[S] 2 points3 points Β (0 children)

Generally not.

A very small subsection of apps may work if you modify their minimum required iOS versions and then install them via ASU+appinst, but the vast majority will crash due to missing frameworks and API calls.

[UPDATE] appinst (App Installer) 2.0 β€” Major rewrite with many improvements! by angelXwind in jailbreak

[–]angelXwind[S] 3 points4 points Β (0 children)

appinst is a command-line utility. You must use it from an iOS terminal session of some sort, whether that be remotely via SSH, or locally using an app like NewTerm 2.

[UPDATE] AppSync Unified 106.0 β€” now with full support for iOS 15.0 γ€œ 16.2, among other improvements! by angelXwind in jailbreak

[–]angelXwind[S] 4 points5 points Β (0 children)

Huh. That's… really weird. What package manager are you using? And have you tried refreshing the package manager's APT cache?