Known Issues on Android 9

[Martin]

This posts lists the currently known issues on Android P. Please note that the list is not complete. Please let me know if you should know of any other issue on Android P. You can send issue reports either as a reply to this post or send a mail to info@automagic4android.com.

• [Workaround in v1.36.0_01]Time triggers are sometimes executed early by a few seconds which causes the trigger to execute a second time shortly afterwards. This is a known issue on Android 9: https://issuetracker.google.com/issues/117577886.
• [Fixed in v1.36] WiFi Connected/disconnected triggers don't work anymore since Android P removed the SSID information in some used APIs for security reasons.
• [Fixed in v1.36] The ringing state of trigger Incoming Call does not set the variable incoming_number anymore. This is a reported bug of Android P.
• Workaround by installing Workarounds for Automagic action Set WiFi Tethering State without root does not work anymore with version 1.37 since Google enforces new limitations for apps targeting Android 8+. A workaround for some devices will be provided soon.
• Location can not be acquired: Can not reproduce. Please ensure location mode of the device is turned on and location permissions have been granted to Automagic.
• Phone cell information is not available anymore: Can only reproduce when location permission is missing. Please ensure location mode of the device is turned on and location permissions have been granted to Automagic.
• The proximity sensor does not work on the Samsung S10 (seems that all apps are affected). The sensor always shows value 5.0 even when covered. No workaround known.

Thanks & Regards,
Martin

[Wibbly]

Do WiFi connect/disconnected conditions still work, currently?

[Martin]

In my tests on P the conditions still work and the triggers will also work again in the first EAP version of 1.36 of Automagic.

Regards,
Martin

[Serum_114]

Active network type trigger makes for a seemless work-around.

[gollyzila]

My phone is only intermittently recognizing my NFC tag. Toggling NFC off and on makes it work for one scan. I'm not sure if this is an Automagic or Pie bug.

[Serum_114]

I also experience the NFC issue. I can only make one successful scan and then I need to toggle NFC off and on to allow another successful scan. Also unsure if this is a Pie or Automagic issue. (Pixel 1, Android 9)

[digitalstone]

Why not trying to scan an NFC-tag within another app than Automagic, and then check if the problem persists?
If so, it's not Automagic.
Also, you could create an NFC-flow with in there an NFC-checkloop to see if it's on:
If it's on then: go on
If it's off then: turn NFC on.
...

You could also create a timer around it to determine how long NFC should be activated.

[Serum_114]

Thank you for the suggestion. Automagic reads any NFC tag. Other apps read NFC made specifically for them. I have no NFC tags made for a specific app. My device is not rooted. NFC cannot be toggled without root.

[Serum_114]

I use Sleep as Android to track sleep. It has Tasker integration. Automagic is not receiving the start and stop messages via the Tasker integration since I moved to Pie. This is my only use of Tasker integration.

[Serum_114]

Incoming call trigger provides "null" for all variables on Pie.