-
-
Notifications
You must be signed in to change notification settings - Fork 95
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Updates #166
Comments
the altsource spec provides timestamps and versions but the app has no actual access to the apps installed onto your device so if they attempt something like that it would end up being guesswork trying to determine update prompts (except for feather itself), as for the app installing itself, afaik there's not really a technically feasible way to do that, you'll always have to sideload it via other means to succeed the install |
As castdrian mentioned yes it is difficult to really determine if an app needs an update. For example, many piracy repos reuse the same bundleIdentifier for hundreds of applications which make it extremely difficult to differenciate between apps. As for in-app updating, the only feasable way of doing this is to require an external server with zsign to sign with your certificates. So the app can be fed to your device through a server instead of locally (locally would cause a crash, as you would be streaming the IPA to iOS.. while iOS is attempting to update at the same time) |
Though, I will keep this feature in mind in the future. |
I think a good PoC for this would be something along the lines of:
struct LatestFeatherInstalledAppVersion {
let appRepository: String
let bundleID: String
let version: String
}
|
Can we possibly get a feature in the future that will show if the apps we have signed/installed have an update available including the Feather App itself? Also I would like to be able to update the Feather App within itself. Currently it crashes and says it was unable to install the Feather app when I try to install the new updated version. Thanks
The text was updated successfully, but these errors were encountered: