SignTools VS ios-app-signer

check this out https://github.com/SignTools/SignTools (personally haven't tried it)

There are two components to self-hosting SignTools, the web frontend, and the actual signing server, the latter of which must be run on macOS. Fortunately there's a guide to set it up so that you use GitHub Actions as the signing server, which gives you a certain amount of free minutes per month. I've never gotten close to the limit, even when I'm signing a few dozen apps. The guide also shows you how to set up the web frontend on Railway, which also offers free monthly credits, so you can actually self-host both components for free: https://github.com/SignTools/SignTools/blob/master/INSTALL-SIMPLE.md

SignTools (it's nice for developers with Apple Developer Accounts), for regular users it's kind of a hustle

The SignTools developer (tool that I used to sign other apps with working push notifications) said this about the document posted above:

im new to this i used to use appdb but i kept getting revoked so now i got a dev account for me to make apps and also use it to sideload idk what app to use , i saw some people talk about SignTools to get notification is there any other way to get notification other than that app? i only use it for cercube and rocket insta so please help

Keeping the original bundle ID is required, but not enough for PN working. You have to use a distribution certificate & an explicit profile with the correct PN entitlement. AltStore/Sideloadly cannot do it so you have to do it manually. I recommend you take a look at SignTools if you need working PN: https://github.com/SignTools/SignTools

This is quite easy to do if you are using SignTools. When signing an app, make sure to select Use custom when choosing bundle identifier options and specify it in the aforementioned format. When it's signed, your sign in should work.

It is a very involved process that requires XCode (a very bloated developer application made by Apple), the latest version of OS X and a third party application called iOS App Signer. This allows you to sign ipa files temporary for 7 days (after that they won’t launch and need to be re-signed), which allows them to run on your iOS device. The reason why this process is so convoluted and annoying is that Apple doesn’t want people doing it. This article has a more detailed explanation on how to sideload apps: https://dantheman827.github.io/ios-app-signer/. You can find the ipa files to sideload on the Web Archive (https://archive.org/download/minecraft-pocket-edition-versions-ipa), but keep in mind that any version before 0.10.0 is 32-bit and won’t run on modern iOS. Also remember that the older versions use the same package name as the newer ones and will override any existing Minecraft installation on that iOS device.

Sideload daibutsu with XCode+iOS App Signer v1.13 (do not use Sideloadly for daibutsu)

Proof for my „claim“ in this thread: https://github.com/DanTheMan827/ios-app-signer.

I’ve been using this for about a year: https://dantheman827.github.io/ios-app-signer/ I only sign stuff for myself and my family and I’ve never had an issue with my certificate

iOS App Signer on GitHub

If you have an Developer Account, you can get around the need for a Signing Service. Use https://dantheman827.github.io/ios-app-signer/ to sign the apps. You can use Apple's developer portal to obtain the Certificates and Profiles you need.

I second this. Ideally with the option to „register“ mobileprovisions which you can chose with a drop down menu or something. Using iOS App Signer (https://github.com/DanTheMan827/ios-app-signer) an then sideloadly again is kinda cumbersome.

If you are using a Mac, use Xcode+iOS App Signer. Not the most straightforward process, but it is the most reliable sideloading method available