Search the Community

MyAppStore is unique appdb feature - you can build your own apps library and store it on appdb servers, apps will always be installable to your devices, jailbroken or not. IPA way to your device through MyAppStore is the following: You upload IPA file to appdb Appdb creates job to analyse your IPA to make sure it is valid and installable Appdb stores IPA into your library You can trigger app installations from MyAppStore section via "install" method from main API MyAppStore API acts on the same endpoint and with same principles as our Main API, but adds couple new methods that you can use. Adding IPA to library By using this method you can upload IPA for analyse to appdb. Device auth is required. It should return true if IPA was successfully queued to be analysed. Then, you can check what's happening with your job: Getting jobs status By using this method you can check what jobs are running. Device auth is required. It should return job objects. All fields are self-explainable: {"success":true,"errors":[],"data":[{"id":"xxxx","updated_at":"1511865973","status":"Success: appdb_1.4.2.ipa was validated, added to your apps","is_finished":"1"}],"total":null} Getting IPA library And finally, here is how to obtain IPAs in your library. Device auth is required. It should return the following information. All fields are self-explainable: {"success":true,"errors":[],"data":[{"id":"656","bundle_id":"com.4sh2812.32u1982378","uploaded_at":"1511865973","name":"appdb","size":"35172335","compatibility_string":"Requires iOS 8.0 or iPhone, iPod iPad "}],"total":null} Deleting IPA from library Device auth is required. Installing IPA Just trigger "install" method of main API with ID of IPA and type="MyAppStore". Device auth is required.

show the bundle ID of the uploaded package.

Hi, ipa in MyAppStore is ready to install via rickpactor, but download failed. It seems like a download timeout error in rickpactor? I followed the link "appdb.to/download.php?t=SFNqRW5...MWQ0PQ==&action=download" got a http 404 page Thank you!

After several issues with installing Facebook++ with the new installer, I found out that it is due to the shortcomings of the new installer. The old installer had the option for renaming the uploaded app as well as installing it alongside another version of the app. Losing that feature meant that now I have to rely on ++ tweaks (that aren't always 100% stable when sideloaded) or deal with stock app store apps...which means why even buy PRO. I bought pro for this very reason and as of the past week I have not had time to experiment and delete apps and retry. So basically if I this feature does not get reimplemented then I may have to try another service. I'm not trying to be threatening, its just frustrating that a feature thats been in beta for years loses more essential features than it creates. I trust that Freddy will get it all fixed, but please be quick!