Pie: Call Incoming returns null phone number

1,489 views
Skip to first unread message

Fran T

unread,
Aug 19, 2018, 12:59:10 AM8/19/18
to Automate
Since upgrading my Verizon Pixel 2 XL to Android Pie, the Call Incoming block has begun to return null for the 'Caller phone number' output field. I don't know if it's related, but I have the Caller ID and Spam filter features enabled in the Android dialer app. The block's Subscription ID option is unspecified.

Missed a few calls when a flow I'm running thought everyone was an unknown caller! :-)

Henrik "The Developer" Lindqvist

unread,
Aug 19, 2018, 5:10:17 AM8/19/18
to Automate
Try granting the "read call log" privilege.

Fran T

unread,
Aug 19, 2018, 10:18:58 AM8/19/18
to Automate
Thanks for your reply!

That permission is already granted.

Henrik "The Developer" Lindqvist

unread,
Aug 19, 2018, 3:11:20 PM8/19/18
to Automate

Fran T

unread,
Aug 19, 2018, 3:17:32 PM8/19/18
to Automate
Thanks!

Saw this just above the part of the article you linked to; maybe the trouble is related to them moving the permission to a new group?

Restricted access to call logs

Android 9 introduces the CALL_LOG permission group and moves the READ_CALL_LOG, WRITE_CALL_LOG, and PROCESS_OUTGOING_CALLS permissions into this group. In previous versions of Android, these permissions were located in the PHONE permission group.

Henrik "The Developer" Lindqvist

unread,
Aug 19, 2018, 8:45:56 PM8/19/18
to Automate

Fran T

unread,
Aug 19, 2018, 10:57:40 PM8/19/18
to Automate
Ick, it looks like there's no way back yet without adding a 100ms delay to be able to tell the difference between the new duplicate event and a private caller. Hopefully they'll get rid of the useless and confusing second broadcast in a future release.

Thank you again for your heroic support of Automate across all these devices and OS versions!

Fran T

unread,
Sep 6, 2018, 11:34:38 PM9/6/18
to Automate
Alpha version 14 of Automate resolved this problem.  Thanks!
Reply all
Reply to author
Forward
0 new messages