blobsaver
blobsaver copied to clipboard
airsquared
Error retrieving beta versions
Enabling "Include Betas" will produce an error. The only workaround to save blobs for beta versions is to manually specify a URL.
This is due to the BetaHub API being shut down without warning. Any GET request to the API returns code 302. I am looking for an alternative API or another way to do this.
Logs
HTTP Response was (GET https://www.betahub.cn/api/apple/firmwares/iPhone12,8?type=2) 302
maybe something like https://ipswdownloads.docs.apiary.io/ ?
This is already used in blobsaver for release versions; but it doesn't provide information on betas.
Maybe use https://ipswbeta.dev/ ?
This website doesn't provide information on the signing status of betas - same issue with https://appledb.dev/ .
Hey @airsquared I've thought a great way to make saving bets blobs happen! Although you can't find the signing status just from ipswbeta.dev but you can fetch the list of available IPSW from ipswbeta.dev and let the users choose which version to save(while notifying that they can only save blobs that are signed) or you can make it automatically fetch the signing status here.
TL;DR Fetch beta IPSWs from one website and fetch signing status from the other.
Hey @airsquared ive thought a great way to make saving bets blobs happen! Although you can't find signing status just from ipswbeta.dev but you can fetch the list of available ipas from ipswbeta.dev and let the users choose which version to save(while notifying that they can only save blobs that are signed) or you can check signing status at https://idevicecentral.com/ios-updates/ios-beta-signing-status/
genius
Hey @airsquared ive thought a great way to make saving bets blobs happen! Although you can't find signing status just from ipswbeta.dev but you can fetch the list of available ipas from ipswbeta.dev and let the users choose which version to save(while notifying that they can only save blobs that are signed) or you can check signing status at https://idevicecentral.com/ios-updates/ios-beta-signing-status/
genius
Lol thanks, but I'm the only one who does not really code for others and talking like a genius, like those corrupt politicians.
Hey @airsquared ive thought a great way to make saving bets blobs happen! Although you can't find signing status just from ipswbeta.dev but you can fetch the list of available ipas from ipswbeta.dev and let the users choose which version to save(while notifying that they can only save blobs that are signed) or you can check signing status at https://idevicecentral.com/ios-updates/ios-beta-signing-status/
genius
Lol thanks, but I'm the only one who does not really code for others and talking like a genius, like those corrupt politicians.
That's actually a good simile, might steal that >:D
Hey @airsquared ive thought a great way to make saving bets blobs happen! Although you can't find signing status just from ipswbeta.dev but you can fetch the list of available ipas from ipswbeta.dev and let the users choose which version to save(while notifying that they can only save blobs that are signed) or you can check signing status at https://idevicecentral.com/ios-updates/ios-beta-signing-status/
genius
Lol thanks, but I'm the only one who does not really code for others and talking like a genius, like those corrupt politicians.
That's actually a good simile, might steal that >:D
(⁎⁍̴̛ᴗ⁍̴̛⁎)
Based on the whole situation with Cryptex, saving these beta blobs will not be useful until we are able to save Cryptex blobs as well. Because of this, I will be holding off on implementing this feature until we can save Cryptex blobs.
If someone else wants to work on @olivertzeng's idea, I can help and accept a PR. Another idea I had (if someone else wants to try) was to write a new API that just updates a GitHub repository with json files every hour or so with GitHub Actions.
Based on the whole situation with Cryptex, saving these beta blobs will not be useful until we are able to save Cryptex blobs as well. Because of this, I will be holding off on implementing this feature until we can save Cryptex blobs.
If someone else wants to work on @olivertzeng's idea, I can help and accept a PR. Another idea I had (if someone else wants to try) was to write a new API that just updates a GitHub repository with json files every hour or so with GitHub Actions.
Thanks @airsquared !
Based on the whole situation with Cryptex, saving these beta blobs will not be useful until we are able to save Cryptex blobs as well.
I mean, you never know who knows what the future will look like maybe they'll be some exploit that we can use them with or something...
You can still save blobs for beta versions manually with an IPSW URL, if you really want to. I just won't be working further on beta versions until there is a clear way to use them.
I realized now that all my saves have potentially been broken since I haven't updated in a while and have been relying on the background service. Furthermore, all my saved devices have the beta firmware option checked, so it would have been broken anyways I reckon.
Since there won't be an update and there still isn't a way to persist saved-device changes, is there a way to mass edit them so I don't have to re-create all of my profiles?
@Infinitay It will always save blobs for non-beta versions first before attempting (and failing) to save blobs for beta versions, meaning your blobs will still be saved regardless of whether beta blobs are working or not.
If you want to edit them anyway, you can export them to XML, edit the XML file, then import the new XML file.
You can also use the CLI:
blobsaver --export export.xml
sed -i 's/"Include Betas" value="true"/"Include Betas" value="false"/g' export.xml
blobsaver --import export.xml
@Infinitay It will always save blobs for non-beta versions first before attempting (and failing) to save blobs for beta versions, meaning your blobs will still be saved regardless of whether beta blobs are working or not.
If you want to edit them anyway, you can export them to XML, edit the XML file, then import the new XML file.
You can also use the CLI:
blobsaver --export export.xml sed -i 's/"Include Betas" value="true"/"Include Betas" value="false"/g' export.xml blobsaver --import export.xml
whoa cool thank you @airsquared ||However blobs are useless anyway(I'm on A15)...||
Hey @airsquared I've thought a great way to make saving bets blobs happen! Although you can't find the signing status just from ipswbeta.dev but you can fetch the list of available IPSW from ipswbeta.dev and let the users choose which version to save(while notifying that they can only save blobs that are signed) or you can make it automatically fetch the signing status here.
TL;DR Fetch beta IPSWs from one website and fetch signing status from the other.
I've updated my comment.
It will always save blobs for non-beta versions first before attempting (and failing) to save blobs for beta versions, meaning your blobs will still be saved regardless of whether beta blobs are working or not.
After almost a month I checked my folder and noticed that it still didn't save any of the new iOS versions because I assumed this held true. It does not. I tested it now myself too on my new phone and a new folder, and the blobs weren't saving because I had beta versions checked. Whether I was force checking the background task or doing a manual run.
After exporting, disabling saving beta, and importing, everything worked fine.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. If you would like this issue to remain open, please comment.
![stale[bot] avatar](https://avatars.githubusercontent.com/in/1724?v=4 "Published by a pub.dev verified publisher"){kind=small}
Don't know what has happened but it seems the url you provided: https://www.betahub.cn/api/apple/firmwares/iPhone12,8?type=2 works just fine
Don't know what has happened but it seems the url you provided: https://www.betahub.cn/api/apple/firmwares/iPhone12,8?type=2 works just fine
EDIT: It's down again