Unable to install with feather

[insitedd]

Was able to install with feather previously using iPhone & iPad. Removed certificate & mobileprovision from apple account, then uninstalled feather from both devices.

Created a new certificate & mobileprovision for iPhone & iPad. Installed feather to both devices again. It launches and works on both devices.

iPad is able to install .ipa files using the new .p12 & .mobileprovision, iPhone is not. Online install method is also unable to connect on iPhone.

[insitedd]

I believe this is a bug btw, as it was working before

[nickk024]

Having the same issue as well, potentially could be a beta thing as I am running 18.2. Was working without issue and all of a sudden it stopped.

[TeslaMan3092]

Same issue here, was working fine but now it's doing this. ESign works fine though.

[khcrysalis]

localhost.direct got revoked and I'm waiting for a response from the owner of the domain to give me a new bundle, which is why this problem is occuring as it relies on an SSL certificate.

For context:
itms-services needs a valid https url when it comes to installing apps, presumably to keep things secure, without https it will just fail. Which is why I bundled a localhost.direct certificate and private key within the app.

[D1mar0n]

Наличие той же проблемы, что и в качестве бета-версии, так как я запускаю 18.2. Работал без проблем, и вдруг остановился. I also have the latest beta version of the firmware installed and until recently everything worked, but now nothing can be installed. You need to activate the "Signature Server" application settings - then the installation is completed successfully. Let's be patient and wait for the new version of the application...

[theory18]

Hi, to verify as i have the same issue, is this an issue where we just have to wait for a newer version of Feather? Or is there a way we can fix this? I can’t seem to find a proper solution to this issue in this thread.

thanks in advance.

[khcrysalis]

localhost.direct got revoked and I'm waiting for a response from the owner of the domain to give me a new bundle, which is why this problem is occuring as it relies on an SSL certificate.

Theres going to be a new build once I get the new bundle

[Farman2019]

Yesterday was fine today stuck at sending manifest… resset change certificate didnt resolve ios 17.3

[khcrysalis]

read above.

[Farman2019]

read above.

I dont know how to activate signiture server and put which http , tried profile dns http same thing please could u clarify step by step

[AushevAhmad]

read above.

I dont know how to activate signiture server and put which http , tried profile dns http same thing please could u clarify step by step

Settings -> Server Options -> Enable 'Online Install Method'. Use default server. That's it! If you don't have that option then you should update Feather to latest version.

[Farman2019]

read above.

I dont know how to activate signiture server and put which http , tried profile dns http same thing please could u clarify step by step

Settings -> Server Options -> Enable 'Online Install Method'. Use default server. That's it! If you don't have that option then you should update Feather to latest version.

What is default server ? I have activated online install but not work
Thanks for replay

[nickk024]

This has been working fine for me for now using the online install method as long as I am connected to a WiFi network. I am patiently waiting for a fix for the other method! Thank you so much for all that you are doing @khcrysalis , love the app.

[Farman2019]

This has been working fine for me for now using the online install method as long as I am connected to a WiFi network. I am patiently waiting for a fix for the other method! Thank you so much for all that you are doing @khcrysalis , love the app.

I have done this now install apps but with integrity problem

[khcrysalis]

That doesn't seem server related but it seems like your certificate is bad, are you sure you're using valid certificates?

[Farman2019]

That doesn't seem server related but it seems like your certificate is bad, are you sure you're using valid certificates?

Yes also changed to other certificates the same thing!

[ZhangYiQiu]

localhost.direct got revoked and I'm waiting for a response from the owner of the domain to give me a new bundle, which is why this problem is occuring as it relies on an SSL certificate.

For context: itms-services needs a valid https url when it comes to installing apps, presumably to keep things secure, without https it will just fail. Which is why I bundled a localhost.direct certificate and private key within the app.

Upinel/localhost.direct#18 (comment)

A password must be set for the private key

[khcrysalis]

I'm aware, but I'm awaiting a new private key as stated in my message so I can bundle it without it being inside the github repository in a public eye.

[alibusut]

I have previously tried to solve the application issues, but so far, the installation issue has not been resolved.

I am not exactly sure where the problem lies, but it seems to be related to generating the installation link. This seems to result from an issue with the SSL certificate for localhost.direct.

I don’t know why you still rely on localhost.direct instead of using your own SSL certificate or guiding others in the README.md to rely on their domain’s SSL certificate.

Feather is a fantastic application, built with great effort and beautiful design. However, the issue I mentioned is what causes users to stop using Feather.

I wish you success in your work and hope these issues are resolved as soon as possible.

[khcrysalis]

#182 (comment)

[lokiuox]

Here are a few ideas on how to prevent this issue in the future:

• Generate a CA and localhost cert on first app boot and ask the user to install the CA
• Allow the user to import a custom certificate + private key and set a custom domain for the local installation instead of hardcoding "localhost.direct". This way anyone with a domain or custom DNS can use the local install without having to rely on localhost.direct

[XEJK]

Here are a few ideas on how to prevent this issue in the future:

• Generate a CA and localhost cert on first app boot and ask the user to install the CA

• Allow the user to import a custom certificate + private key and set a custom domain for the local installation instead of hardcoding "localhost.direct". This way anyone with a domain or custom DNS can use the local install without having to rely on localhost.direct

The second option would be the best many of us using this app are developers and most of us do have domain names for which we are able to generate certs.

[khcrysalis]

Hey everyone, I've released https://github.com/khcrysalis/Feather/releases/tag/v1.2.0 which should include new certificates used for the local-installation method. It should now work (from my testing) provided if you have the proper entitlements (like before) to use it (i.e. old kravasign certificates will not work).

Happy sideloading!

[khcrysalis]

NOTE: If you really want to use your own SSL certificate, I have provided that option to you by letting you overwrite the files within its documents folder, while also changing the domain it tries to install from.