axel358 / smartdock

A user-friendly desktop mode launcher that offers a modern and customizable user interface
GNU General Public License v3.0
708 stars 51 forks source link

Settings SmartDock as default launcher causes the current launcher to crash #63

Closed JUDE122-MAX closed 11 months ago

JUDE122-MAX commented 1 year ago

Anytime I want to set the app as my default launcher it crashes. Note mg Phone is not rooted and I use gesture navigation (android 12)

axel358 commented 1 year ago

Device brand?

Kabouik commented 1 year ago

Not sure if related, but on my end, Smartdock was crashing after I granted it permissions to show notifications, but hadn't figured out how to grant it the "Accessibility service" permissions. I had to clear the application storage (long tap on the Smartdock icon) to grant those permissions together, or at least remove the notifications permission if the other one was not granted, in order to make Smartdock run normally.

I am using a F(x)tec Pro1, running Droidian, and Waydroid with lineage_waydroid_arm64_userdebug 11 RQ3A.211001.001 48 test-keys.

axel358 commented 1 year ago

@Kabouik There is a reason why those permissions are in that particular order

Kabouik commented 1 year ago

Yup, I just couldn't figure out how to grant the Accessibility ones so I enabled all I could first, and then noticed that issue. Not complaining about it, just mentioning in case the OP would be in the same situation.

On 2023-07-25 12:24 Axel @.***> wrote:

@Kabouik There is a reason why those permissions are in that particular order

--
Reply to this email directly or view it on GitHub: https://github.com/axel358/smartdock/issues/63#issuecomment-1649551635

You are receiving this because you were mentioned.

Message ID: @.***>

axel358 commented 1 year ago

This might have been fixed here, please give it a try https://github.com/axel358/smartdock/suites/15163236007/artifacts/866497365

axel358 commented 11 months ago

Closing this as completed since im not able to reproduce it and there has not been any feedback from @JUDE122-MAX. Feel free to reopen it if the issue still persists