chaoscreater
Active member
Hi there,
I've noticed that the Launch application action is rather inconsistent, depending on the app that you launch. For example:
- if my phone's screen is on and unlocked and I test launch application with Spotify, it'll launch in the foreground and works fine.
- if I set my macro to wait 1 second and then launch application with Spotify and I turn off my phone screen as soon as the macro is run, then Spotify will launch in the background. If I unlock my phone, I can see Spotify already as my foreground app and ready to go.
However:
- if my phone's screen is on and unlocked and I test launch application with DesktopSMS, it'll launch in the foreground and works fine.
- if I set my macro to wait 1 second and then launch application with DesktopSMS and I turn off my phone screen as soon as the macro is run, then when I unlock my phone, I don't see the app. It's not launched.
Any ideas why this is the case?
I've noticed that the Launch application action is rather inconsistent, depending on the app that you launch. For example:
- if my phone's screen is on and unlocked and I test launch application with Spotify, it'll launch in the foreground and works fine.
- if I set my macro to wait 1 second and then launch application with Spotify and I turn off my phone screen as soon as the macro is run, then Spotify will launch in the background. If I unlock my phone, I can see Spotify already as my foreground app and ready to go.
However:
- if my phone's screen is on and unlocked and I test launch application with DesktopSMS, it'll launch in the foreground and works fine.
- if I set my macro to wait 1 second and then launch application with DesktopSMS and I turn off my phone screen as soon as the macro is run, then when I unlock my phone, I don't see the app. It's not launched.
Any ideas why this is the case?