Automagic to remove SMS and Call log features in update

[Martin]

Hi,

Google asks developers to remove SMS and call log features from apps by the 9th of January. Automagic will likely have to comply if Google does not grant Automagic an exception:
https://support.google.com/googleplay/a ... er/9047303
https://android-developers.googleblog.c ... ience.html
https://www.xda-developers.com/google-r ... rmissions/

It looks like Google did not grant Tasker an exception so Google will likely not grant the exception to Automagic either:
https://groups.google.com/forum/#!topic ... ZcHqV23ibY

Please star the following issue to let Google know that you are interested that Automation apps should be eligible for an exception:
https://issuetracker.google.com/issues/117486314

Affected features in Automagic (Android 9 requires the call log permission to access the phone number for incoming/outgoing phone calls):
- trigger Incoming Call (Android 9+ will not have access to the number anymore)
- trigger Outgoing Call (Android 9+ will not have access to the number anymore)
- trigger SMS Received
- trigger SMS Sent
- trigger Automagic SMS Delivery Status Report
- action Init Variables Call Log
- action Modify Call Log
- action Send SMS
- action Query Content Provider (when it's used to read call log and SMS content providers)

I'll update this topic as soon as I have more information to share.

Update 2018-11-13: According to Google Automagic "does not qualify for use of the requested permissions" so it seems that Automagic will have to remove the features or build workarounds (if possible at all).

Thanks & Regards,
Martin

[beelze]

Those threads are almost Tasker-only related. Well, the whole idea to not let Google ruin Tasker is good, but what about AM? Did we need a separate issue for AM?

[Martin]

The linked issue is quite general and I think it's better to collect all comments in this one issue. Adding a star might also help:
https://issuetracker.google.com/issues/117486314

It seems that Google does not even grant an exception to apps whose main feature is to send SMS or handle call logs so either Google rethinks it's position on this issue entirely and adds automation apps as a valid exception or all hope is lost

[Desmanto]

Such a terrible move from google. Last year it is accessibility, this year is call/sms. Android is slowly turning to fruit.

I have starred and commented in that thread. Let the outrage reach out far. Although that is mostly tasker user, I should say that we say support other app too (Automagic is included). If the devs don't worked together, it won't be strong enough.

[digitalstone]

Adding a star might also help:
https://issuetracker.google.com/issues/117486314

I don't see any option to add a "star" anywhere. Where/how can I do that.. and would it actually help (even if only a bit).

Google is turning soft and going downhill bit by bit

[skiptannen]

According to Android Police, Google has denied Tasker's exception request:

https://www.androidpolice.com/2018/11/1 ... y-changes/

[beelze]

I don't see any option to add a "star" anywhere

It's to the left of Issue ID.

[Martin]

Sad news. According to Google Automagic "does not qualify for use of the requested permissions".
This was to be expected but I'm frustrated anyway. Let's wait and see if Google changes its mind in the next few days. Maybe they will respond in the linked issue.

[beelze]

Can those new restrictions be overridden on rooted device?

[moonspeak]

Sad news. According to Google Automagic "does not qualify for use of the requested permissions".
This was to be expected but I'm frustrated anyway. Let's wait and see if Google changes its mind in the next few days. Maybe they will respond in the linked issue.

Do you think it would be a viable workaround to make a companion app whose only "core functionality" is to read and send SMS and extend that to AM? Maybe it could be a locale plugin.

Also, would it be possible to circumvent the need for the permission by root? Would be a valuable option for root users.