Windows app shuts down

[Percussive8]

Description

Windows app shuts down instantly when connected to the phone. It can only stay open if I exit the phone app.
Tried reinstalling, but the same issue occurred.

Steps To Reproduce

1. Paired device successfully
2. The app opens up and closes immediately

Windows Version

Version 10.0.26100 Build 26100

Android Version

Android 15

Android Device

Vivo X90 Pro

Other details

No response

Log File

Sefirah.zip

[shrimqy]

There seems to be an issue with my logging configuration and that zip doesn't have any logs at all, could you try the following package instead?

https://drive.google.com/file/d/1hL4w6EIiwr0Utsn7X7yw79YiUIpdn03E/view?usp=sharing

Instructions for installing with the zip file:

Extract everything
Right-click on the Install.ps1
Click "Run with Powershell"

Hopefully, it fixes the logs not being recorded and could you also try to connect without giving the Android app permission for storage? That may or may not resolve your issue.

[Maffia171]

Hi @shrimqy, just wanted to add onto this since I'm experiencing the same thing.
Windows 11 23H2 (version 10.0.22631.4890) - Galaxy S22 Ultra (Android Version 14).
I can confirm that it seems to work fine when I disable the 'Storage access' permission.

I attached my log file where the initial setup with 'Storage access' disabled went fine. After that I closed Sefirah, enabled the storage permission and started it again, the result of that is at the end of the log file.

Log20250216.log

[shrimqy]

I see thanks for reporting, @Maffia171 could you check the log folder again, this seems to be the logs from when you had the storage access disabled or maybe it didn't catch the error? but highly unlikely.

[Maffia171]

The end of the log was with storage access enabled so it doesn't seem to show a specific error. Here I have some new logs from a fresh install where I enabled storage access during the setup process.

Log20250216 - 2.log

After it connected, the Windows app crashed without an error. I then tried starting the Windows app two more times to trigger the crash again but this is all that the log shows.

[Percussive8]

Turning off Storage permission worked, but it turned itself back on for unknown reasons when it connected.
However, I cannot find the log file after installing the update. Or I just don't what I'm supposed to look into.

[shrimqy]

Turning off Storage permission worked, but it turned itself back on for unknown reasons when it connected.

Yea that preference setting is buggy, just remove the permission for the app altogether which should work for now.

However, I cannot find the log file after installing the update. Or I just don't what I'm supposed to look into.

Try to reproduce the crash like before and the log file (log[date].txt) should be present in the following path(though it won't give me much info if it is the same issue as @Maffia171):

C:\Users\{user profile name}\AppData\Local\Packages\shrimqy.Seki-PhoneLink_fbe9dzh3mzsqw\LocalState\

After it connected, the Windows app crashed without an error. I then tried starting the Windows app two more times to trigger the crash again but this is all that the log shows.

The logs didn't have much info other than the fact that it was caused by registering the sync root (Android drive).

If it won't be too much trouble try this package @Maffia171 :

https://drive.google.com/file/d/11phjJBQnbKe5OGnD_8kZx8r-P411r4vA/view?usp=sharing

Which should help me narrow it down more. Thanks.

[Maffia171]

Uninstalled the old version and installed your new package but as far as I can tell it doesn't seem to log anything new:

Log20250217.log

[shrimqy]

All right that is unfortunate, can you check if "RemoteDevice" folder was created in your user directory? If not change the remote storage location and try again, though that is also unlikely.
C:\Users\{User}\RemoteDevice
And also could you clarify if the Windows is indeed Windows 11 23H2 (version 10.0.22631.4890), there was an issue with AtlasOS as well and maybe debloating software may also cause a problem with registering. I will try to reproduce the issue on my end in a VM perhaps.

[Maffia171]

The 'RemoteDevice' folder does get created before Sefirah crashes. Double checked this by deleting the 'RemoteDevice' folder and starting Sefirah again, and the folder always gets created.

To confirm, this is the Windows 11 version I'm running, which is 10.0.22631.4890:

[shrimqy]

Ok, thanks, I will let you know if there is a fix.

[shrimqy]

Update to this issue: I have checked with multiple desktops with the same version, and it registered the sync root without a crash. I presume this could just be a Windows bug, try running the following in the cmd and see if it works:

dism /online /cleanup-image /restorehealth

sfc /scannow

[Maffia171]

Unfortunately that didn't do anything for me, which is what I was kind of expecting since this is a relatively fresh Windows install on a new SSD. I understand that there's not a lot to do if you can't reproduce it so for now I'll just leave the 'Storage access' permission disabled, thanks for looking into it though. Perhaps the original reporter has some different finding to share.

[shrimqy]

All right, I will try to figure out why my debugger ain't working for the time being. I'm sorry for the trouble and thanks for all the feedback.