An error occurred while fetching shortcuts! (User 100 is locked or not running)

[Qutition]

Describe the bug
After restarting my phone this randomly start appearing, even if I do command reset or exit (I have it as default launcher)

To Reproduce
Steps to reproduce the behavior:

1. Restart your phone (hard restart)
2. Boot up

Expected behavior
My phone frozen, cause it had low percent (it's starting to glitch and freeze alot) I done a hard restart and I expected it to work normally, idk...

Smartphone (please complete the following information):

• Device: [Honor x9b 5G 256Gb]
• OS: [MagicOS 8.0 (Android 14)]
• Version [9.7]

Additional context
Maybe that's not it, but when I do command list shortcuts it shows them.

• I will send screenshots rn, please wait

[Qutition]

SVID_20240903_081708_1.mp4

Its very long and vibrates when restarting/starting

[Qutition]

SVID_20240903_081822_1.mp4

[coderGtm]

Do you have Secure Folder on your device?

[Qutition]

What's is that?

[Qutition]

@coderGtm oh I have a thing called parallel space, its like a secury space for apps and files, and when I unlocking it, but clicking to not fully shutdown the system its not giving the error! And apps in parrele space have PKG names and (work) after it

[Qutition]

I will upload later

[coderGtm]

I did not exactly understand the behaviour. When does the issue occur and when not?

[Qutition]

I https://github.com/user-attachments/assets/e2bda602-baf3-4a6d-b300-7909754ecf96

@coderGtm

[Qutition]

I'm just kinda busy rn so I typing fast, and I'm also not english. So my messages very delayed

[Qutition]

and the autocorrect is sucks

[coderGtm]

Okay got it.

This is like secure folder is samsung. I can't reproduce this issue as I don't have the test device but you can suggest a fix for it and we can code it!

[axolotl-git]

coderGtm I have a Samsung device (a galaxy J6), I can test it , but uh I think that solving the problem is not easy at all as I don't think there is much documentation

[coderGtm]

Do you get this error?

[axolotl-git]

No, I have never had this error and I just did the test, but I have never activated the Samsung secure folder function, so I deduce that if it is deactivated it is not bugged. Give me a moment and I'll try to activate the secure folder and try to reproduce the bug