Auto clicker stops by itself & not remembering last position

[pnkpp2]

Version of Smart AutoClicker

3.0.0

Device brand and model

MuMu Android Emulator

Version of your Android OS

12

Type

Smart scenario

Describe what happened?

Before updating everything is working fine, then after updating to the latest version 3.0.0 the clicker just randomly stop (never happened before) and the last known position is not saved and always on center of the screen.

Describe what should have happened?

Before updating everything is working fine, then after updating to the latest version 3.0.0 the clicker just randomly stop (never happened before) and the last known position is not saved and always on center of the screen.

[pnkpp2]

I just found the problem on clicker randomly stop now it clicks on top of the clicker app unlike before it clicks under it, so when you have programmed it to click something on the position it will click the app too when it is position there. Hope developer will fix it soon, thank you. Still, the last known position is not saved.

[AlmightyCZ]

I've also noticed that it takes way longer to load list of automations, when I enter the app (from app drawer or through notification).

[Nain57]

Hi and thank you for your feedback.

This happen when:

• App has crashed
• App has been killed by your device

I have litterally 0 crashes on 3.0.x during a detection (crashlytics is enabled on PlayStore version, 17K monthly users), so if your have installed it from the PlayStore, your emulator is most likely killing Klick'r.

If you have installed it from GitHub/F-Droid (any other installation/download source is not from me and probably modified, bugged and rigged with spywares), I will not receive a crash report even if that's the cause of your issue. If you think you are in this case, you can either capture the stacktrace in the logs during the crash and paste it here (easy if you are a dev), or reproduce the crash with the 3.0.2 PlayStore version in order for me to receive the stacktrace automatically.

@AlmightyCZ Please keep the focus on this bug. If you encounter another unrelated issue, open another ticket

[AlmightyCZ]

Sorry for the off topic. I'll file another bug ticket as soon as I'll find some time.
However I'm having the issue with not remembering location of the control panel, as well. It happens when I start the app (after choosing macro) or after rotating the screen while the panel is showing - the panel always returns to the center. There are no crashes of the app and except for the huge delay, I'll file another ticket for, it's working fine as before. It started happening after updating the app from 2.4.2 to 3.0.2 and I'm running playstore version on the regular Samsung S23. (A14)

[AlmightyCZ]

Small update.
I exported all the macros and did full reinstall with import. The delay is gone, so probably some kind of glitch in the db. So I'm not gonna make a ticket for this issue. However if you are interested I could send you the exported macros (I have exports from both versions).

The screen position issue still remains the same as I described in last comment.

[Nain57]

I'm trying to reproduce the problem but without success. If anybody can provide a video capture of the bug, this would really help me to understand how to reproduce it.

One small question: have you disabled the animations in the Developer Options of your phone ? UI issues have been reported with this setting

[AlmightyCZ]

My developer options are enabled, but only for USB debugging. Animations, activity and process persistence is on default settings.

Here's video for screen rotation

And here I had to use another phone because of screen capture access to capture regular usecases of launching for the first time and then switching selected macro through notification.

video

[pnkpp2]

Hi and thank you for your feedback.

This happen when:

* App has crashed

* App has been killed by your device

I have litterally 0 crashes on 3.0.x during a detection (crashlytics is enabled on PlayStore version, 17K monthly users), so if your have installed it from the PlayStore, your emulator is most likely killing Klick'r.

If you have installed it from GitHub/F-Droid (any other installation/download source is not from me and probably modified, bugged and rigged with spywares), I will not receive a crash report even if that's the cause of your issue. If you think you are in this case, you can either capture the stacktrace in the logs during the crash and paste it here (easy if you are a dev), or reproduce the crash with the 3.0.2 PlayStore version in order for me to receive the stacktrace automatically.

@AlmightyCZ Please keep the focus on this bug. If you encounter another unrelated issue, open another ticket

For me, it didn't crash the app, the only problem is the position of the UI is always on default (center screen) it didn't save the last known position it is always in the center and the app now clicks on top of the UI so it also clicks the UI when it is position on the setting you apply it. Sorry I can't describe it better.

[AlmightyCZ]

I have new observation, if I don't position the panel exactly at the edge of the screen as I'm used to and leave a few pixel margin the position is remembered for the cases with no orientation change. When I rotate the screen first the position is reseted to the center, however if I also reposition the panel with some "air" between screen edges the position is also remembered for this new orientation.

Screenshot of working position (sorry for the light background of the chosen app, but it's visible if you navigate to the image itself from github)

(the detail of the margin)