Is READ_CALL_LOG permission needed when using selfManagedMode?

[aguedob]

Google play store is rejecting me my app because I haven't requested READ_CALL_LOG permission. Is it required when using selfManagedMode? Calls are not currently registered anymore in the calls log.

[MusabBasheer]

These permissions are required as per: https://developer.android.com/guide/topics/connectivity/telecom/selfManaged#manifest

[namnm]

In our case, Google Play rejected us I guess because of we have READ_CALL_LOG permission.

The error message is like:

Unable to verify core functionality of app
When you submitted your app, you specified your app's core functionality as follows: Default Phone handler (and any other core functionality usage while default handler). However, we couldn’t find evidence that the app offers the declared core functionality during our review. Please submit an updated Permissions Declaration Form that includes instructions on how to verify your declared functionality, and include details such as test account information. If portions of your app are restricted, please share a link to a video of your app to help us verify the core functionalities you’ve declared.

No default handler capability
Default handler capability for Default Phone handler (and any other core functionality usage while default handler) was listed on your declaration form, but your app does not appear to have default handler capability. Please submit a revised Permissions Declaration Form and/or add default handler capability to your app.

As I do more research, people say that this issue related to restricted permission listed here: https://support.google.com/googleplay/android-developer/answer/9888170

Im trying to remove this permission and see if it's working.

Any idea?

[MateWW]

@namnm Is it working for you after remove that permission?

[namnm]

@MateWW I have been testing it, so far no issue. After remove it, the app is approved on Play Store!

[aguedob]

@namnm Is it working for you after remove that permission?

Same here. No problems so far once removed, at least using self-managed mode. Works perfectly.

[manuquentin]

Thanks everyone.
I'm closing as the issues is resolved.

[namnm]

Why is this resolved? We need to manually remove READ_CALL_LOG from the code using our custom fork.

[manuquentin]

It seem's that the Android doc requires to add READ_CALL_LOG to use self managed but Google is rejecting app with this permission.
@jonastelzio what do you think ? Should we use additionalPermissions to let everyone add READ_CALL_LOG instead of hardcoding it ?

[jonastelzio]

@jonastelzio what do you think ? Should we use additionalPermissions to let everyone add READ_CALL_LOG instead of hardcoding it ?

Yeah I'm all for removing it. As far as I know (?) if needed it could be added to the implementing apps manifest?

Now additionalPermissions is completely bypassed in self managed mode I believe, but can't the implementing app just request that permission if need be?

[manuquentin]

+1 for removing it.

[agam-colaburate]

When are we going forward with removing this as we have to manually remove this.
Got my rejection today.

[se1exin]

For those that are getting rejected due to the permission (as my app did), adding the following to your AndroidManifest.xml removes the permission without needing to fork the repo or otherwise:

 <uses-permission android:name="android.permission.READ_CALL_LOG" tools:node="remove" />

I think this should be added to the project readme, perhaps even as an 'upgrading from version < 4.2?` warning, as my rejection was after I updated my dependencies and had no idea this new permission was added to my manifest.

[namnm]

@se1exin Very helpful solution. We are just js junky and have no idea about those android things. Thanks for the info.