#Iloader Archlinux Keyring problem

1 messages · Page 1 of 1 (latest)

jagged wharf
#

Im on archlinux (omarchy to be exact) and when running iloader (installed through AUR iloader-bin) and having my device connected i get this error after pressing "Sign in": Keyring error: Failed to get credentials - Couldn't access platform secure storage: Secret Service: no result found. This even happens when checking the box next to "Dont use Keyring". Can somebody please help?

minor sky
#

Though as for the keyring error, perhaps it's related to not having something like gnome keyring or

#

im not sure what DE/WM you're using

jagged wharf
#

Im running a minimal Hyprland window manager on Omarchy Linux, which is why the keyring is completely broken.If I use the AUR version: It bypasses the graphic crash by using XWayland, but then it hits a hard wall with the keyring. Because Hyprland doesn't have a desktop session manager, gnome keyring is permanently locked. Every time I try to run it or seed it with secret-tool, it throws Cannot create an item in a locked collection. Even Python's keyring library gets rejected.If I use the AppImage version: It doesn't even get to the keyring step. Because it's an Electron app running on pure Wayland, it instantly crashes at startup with Could not create default EGL display: EGL_BAD_PARAMETER, leaving me with a blank grey screen. If I run it through Gear Lever, the sandbox blocks it from talking to /var/run/usbmuxd, so it says 'No devices found.'Is there a hidden command-line flag or an environment variable I can pass to the official AppImage to force it to completely ignore the system keyring, or a way to run the AppImage natively on Wayland without the EGL crash?

minor sky
jagged wharf
#

Yes that actually got me into the App through the Appimage but i still get this error sadly. Now it is slightly different though

image.png
minor sky
jagged wharf
#

Sadly this doesn’t work. I think it’s because omarchy in and of itself handles the keying system differently.

minor sky
# jagged wharf Sadly this doesn’t work. I think it’s because omarchy in and of itself handles t...

Well if you absolutely cannot get a keyring system then an alternative is to use something like a mix of altserver and an anisette server

Basically:
https://github.com/jkcoxson/idevice_pair (where you get pairing files)
https://github.com/NyaMisty/AltServer-Linux (altserver, where you sideload)
https://github.com/Dadoum/Provision/releases/tag/2.1.0 (anisette server)
Download the binaries corresponding to your arch based on uname -m (I will assume x86_64)

Then in one terminal, run

./anisette-server-x86_64 -n 127.0.0.1 -p 6969

and in another terminal run

export ALTSERVER_ANISETTE_SERVER=http://127.0.0.1:6969

# replace UDID, Email, Password with the correct fields. Also this assumes SideStore.ipa is in the same directory as CWD
./AltServer-x86_64 -u "UDID" -a "Email" -p "Password" SideStore.ipa

You can find the udid through usbmuxd logs, or sudo dmesg or recent journalctl logs

For dmesg it should be something like

[22090.143633] usb 1-2: Product: iPhone
[22090.143635] usb 1-2: Manufacturer: Apple Inc.
[22090.143637] usb 1-2: SerialNumber: [UDID HERE]

or for usbmuxd, when doing systemctl status usbmuxd, you should see something like this:

usbmuxd[1220834]: [19:31:44.794][3] Connected to v2.0 device 1 on location 0x10007 with serial number [UDID HERE]

I recommend the usbmuxd approach as it does properly add the hyphen - to the correct place.

#

Then after installing SideStore, you can use idevice pair to place the pairing file in SideStore

jagged wharf
#

~/sidestore-tools ❯ ./anisette-server-x86_64 -n 127.0.0.1 -p 6969
object.Exception@../../../.dub/packages/requests-2.0.9/requests/source/requests/ssl_adapter.d(197): loading openssl: unknown version for init

#

This is a weird error i get while trying to run ./anisette-server-x86_64 -n 127.0.0.1 -p 6969.

minor sky