You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If in the Packages file, rootful (iphoneos-arm) is 1st and rootless (iphoneos-arm64) is below it then everything seems to work just fine.
If it's the other way around and the iphoneos-arm64 one is 1st in Packages, then swiping and clicking Upgrade works, but going to the depiction view and clicking Modify > Upgrade selects the rootless one although the device has an older rootful version installed.
Also, if the repo serves the previous versions for a package, also both types, then clicking on Downgrade (both from the swipe or the Modify button), lists two rows of the previous version. They are ordered the way they are in the Packages file, whichever is 1st is on top in the "Select Version" modal view.
To Reproduce
Put 5 or 6 "Package:" blocks in a Packages file, 3 versions of the same package, 2 different architectures for the newer versions (iphoneos-arm and iphoneos-arm64), the oldest version doesn't need the rootless version listed. The blocks for the same version should be identical except for the fields "Architecture:", "Filename:", and the hashes (and maybe the "Size:" and "Installed-Size:"). On a device with a rootful jb, have the oldest version or the middle version installed and try upgrading it while having the 2 different architecture blocks of the newest version one after the other and vice versa in the Packages file.
For the downgrade issue to occur just get the package upgraded and click on Downgrade to see the list of the available versions, it lists all of them, 3 or 4 rows depending if you had the oldest version also listed as rootless.
Expected behavior
For upgrades, it should select the same "Architecture" of the package, as the one currently installed (from the Modify button).
For downgrades, it could also only list the corresponding ones, based on what's already installed.
Device Information:
iOS Version: 14.3 and 14.8
Zebra Version: 1.1.30
Device Type: iPhone
Jailbreak Type: either Taurine or unc0ver, these things occur on both
Additional context
The blocks in the Packages file don't really need to be one right after the other for this nuicance to occur, I mean if other packages are in between or whatever, it acts on the particular package obviously but the order does matter.
Also, at the moment I'm working with package version numbers containing tildes denoting alphas/betas, like eg.
"1.1.0~a15" vs "1.1.0~a16" vs "1.1.0~a18"
"1.6~b3" vs "1.6~b4"
The text was updated successfully, but these errors were encountered:
Describe the bug
If in the Packages file, rootful (iphoneos-arm) is 1st and rootless (iphoneos-arm64) is below it then everything seems to work just fine.
If it's the other way around and the iphoneos-arm64 one is 1st in Packages, then swiping and clicking Upgrade works, but going to the depiction view and clicking Modify > Upgrade selects the rootless one although the device has an older rootful version installed.
Also, if the repo serves the previous versions for a package, also both types, then clicking on Downgrade (both from the swipe or the Modify button), lists two rows of the previous version. They are ordered the way they are in the Packages file, whichever is 1st is on top in the "Select Version" modal view.
To Reproduce
Put 5 or 6 "Package:" blocks in a Packages file, 3 versions of the same package, 2 different architectures for the newer versions (iphoneos-arm and iphoneos-arm64), the oldest version doesn't need the rootless version listed. The blocks for the same version should be identical except for the fields "Architecture:", "Filename:", and the hashes (and maybe the "Size:" and "Installed-Size:"). On a device with a rootful jb, have the oldest version or the middle version installed and try upgrading it while having the 2 different architecture blocks of the newest version one after the other and vice versa in the Packages file.
For the downgrade issue to occur just get the package upgraded and click on Downgrade to see the list of the available versions, it lists all of them, 3 or 4 rows depending if you had the oldest version also listed as rootless.
Expected behavior
For upgrades, it should select the same "Architecture" of the package, as the one currently installed (from the Modify button).
For downgrades, it could also only list the corresponding ones, based on what's already installed.
Device Information:
Additional context
The blocks in the Packages file don't really need to be one right after the other for this nuicance to occur, I mean if other packages are in between or whatever, it acts on the particular package obviously but the order does matter.
Also, at the moment I'm working with package version numbers containing tildes denoting alphas/betas, like eg.
"1.1.0~a15" vs "1.1.0~a16" vs "1.1.0~a18"
"1.6~b3" vs "1.6~b4"
The text was updated successfully, but these errors were encountered: