How can I eliminate keyguard after phone wakes?

[Econdoc]

My Moto G4 is running Nougat. When the phone is in a “Trusted Place,” it does not lock, but the keyguard must still be dismissed with a swipe when the phone is woken. (If the phone is not in a Trusted Place, the phone needs a pattern unlock. )
I have tried “Dismiss Slide to Unlock Keyguard” when the phone wakes (trigger: User Present), but it will not respond. Apparently, the flow that contains “Dismiss Slide to Unlock Keyguard” cannot be accessed when the phone is “locked.” To my mind, the phone is NOT locked under these conditions; the keyguard is operative, but the screen is not locked.

Is there a way to fix this?

[Desmanto]

Trigger User Present only triggered when the phone is turn on and "Unlocked" (pass thru the lockguard). If you want to trigger when the phone is turned on only, you should use Trigger Display State : On. Probably you should put sleep several seconds before trying the Dismiss Slide. At mine, no sleep is needed, as soon as the display on, dismiss slide directly works, even though we can see some delay.

The other way is to disable the keyguard and enable it back before lock the device. viewtopic.php?f=5&t=6856
Swipe to unlock is considered as one the keyguard, except it doesn't have any security. So the screen is still locked, but doesn't have any security pattern to unlock it.

[Econdoc]

Thanks for the directions. I tried the Trigger: Display on, with Dismiss Slide...but I could not get this to work. Strange behavior ensued! The initial keyguard screen has three icons on the bottom: Microphone Icon, Unlocked Icon, Camera Icon. That keyguard screen goes away, but it is immediately replaced with another screen with only the Unlocked icon at the bottom. It takes a swipe to get rid of that second screen. I tried using Dismiss Slide...twice, after a few seconds delay in between. Could not get it work. Any ideas, Professor?

[Desmanto]

It seems you have another app creating that lockscreen. Automagic can't interact with the lockscreen created by 3rd party.

Which one is the usual lockscreen that supposed to be? I think the first one is the real one, the second comes from 3rd party app. Try to disable the whole keyguard, set to none and see if the "another lockscreen" is still there. This "another lockscreen" must come from the app which have device administrator access too, try to check with setting - security - device administrator. Make sure it is only automagic and other app that you really need. Some bloated apps has gone too far and requesting device admin which are not supposed to be granted to them.

[Econdoc]

There was one other app with device administrator access. I removed the privilege for that app and tried again. Still did not work and still got two Keyguard screens. Oh well. I guess I will have to live with it.
Thanks for your help.

[Desmanto]

For this kind of problem, I won't deal with it. It can be a potential Unwanted app, spying you in the background. There are also another possibility it will interfere with automagic in some other way.

When did it start to appear? Most likely it comes from the app you have installed just before it started to appear. You can install MiXplorer from xda, open the app manager, sort the app based on date - descending. Try to remember the date it started to appear and make an educated guess at the culprit. The culprit must have permission/feature to set lock screen.

I don't know if it will detect it, but you can try my Windows Recognizer flow. It will detect all package name and class name of the current opened windows and maybe the "another lockscreen" too.