IssueTracker

Thanks for filing the bug. I've examined the apk/bundle that you've uploaded, and I could not find any obvious reason why this issue might be happening. Because you are able to reliably reproduce the issue, can you please capture and upload a bug report (https://developer.android.com/studio/debug/bug-report)? This should contain more information why the error occurs.

I put the bug report on the same gdrive folder I shared. Let me know if you can't access it or if I captured it wrong.

Here is the bug report shared by the reporter:

https://drive.google.com/a/google.com/file/d/1n6mDNfeDLudtbGzeceCa5JlM2AP21Ij5/view?usp=drive_web (bugreport.txt)

Todd, can you please have a look. There is a ResourceManager error log before the exception occurs.

Might be related: https://issuetracker.google.com/119839527

Here is a link straight to the bug report, can't remember if the other share was only for an specific email.

https://drive.google.com/file/d/1Z6TQhPkIjeBnLKTpGsTUa5QuGReKoCru/view?usp=sharing

From issue marked duplicate: https://issuetracker.google.com/issues/119839527
================================
Steps to reproduce the problem:
    Send push notification

What happened:
     App crashed. Based on crashes received from Fabric.

Mostly happens on:
  - OnePlus One device with Android 6.0.1 (99% OnePlus but also appeared on LGE, Samsung, Xiaomi and others)
  - Various Samsung devices with Android 7.0
  - Galaxy Tab /Tab 3 devices with Android 4.4.4

Crash:
Fatal Exception: android.app.RemoteServiceException: Bad notification posted from package com.xx.yy: Couldn't expand RemoteViews for: StatusBarNotification(pkg=com.xx.yy user=UserHandle{0} id=753962216 tag=null score=10 key=0|com.xx.yy|753962216|null|10117: Notification(pri=1 contentView=com.xx.yy/0x7f0a006f vibrate=null sound=null defaults=0x4 flags=0x11 color=0x00000000 vis=PRIVATE))

XML files of content view and big content view are attached.
All the images are in PNG format (hdpi,xhdpi,xxhdpi).

==============================================
Unfortunately, I didn't succeed to reproduce the issue even on OnePlus One device.

push a message to old version app
upgrade the new app from google play store
click the message push to the device before
app crash

I tried to reproduce the issue by following the steps above but without success.
After the app is updated notifications are disappeared, so I couldn't click on the notification.

All I have it is Fabric crash reports (Attached).
As you can see it is a lot of exception.
===============================================
Question about the similar issue on StackOverflow: https://stackoverflow.com/questions/53162489/bad-notification-exception-only-under-android-6-0-1

Any conclusions from the bug report? (https://drive.google.com/file/d/1Z6TQhPkIjeBnLKTpGsTUa5QuGReKoCru/view?usp=sharing)

I'm curious #8, are you using bundles or apk? Switching to apk seems to solve the issue for me.

I'm using a bundle and unfortunately switching to apk is not an option for me.

this code has changed significantly from marshmallow

Sorry, are you saying we just can't use bundles with notifications with marshmallow?

If it doesn't crash for an APK, it shouldn't crash for an Android App Bundle.

I suspect what happens here is that some people have sideloaded the app, but have only installed the base APK and not any of the config split APKs, hence some resources are missing at runtime.
To confirm this theory, you could try installing only the "base-master.apk" (you could download from the Bundle Explorer in the Play Console) and try triggering a notification.

We are aware that incorrectly sideloaded apps can cause crashes with the App Bundle. We are working on a solution to mitigate this issue. If you can confirm that this issue is indeed caused by the missing config split APKs, then I'll update this thread when our solution is available.

I don't think this is correct because of two reasons.

1.- I can reproduce it myself by creating a bundle, signing it and installing it using bundletool.  I bought one of the phones it happens with (one plus one) specifically for this reason.

2.- When I release a bundle build as beta, within a few hours I start getting crash reports for it. Seems highly unlikely that within a few hours of a new beta someone would already be extracting the apk and causing this issue.

I tried the base-master.apk trick and interestingly enough that allowed me to replicate another issue I've had recently with just a handful of phones. They will crash while loading my splash activity. The splash activity doesn't have a layout, it just has a drawable on the theme background. The drawable is a bitmap. It is a normal drawable, just an image, not a vector, not drawable xml. Using bundletool to install the same bundle that I got the base-master.apk out of works just fine until the notification crash.

11-28 16:18:47.179 21964-21964/? E/AndroidRuntime: FATAL EXCEPTION: main
    Process: mypacakge, PID: 21964
    Theme: themes:{default=overlay:com.cyngn.hexo, iconPack:com.cyngn.hexo, fontPkg:com.cyngn.hexo, com.android.systemui=overlay:com.cyngn.hexo, com.android.systemui.navbar=overlay:com.cyngn.hexo}
    java.lang.RuntimeException: Unable to start activity ComponentInfo{mypacakge/mypacakge.SplashActivity}: android.content.res.Resources$NotFoundException: Resource ID #0x7f0802e3
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2450)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2510)
        at android.app.ActivityThread.-wrap11(ActivityThread.java)
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1363)
        at android.os.Handler.dispatchMessage(Handler.java:102)
        at android.os.Looper.loop(Looper.java:148)
        at android.app.ActivityThread.main(ActivityThread.java:5461)
        at java.lang.reflect.Method.invoke(Native Method)
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
     Caused by: android.content.res.Resources$NotFoundException: Resource ID #0x7f0802e3
        at android.content.res.Resources.getValue(Resources.java:1432)
        at android.content.res.Resources.getValue(Resources.java:1412)
        at android.support.v7.widget.AppCompatDrawableManager.loadDrawableFromDelegates(AppCompatDrawableManager.java:331)
        at android.support.v7.widget.AppCompatDrawableManager.getDrawable(AppCompatDrawableManager.java:198)
        at android.support.v7.widget.TintTypedArray.getDrawableIfKnown(TintTypedArray.java:86)
        at android.support.v7.app.AppCompatDelegateImpl.<init>(AppCompatDelegateImpl.java:260)
        at android.support.v7.app.AppCompatDelegate.create(AppCompatDelegate.java:182)
        at android.support.v7.app.AppCompatActivity.getDelegate(AppCompatActivity.java:520)
        at android.support.v7.app.AppCompatActivity.onCreate(AppCompatActivity.java:71)
        at mypacakge.SplashActivity.onCreate(SplashActivity.java:33)
        at android.app.Activity.performCreate(Activity.java:6251)
        at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1108)
        at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2403)
        at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2510) 
        at android.app.ActivityThread.-wrap11(ActivityThread.java) 
        at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1363) 
        at android.os.Handler.dispatchMessage(Handler.java:102) 
        at android.os.Looper.loop(Looper.java:148) 
        at android.app.ActivityThread.main(ActivityThread.java:5461) 
        at java.lang.reflect.Method.invoke(Native Method) 
        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726) 
        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)

Thank you, that's helpful.
Would you be able to share a Bundle that can reproduce the crash and the APK that works so that I can compare them and try reproducing the issue locally?

Yeah I can share them. Any chance I can email you a gdrive link? Already sent the link to #2, don't know if they can share it with you.

If that's an option, you can upload them on Drive and share them with lecesne@google.com

I sent the link over email and also shared it with the email.

I have installed the app locally on a OnePlus One on M.
It starts correctly on my device.
Do I need to perform any specific action in the app to reproduce the bug?

On my app you would need to cast a video in order to get that notification. To do that (assuming you have a Chromecast available or similar streaming device), open https://www.w3.org/2010/05/video/mediaevents.html on the browser, then play the video and it will ask you to cast it and then it will crash. Has to be on the stock rom of the OnePlus One, I flashed mine to the stock image.

If you don't have the a Chromecast available I can see if I can make a test app to reproduce it or temporarily modify mine to always show the notification.

One more thing, the starting crash only happens if you use the base-master.apk, if you use bundletools to install then the starting crash doesn't happen but the notification crash does.

Figured a way to reproduce the issue. Same deal, bundle crashes, apk doesn't. I'm attaching the bundle, signed apks, and the project.

#22, so what are the steps to reproduce the crash?
1. Taking OnePlus One device with the stock rom.
2. Install apk from bundleapks-testapp.apks?
3. What actions should I do in the app to get the crash?

Thanks

Install the bundle using bundle tool and start the app. Crashes for me right away since the notification starts on onCreate.

Before the stacktrace "Couldn't expand themed RemoteViews", there is a bigger one:

01-04 11:10:17.381  2531  2531 W ResourceType: Failure getting entry for 0x7f060069 (t=5 e=105) (error -75)
01-04 11:10:17.384  2531  2531 E StatusBar: couldn't inflate view for notification com.example.carlos.notificationcrashtest/0x65
01-04 11:10:17.384  2531  2531 E StatusBar: android.view.InflateException: Binary XML file line #9: Binary XML file line #9: Error inflating class android.widget.ImageView
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.inflate(LayoutInflater.java:539)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.inflate(LayoutInflater.java:423)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.widget.RemoteViews.apply(RemoteViews.java:2783)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.systemui.statusbar.BaseStatusBar.inflateViews(BaseStatusBar.java:1397)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.systemui.statusbar.BaseStatusBar.inflateViews(BaseStatusBar.java:1302)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.systemui.statusbar.BaseStatusBar.createNotificationViews(BaseStatusBar.java:1820)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.systemui.statusbar.phone.PhoneStatusBar.addNotification(PhoneStatusBar.java:1693)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.systemui.statusbar.BaseStatusBar$6$2.run(BaseStatusBar.java:516)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.os.Handler.handleCallback(Handler.java:739)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.os.Handler.dispatchMessage(Handler.java:95)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.os.Looper.loop(Looper.java:148)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.app.ActivityThread.main(ActivityThread.java:5461)
01-04 11:10:17.384  2531  2531 E StatusBar:     at java.lang.reflect.Method.invoke(Native Method)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:726)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:616)
01-04 11:10:17.384  2531  2531 E StatusBar: Caused by: android.view.InflateException: Binary XML file line #9: Error inflating class android.widget.ImageView
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.createView(LayoutInflater.java:645)
01-04 11:10:17.384  2531  2531 E StatusBar:     at com.android.internal.policy.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:58)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.onCreateView(LayoutInflater.java:694)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:762)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:704)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.rInflate(LayoutInflater.java:835)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.rInflateChildren(LayoutInflater.java:798)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.inflate(LayoutInflater.java:515)
01-04 11:10:17.384  2531  2531 E StatusBar:     ... 14 more
01-04 11:10:17.384  2531  2531 E StatusBar: Caused by: java.lang.reflect.InvocationTargetException
01-04 11:10:17.384  2531  2531 E StatusBar:     at java.lang.reflect.Constructor.newInstance(Native Method)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.view.LayoutInflater.createView(LayoutInflater.java:619)
01-04 11:10:17.384  2531  2531 E StatusBar:     ... 21 more
01-04 11:10:17.384  2531  2531 E StatusBar: Caused by: android.content.res.Resources$NotFoundException: Unable to find resource ID #0x7f060069
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.content.res.Resources.getResourceName(Resources.java:2329)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.content.res.Resources.loadDrawableForCookie(Resources.java:2697)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.content.res.Resources.loadDrawable(Resources.java:2635)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.content.res.TypedArray.getDrawable(TypedArray.java:870)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.widget.ImageView.<init>(ImageView.java:152)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.widget.ImageView.<init>(ImageView.java:140)
01-04 11:10:17.384  2531  2531 E StatusBar:     at android.widget.ImageView.<init>(ImageView.java:136)
01-04 11:10:17.384  2531  2531 E StatusBar:     ... 23 more

The resource is present however in the base-xxhdpi.apk which is installed on the OnePlus One.

It looks like this version of Cyanogen OS didn't support split APKs.

Do you have a list of devices for which you notice this particular crash?
It would be useful for us so that Play can avoid serving splits to these devices.

--
By the way, thank you very much for helping me reproduce the issue, that was very helpful!

Thank you,

Here is a list that I got from Fabric:

1. http://crashes.to/s/def037f628d

96% OnePlus One device
4% Other devices
ONE A2001
SM-G9006V
Galaxy S5
LG G3
Nexus 5
Redmi Note 3
Mi 4c


2. http://crashes.to/s/0ce8d6ec6b5

Samsung devices:
Galaxy J7(2016)
SM-G950F
SM-J701F
SM-J730F
SM-G610F
SM-G955F
Galaxy Tab A 10.
SM-A520F
SM-J530F
SM-J730GM
SM-A720F
Galaxy A5(2016)
SM-J330F
SM-G570F
SM-J730G
SM-G570Y
SM-G615F
SM-J530Y
SM-J530YM
SM-G610M

OnePlus one 82%

11% Samsung:
Galaxy S3
Galaxy S4
Galaxy S5
Galaxy Tab 2
Galaxy Tab 2 3G

3% Motorola
Moto G4 Play
Moto Z Play

Others:
Wileyfox
HUAWEI
asus


So the fix for this will be on the Play Store, not on Android Studio or bundletool?

For the OnePlus One devices, yes, the fix will be on Play Store.

I still believe that the other issue on the other devices are due to sideloading (unfortunately, they would have the same stacktrace), and we are still working on a solution to mitigate those crashes for those devices.

Any idea when the fix will go out? would love to go back to shipping bundles.

I bought a Moto G4 Play for testing since I have a different crash on that device as well and I can not reproduce the issue with it so you are probably right about side loading, specially considering how low the percentages are for those phones vs the OnePlus One.

The fix was released today but it may take up to 24 hours to propagate to all apps.
Note that it only applies to updates and new installs. This means you may still notice crashes from users having the app currently installed until they get an update or re-install the app.

Thanks, I'll test it on my next beta.

Is bunbletool also going to be fixed so I can test with it?

Bundletool does not have knowledge of specific devices. To test locally, you can manually install the standalone APK (generated for pre-L devices) if your minSdkVersion < 21.

So I released a bundle and for the most part it went well until someone with a  Samsung Galaxy Tab 2 with LineagoOS 13 contacted me. They installed from the play store and have the exact same crash.

So will there be a fix for that Samsung Galaxy Tab 2 issue?

This seems to be an issue with LineageOS.

While that is probably correct, I'm guessing there are other ROMs out there with issues like this and I still have to support those users or suffer through their 1 star reviews, or worse, if I get enough of those users I might see my Play Store Vitals drop and then my ranking will suffer. I guess I just don't know what the permanent solution for this is, I really want to use bundles but these issues keep me from it. I am redoing my notification completely, maybe that will fix it, but I'm guessing this issue could still popup somewhere else.

Let me look into it.

Thanks, I appreciate that.

I have tried with LineageOS 15.1 nightly from Jan 10th, and splits seem to work correctly.

I couldn't find how to download an older version of LineageOS yet.

I was going to test the roms from this page https://www.cyanogenmods.org/lineage-13-rom-download-update-guide-devices-list/ but haven't had time yet. I think those are official but not totally sure.

I don't have enough visibility on how widespread LineageOS 13 is nor how we'd go about downloading such version in an official way to test, and the latest versions of LineageOS seems to have fixed the issue (see #comment42).
If someone from LineageOS team could comment on exactly which devices on L+ don't support splits, then I'd be happy to work something out, but I couldn't find a point of contact either.

Since it's now fixed for OnePlus One devices, I'll mark this bug as fixed.

I think it is safe to close it. I just released a new version with a bundle and while I have had issues with resources not being found, I have found ways to work around them.

Which ways did you find to work around them? More specific, I have the exact same issue as reported in https://issuetracker.google.com/issues/120625421

There were several fixes I had to apply. In some cases I put a png on the drawable folder along with the dpi ones. In other cases like on my splash screen, I had to move to a single png on drawable instead of a vector. I also tried a drawable composed of a background and a bitmap and that also failed. Single png worked best.

None of these solutions are ideal but they minimized the crashes and I'm not sure there is much else that can be done.

Another fix I forgot to mention. After going with bundles and vectors, for a small number of users, some images weren't found when used inside the xml of the layout, but if I set them in code it worked fine. Don't know if this is because I use multidex since most of the errors were on the first activity. It is an ugly solution but at least it stopped the crashes.

ca, thank you so much for sharing your workarounds. Are the real MVP. Our issue is just like yours.
https://issuetracker.google.com/issues/132435772

FYI - Regarding split issues due to the lack of all splits being installed (e.g. sideloading or similar), we are also working on a solution that would be easy to integrate with, which would prevent the crashes from occurring. This is being tested at the moment and will be released in the next month or so.

I just wanted to mention that the new library to check if your app install is missing splits appears to be working well. I first did a test by flagging on fabric all users that had that when the app starts but letting them continue and sure enough, every crash I got for a Resources$NotFoundException had that user marked as missing splits. So I then reimplemented the code like on the sample, to just return on Application onCreate after disableAppIfMissingRequiredSplits() is true and so far (only on beta) not a single crash for a missing resource.

The only thing I don't understand is how users are installing my app with missing splits even at the beta stages.

I also live where call recording is perfectly legal and use ACR to record calls to and from my ex because she constantly lies about our interactions in court. I need ACR to protect myself from false accusations and choose to give the permission to access my contacts willingly. I will continue to use ACR, however it is accessible, because my freedom and my time with my child depend on it.

   It is clear Google has not considered all of the reasons why people may be using call recording apps, or the ramifications of no longer allowing them in the play store.

Android is not just a Google product any more. It affects a way of how other people and company use phones, build businesses, etc. You, Google, must listen to what people say. Stop ignoring requests from your partners, users and fans!

By the look of comments here Android/Google should be getting a clear picture... Not a single person/customer is happy about this decision including my self. I for left Windows and bought an android specially for ACR. But now this makes me regret my decision becus it has not even been a month since I bought my new Android SamsungJ7 Neo... This is really a 10 steps back decision... Same reason why people left Apple in numbers

I'd like to be updated on this issue since I'm using call-log and voice recording on my Android too.
Please find a way that this feature stays open to developers and users of Android.

Banning these permissions from a call recorder is not right. I paid for these features on Google Play Store and now feeling stupid for that..

ACR call log should not be restricted in the way Google is suggesting. As long as users are informed about the way apps utilize phone numbers each user should have the freedom and ability to choose.  I agree that apps should not utilize user information in convert and hidden ways. Google has gone too far with what they are suggesting in this policy update for planned for March. PLEASE peconsider your decision for the ACR app.  Google, please let your user voices be heard!  Thank you, in advance (I hope...) for your reconsideration in this matter.

Google,

You folks need to reevaluate this policy. There are a ton of useful apps that don't fit the cookie cutter you're trying to use here. Your simply forcing lagitamit uses to download apps from non-google sources. Stop this madness and allow some common sense exceptions.

This is ridiculous!!!! I have been a loyal customer of Google and owned nothing but pixels. I use ACR a call recording app in my law enforcement duties. I have even had a judge rule that the recordings are admissible in court. Without the phone number information all new evidence will be unusable. Come on google, get your head out of your ass. If I didn't want it, I wouldn't have agreed to the apps permissions.

Google, single handedly bringing the windows phone back! One policy at a time.

Dear Google, please do not restrict apps from recording access calls: PROCESS_OUTGOING_CALLS and READ_CALL_LOG permissions.

I've always felt free with Android, unlike IOS.
I can not understand this prohibition.

I just switched to an Android about a year ago and have loved the freedom of Google. I might as well switch back to iPhone. This is idiotic. You have no idea how much these call recordings help us. Between the court battle I'm currently fighting and meetings, it has helped more than you apparently will ever understand... I don't think I'll be using Google anymore if you follow through with this.

I have used this platform for years and its disheartening that Google is crippling phone apps in the manner. This decision needs to be reversed! Seriously??? My contacts cant be updated to work with my app but... Google still has full access to them. This is BS!

As long as the individual has voluntarily installed a recording app, they should be allowed to use it for that purpose, with the ability to label calls by phone number.

Is this customer care?
I have a payed varsion of ACR wich doesnt work as it did when I payed for it.
Will Google reimburse affected users?
In my contact with sellers, govermental authorites and some other contacts its essential to be able to have full information and to proof it when there are diffrent opinions on wich information are left and what agreements has been made.

My next phone won't be running Android, if this is where Google is taking it. I need a smartphone, not a curated, restricted children's toy...

This new policy is ridiculous. The whole reason I prefer Android is the openness and configurability of the platform as compared to Apple. It's bad enough you let phone manufacturers and carriers forbid rooting, but now you are playing gatekeeper to decide which apps you think are worthy of permissions that don't require root instead of letting us decide for ourselves? I paid real money for apps through the Play Store (money which you took a cut of!) that will now be useless thanks to your new policy. I am not too stupid to decide which permissions to give apps I use, quit treating me like a 5 year old.

@Google, please review your policy and allow the permission decision to lay with the users.  You have been an open advocate for open source ideas.  This restriction sends the message that you are confirming to "big brother" practices.

Let the public decide for themselves and stay out of it.

shame on you google (for all the difference that ever made)!
at a stroke you've made a well made, massively effective app redundant.
GIVE ACR an exemption from this vexatious decision.

Google should allow me to override restrictions. It's my contact book, I should be able to choose who can access it. Google itself has access to too much data, what a shame.

This effects me and my business. Google should be ashamed of themselves by taking away one of the only reasons I use them.

Please don't harm or restrict apps that use call-log or SMS permissions.  Android needs Google not to restrict permissions previously granted for existing products to flourish and NEW INNOVATIONS to continue.  Thank You.

I am disappointed that Android,  Google,  Samsung or any other entity would prevent the full functioning of legally recording my own phone conversations.

Apps such as ACR provide a good quality app that has assisted me:
1. in being a safer driver by being able to get information from my call at a later time.  Thus not having to pull off the road onto the shoulder to write the details down.

2. In gaining information to substantiate my complaints against ROBO Calls, harassment calls, etc.

Which leads me to believe that any company that restricts this information is doing so in  collaboration with Telemarketing for profit.

Regards,

L. White

Please rethink your upcoming policies regarding call recording apps. Consumers deserve the right to accept or deny app permissions according to their own judgement. I guess Google is the new Apple! What will replace Android for power users?

Exclude ACR from your new policies!

Exclude ACR from your new policies!!!

This is ridiculous. On my phone I need to  track and record calls. Please allow ACR.

This is a very annoying change google, ive been call recording for many years, this has allowed me to record such things as my now passed father. It allows me to be clear about detail that ive be requested to do. My memory is not getting any better as im aging so its invaluable to me. Please reconsider. If not I will have no alternative to seek another platform that support the features I need.

Google, I believe you have stepped over your authority on the apps like ACR, SMS or any other recording app. The ACR app is legal in my state and I believe Google should not be able to restrict my use of these apps as long as they are legal for me to use here.

This is so disappointing the once great google who refused to cooperate with the government on releasing search results of millions of users and garnered the trust of it's users now turns against them! The use of call recording has saved me thousands of dollars! It's legal in most of the states and as they record you is the ONLY proof you have of what was said ...(verbal contract). I finaly upgrade my phone and got a note8 as of now I've stopped all system and playstore update and will not be buying the note10 I realy wanted unless google stops trying to babysit me and stops interfereing with freedom!!!  If google is so concerned with privacy why don't the disable the camera functions and not allow uploads to the internet?

Please allow ACR to continue to access telephone numbers and contacts.

Please don't harm or restrict apps that use call-log or SMS permissions.  Android needs Google not to restrict permissions previously granted for existing products to flourish and NEW INNOVATIONS to continue.  Thank You.

Google you don't seem to be denying your access to our telephone numbers and contacts on any of your apps, why are you doing so to other developers? Play fair.

Si estas opciones las configuraran como opcionales obligatorias para la app y que desde la configuración de aplicaciones únicamente se podría dar ese permiso opcional, lo que obliga al usuario a entrar por su propia cuenta a la configuración y cambiar esa autorización, como es en las notificaciones, esto no generaría un inconveniente innecesario como el que están generando.

Please allow ACR app and NLL to have to contacts and call log. It is an essential part of their app and of my use of my phone.
Figure it out some other way.
Jeff

What's happening? Google, as a long time Google fan since you just had a Google search engine, I have been with you through all the highs and downs. I suggest that you don't go through the same as old Symbian. With Symbian, there was a big mistake, no one would hear what users needed. They did what they thought was right. And what happened to them?
I understand that you need to protect users privacy, however why you do not make exception for legitimate apps? I use acr call recorder from nllapps. First you remove the call recording feature from Android and then this permission even though you are aware that people who use call recording need this feature to mark their recordings. Again, I understand that you think about people's privacy, however I have a difficult time to imagine that having these permissions through android 1 to 9 has ruined peoples lives.
I suggest that you ask android users with polls and other means before you decide to "remove" a feature which breaks their favorite apps instead of just doing so because you think it is right thing to do.
Anyways, recording app is a must for me as the way it is today, with access to phone numbers and contacts. Discussion about being legal or not is not your headache. You don't remove camera app just because it is illegal to take pictures in some places.

If I wanted an iPhone, it would have gone behind the Apple's locat. "There's no need to compete, safety if it does with liability and restriction options, not blocking everything.

Google, please reconsider. ACR it's a very important app to have and this policy will make it barely usable. You said, "Don't be evil" long time ago, remember?

Google's decision to cripple such handy and necessary applications is just beyond my understanding.  But they can still collect data about me...

My new Android running on 8.1 is only 2 days old and has obviously many issues including software and hardware issues also invasion of privacy please update or make necessary changes for I feel I am ready to obtain legal counsel at this point for every one of the 8 devices in the last year has me operating under a Enterprise and in a family as a childHELP PLEASE

ACR and apps like it are critical business tools for those of us that have mobile offices.  Google must allow this app to record both sides of conversation and also the phone number so we can search and replay that particular callers interactions.

I use ACR for call recording, and have for years. I also use a third party SMS app. That you would think breaking this functionality is a good idea doesn't bode well. Apple is finally opening up features and abilities that you have provided for years. To think that you're moving backwards and becoming another Apple is just sad.

I don't like this new policy

We are against this new policy
Please change it

I'm not sure what to say google. You appear to be slowly destroying the useful aspects of your platform. The things that draw users to it.

Instead of removing apps that use these permissions, you need to make it clearer to your end users what it's doing. Maybe have the developers of apps say what they need the permission for, and show that on the app page and when a user installs it. Let us decide what we want.

If I can't use the apps I want because you've decided that for us, what is to keep us from looking at Apple and IOS? Looks like they aren't messing with the functionality of call recorders.

Disclaimer, I don't want to use apple, please stop messing with the permissions or find something that actually works for everyone.

I'm appalled! Disabling call recording app functionality in this way is discriminates against people with disabilities and is unreasonable to everyone.
1. People with brain injuries (concussion, MCI, etc.) that affect episodic memory rely on call recording to keep track of what they have agreed to, appointments, health visit details, instructions from clinicians, etc. These are all perfectly valid uses of the technology. You are handicapping people who are already handicapped, and who purchased their Android phones specifically because the OS enabled this kind of enabling technology. It might even be illegal to disable an assistive device in Ontario or EU; it is certainly a very underhanded move. Unconscienable. Despicable!
2. Everyone has perfectly reasonable use cases for this functionality. An obvious one is dealings with Customer Support, or a service person such as a lawyer or broker. A verbal agreement can constitute a legal contract in England, Canada & the US. There does need to be a record of some sort. Recording the conversation and agreement is the standard way of doing this. In fact all corporations - including their customer service operations - record all calls to ensure understanding of commitments made and received is clear and unambiguous. Why should individuals be the only party to agreements and service calls who are unable to protect their interests by recording the call?

The interference of Google on apps that have been purchased is wrong. This is sms also, an app is attempting to send many text do you want to allow. Yes of course but I have to keep pressing allow! Now call logging, I'm tired of you breaking working stuff by code updates. This is a non sense and can only see it to be self serving. I'd like the choice

Hey Google, please don't remove these permissions (call and SMS) from ACR (and other apps). We realy need it. Why you want think for us? I need it! Why you destroy it? Why you remove any users choise??? Stop it, please!

[image: image.png]

вт, 15 янв. 2019 г. в 14:53, <buganizer-system@google.com>:

As a user, I think it's bad that google are doing this.

Google, please reconsider this for specific call recording apps such as ACR. I have 2 friends who've been in abusive relationships and the recordings provided by ACR have been pivotal in getting them the help and support they've needed. (I'll ask them to post here too). My primary use case has saved me thousands of pounds (when things have been agreed in conference calls, then forgotten by 3rd parties), saved me from embarrassing myself when I've forgotten things too, and is great when I have to make notes after a long call. It was also exceedingly useful after I'd fallen from my mountain bike and was suffering from a severe concussion. Once I'd passed from hospital care to my specialist, the call recordings were used to show just how badly my memory had been impacted at the time of the accident, and as I recovered in the weeks afterwards. These recordings were invaluable in measuring/documenting my recovery.

While you can argue that this isn't core functionality for the OS, Call Recording has been a core Telephony feature for decades, and is a regulatory feature for many industries (such as certain Financial services). Crippling this service without giving customers or developers a viable alternative doesn't make your platform more secure. At best it encourages users to weaken that security (rooting their devices), at worst it drives them to use other providers, introducing a myriad of other issues in the process.

I specifically use ACR Call Recorder by NLL and have been doing so for the past couple of years, and in that time I have found the app to be absolutely indispensable as it allows me to record both side of the telephone conversation, it allows me to retain information that might have normally been missed without having to ask for this information over and over again, I recently was in a disagreement with my former credit card company however I was able to produce a recording that contradicted what they recently stated as a result of the call recorder app it saved me in excess of £600.  

I can name many more instances whereby the use of ACR by NLL has saved a lot of time and money and in another instance saved my sons friend from verbal intimidation on his phone. Googles intended policy to restrict such app as this will have a detrimental effect on many many users, who I might add are aware of the permissions required for the app to operate correctly, I made this decision myself and have never looked back, there are over 500,000 app downloads on this specific app alone, with many more similar apps in the Google play store market that will be effected by this detrimental policy.

I understand that NLL has already applied for exemption, however this has been denied.

I use the app daily, I have purchased additional Google One Storage so that my audio files are securely stored and can be referred back to at any time and at my discretion.  

Without exaggeration this app empowers its users, and anybody that has been inundated with either marketing or malicious calls, Google will be effectively taking this away, I implore Google "Dont be evil" and "Do the right thing"

Concordo. Deve ser dado o poder aos utilizadores, de forma informada, a autorizar ou não as APP a ter acesso  à identificação das chamadas e SMS

Have they ever have they ever considered that some users need affected apps for medical reasons... Please consider the assistance such apps provide when already facing stressful health conditions that affect one's recall and has saved me playing phone tag with the Doctor's office to confirm information. Having MS it's not easy to take notes and keep my train of thought on covering important changes in ones treatment plan.. Call recording with permissions are a God send for me and many others! PLEASE Consider that too!

Verificar todos

PLEASE DONT FUCK IT AGAIN GOOGLE!!!! MAKE RESTRICTION FOR Call recorders and utility also!!!

It's our right to use an app and know the legalities behind it dictating our personal use. Preexisting apps should be grandfathered in. I suffer from blackouts and loose track of time and the things I've done, no not because or drugs but because of mental health issues. I need a call recorder so I know what I've done.

could you guys please leave acr call recorder alone and let it keep running like its meant to cause it comes in handy to keep things straight on what times and places to be and is alot faster then having to wright it all down let alone it works great to keep people from lying to you as it has for me with a guy at a sprint store so let it keep using call-logs and what not

Less and less services.
Google world is anything except à democracy.
Let people live their life....

Thank you, google! ACR, the best call recorder will be broken because of your limited thinking. Thanks to the recording of conversations, I do not have to remember all the details and arrangements, because at any time I can go back to the recording, everything is properly described by phone numbers. I also love the fact that I do not have to remember to switch on the conversation recording, assign a contact to the recording, and that I can turn off some contacts from recording. I understand that you want to ensure the safety of users, but it is logical that when someone installs the application for recording conversations, he understands that it will have a wider access to data on the phone. This is not an application that smuggles elevated privileges, but a popular application explicitly specifying what it is for. Please, take a look at the exclusions from this rule of some popular applications, because searching for "unlimited" versions from other sources than your store will not be safer for users.

This is a needless crippling.of software. Users would not be stupid enough to download and install a call recorder software without knowing it will record calls and keep track of the numbers associated with each call.

These type of useful features are what compel me to stay loyal to Android. Continuing to mess with such well functioning utilities will make Android no better than iOS. / Apple.
Add comment

I agree with all said in this thread. Google, stop breaking good software that makes Android an awesome platform it is now.

Add me to the list of people upset with this new policy. They must be doing this to protect themselves from lawsuits. They should figure out another way to protect themselves instead of crippling phone recording apps. I use a recording app to review conference calls that I am in and to take notes afterwards of what everyone had said. There are so many valid uses for recording calls. Google needs to stop policing what people can or can't do with their phones.

As everyone has already said what I have to say, I would like to say "ADD ME TO THE LIST OF PEOPLE UPSET!" This is truly a sledge hammer approach to the serious issue of security.

Simply allow apps with sensitive permission request a dev only option that must be unlocked through the appropriate settings and then have a splash page that we have to agree to every time we go to download one of these apps. This would reduce your employee's workload for approving exemptions for specific apps. OR better yet, give apps who's sole purpose is to deal with sensitive permissions, the rightful exemptions while leaving apps that bury their permission request in the cages they belong in (looking at you facebook). This will be a major blow and I will be sure to stop using Google Play for my apps. The only thing saving me from going to apple is the fact that there are other app providers for android.

Simple solution:  Disable CALL_LOG permissions by default, but but allow user to override in the app settings with a warning about the implications.  That way, people who want it just have to jump through an extra hoop and the default user your are trying to protect never sees or hears about it.  

Why is this even an issue?  Just give the user the option to override as necessary.

Come on u know is not right. If i a user choose to use app that breaks a law that is on me for using it. Most all 50 states allow u to record calls. I sse u loosening many users to other platforms

Agreed, android should be able to record with users Express permission,
especially when we paid for this service! Please correct this otherwise I
will report Google play to the better business bureau for taking money for
a service and restricting said service's permissions.

On Thu, Jan 17, 2019, 1:19 AM <buganizer-system@google.com wrote:

Please do not try to protect us from our decisions. We are not children. Show a warning and shut up.

Of course we all know the real reason: Google wants all data only for itself. Living in the EU I hope some day Google will get a huge GDPR penalty for its data collecting and sharing practices.

Have they explained why they're doing this? Seems pointless, but I'm sure there's some nefarious reason.

In some countries it's fully legal to record all calls without disclosure, in all it's legal WITH disclosure. But if you are going to block all apps from doing this, what are we going to do? In short: DON'T BLOCK CALL RECORDER APPS!!!!

I would strongly urge you to reconsider.  These facilities are not only used for nefarious purposes.

Following a stroke I have been left with mental impairment to faculties such as memory. As a disabled user I regularly use ACR and find it invaluable to review and record details from conversations.

Please exempt call recording (i.e. Advanced Call Recorder) and automation apps (i.e. Tasker) from the restrictions to call-logs and SMS.

Call Recorder has pulled me out of some hairy situations in the past.

Це є неправильна політика

I have never purchased an iOS device, simply because of the the way iOS acts as if it knows what you need more than you do.
Don't become just like them. We don't need that. That's why so many people chose Android.
Millions of people have been using ACR for several years for both medical and legal matters. This kind of blanket restriction is a strike against your customers' right to protect themselves.
It's also a blatant show of disrespect for your users.
It's not your place to police us. Keep your eyes on customer service. If one of us breaks the law, there are multiple law enforcement agencies who will deal with it. Not your circus; not your monkeys.

+1 to this. This is ridiculous. You are becoming Apple. I hate Apple. Don't make me hate you as well.

I just looked at the Google Play Store listings for the ACR Call Recorder app and ACR Call Recorder License. The free ACR app has 10 MILLION + downloads, and a rating of 4.4 from over 500,000 users. The ACR Call Recorder License is #5 Top Paid Productivity app in the Google Play Store, with a rating of 4.1.
What makes Google think that gutting an app that so many of their customers use is a good business plan?

Hacked

I bought an Android specifically because I could use ACR call recorder, and also apps that give me different vibration patterns and LED configurations based on the person texting or calling me.

My business DEPENDS on this. Now my phone is just like a phone from 2003.  It's literally lost all the functionality I need and REQUIRE.

Why can't you vet certain apps thay have been trusted for years? Or have big pop-ups that remind you that it's accessing your phone calls.

ANYTHING would be better.

Why does Google have to blow up the entire building rather than fix one doorknob?

You've aiienated and screwed with dozens of MILLIONS of users who DO know what they're doing, and wrecked the functionality of some of the most crucial elements of the phone.

Meanwhile, Android's base functionality for ring pattern or text message signatures is abhorrently outdated. Even Blackberries did better than this back in 2005 with ring patterns and profiles.

Brutally stupid decision. I am shocked.

+1
Wake up! Let us use android HOW WE NEED IT not how you want it!
You're loosing, step-by-step, every piece of advantage as a mobile SO, that android had on the market.
Maybe I could suggest other "inteligent" moves:
- lock home screen customizations
- stop remote access apps like teamviewer's quicksupport
aso
and I'm sure there will be another SO's or hacks available in no time

By forbidding everything google play store will become GULAG punishment store.

I support transparency efforts for app permissions but unless something is malicious it should be allowed in the Play Store. Preventing developers from adding functionality they require is just going to push people out to get and access their needed functionality in other locations, to get their apps elsewhere.

This is an unnecessary and terrible policy change!

Google should add acr call recorder into an allowed apps list to be able to use the restricted permissions. This will impact my day to day work, as i rely on acr to handle clients.

Wie need the recording software acr.
It is our decision to uwe it. Google listen to your users and customers.

Bad move google. I rely on ACR heavily. Every call I make to corporations is recorded but I cannot record it, how is that fair??? Pie will be my last iteration of Android I think.

I'm in a one party State I downloaded ACR Pro knowing it was a call recorder. That isn't a surprise to me. I'll have to look into rooting my phone. Yes, the feature is that valuable to me.

If I was ACR I would ask their millions of customers for an extra donation to sue Google, I'm open to donate $20-$50. Google allowed ACR to be on the Play Store for a long time, in fact 200 or something recording apps but now Google says we will disable a feature your company and many others use that has made a product for so we allowed you to be on the store and accept money from customers and now we are blocking a key feature of your product. Google says they will allow exemptions but then says call recorders are not exempt. Huh!!! Why not? So far Google has not been able to explain why for any of this. I don't blame ACR, due to unfair trade practices Google is basically telling a company they are going to go under and there is nothing Google will do about it! I call BS.

The technology is there and it's already implemented it's called allowing users to accept that the app they loaded will indeed record calls and get the caller information from contacts. If I download a call recorder I am obviously recording calls and it's up to me to know if recording calls is legal in my State or country (I'm in a one party State).

I believe Google is causing harm to these call recording app makers (companies) for no reason at all. It's clear what these apps do, they should be able to get an exemption and be exempt. If you require them to make it more clear upon installing the app that would be a solution to a problem Google made up but it would be a common sense fix to any confusion.

I haven't rooted a phone in a long time, but now I am considering it. I will also not install any system updates if I can help it. I know they tend to bug you to do it though and it's easy to hit that button to install one early morning. Sorry but I don't want Android 9, I don't want to loose a key feature I like and PAID for. I really do think ACR and other call recorder apps have a case, you simple can not allow companies to be on the Google Play store and then change the game in the middle without a way for them to keep a key feature of their app. Plus you allowed them to continue to accept money from people that might not know about the issue that will come which is BS. ACR is caught int he middle because no one knows what Google will 100% do till it is done.

I would also like ACR to push out that they might not be on the Google Play store anymore and charge maybe more for their app and instead sell the apk file through a website and we as users can download and install the file. It's not hard and I find it funny we rely on the Google Play Store for apps. I don't rely on any online store for my PC Software so why is the mentality of today's youth think just because it's on the play store it's safe? So many spammy type games out there and Google doesn't give a shit about them. I honestly would treat ACR Pro as any other software and go to their website and download an apk file maybe it won't be $15 (I forget what it was) maybe it will be like any other software and be $50 but it's worth the $50 to me. The software would just hit ACR's servers for updates.

For a Start Up I find it appalling as we look to make our own app vs just being on the PC. So this means one day after spending hundreds of thousands to design our app and getting it to work Google says "you know what users don't have a right to access the GPS and receive data from that". So now that we spend hundreds of thousands on design of an app, and sold premium APP functions to (hopefully) millions of users we got to close our doors? That seems kinda crazy to think Google can control a companies future by just changing the game mid-play. Then says they will do exemptions but when you request one they say NOPE we don't exempt your type of app. That is nuts, and that seems again like a lawsuit and class action as it in the above real case has affected 200+ call recorders. I hope they sue and I'll donate to that.

I need ACR to continue to function! It literally saved my life. I was able to prove malfeasance by a Physician via a recording. The hospital apologised and I finally received proper care. The hospital already HAD the same recordings, but REFUSED to even try to find the truth. My state us a one party consent state. It is totally legal for me to tape calls. Why are you removing this LIFE SAVINGS consumer protection? Wrong!

Hey!
Recording calls is a core feature, you have to allow it

Call recording is the sole reason I switched from iPhone. Please don't remove this feature.

Please, allow recording calls and access to phone numbers!

I switched from Apple to Android because I didn't like the way Apple crippled their phones functionality... I use apps like Tasker to auto reply to SMS or calls when I am driving or otherwise unavailable and ACR Pro as my memory is poor and I need to refer back to things I said I'd do - now removing this functionality is pushing Android down the Apple business model... please reconsider these restrictions or risk losing loyal a growing loyal client base.

Hey Google! If I didn't want an app that uses my call log or contacts I wouldn't download it. The fact that you're taking away an app that I paid money to use is utter bullshit. And you have no right to tell me what apps I can or cannot use on my phone. I use ACR for recording calls I make to bill companies when I pay my bills. It comes in handy when I can't write confirmation numbers down. What pisses me off is I paid for a apps service that now you think you have a right to take away. Why don't mind your own damn business. And let us be the judge of the apps we want or need to use on the phones we as consumers pay for. When you start paying my phone bill then you can decide what I put on my phone.

Stop copying apple.... And don't treat your users like a bunch of retard...

You guys changing your own creation dumber and dumber

Not cool at all

I tried to be calm and peace .

but there's only cursing came out of my brain about this issue.

so, good job google

I paid full price for Ceberus.  I've been using it for years and now one of the main features of the app, the SMS Log, no longer functions as it should. I didn't make this choice and I'm not sure why you made it for me, for all of us? You have over 1000+ comments from unhappy users. What's it going to take to revert your policy back and do us right?

Please PLEASE don't do this, Google. Please!

This is a very bad decision by Android and Google in general. I paid for my stinking phone and I live in state with 1 party consent rule. What is wrong with you Google?

Google, we know you removed "Do no evil" as a motto but you don't have to become a corporate #$&@%. The more you restrict the freedoms in the name of control and security the more you lose your loyal base of users. Make it harder to get these permissions, make it obvious to users that they are in use (which you have) but DO NOT remove the ability to use them! This is against the spirit of Android and you can gain nothing but strong resentment for it. Show some care towards your knowledgeable users and don't cripple functionality because of vulnerabilities of simpler users.

One more point. Because of this silly and unnecessary limitation I will refrain from updating my phone to Pie and won't be able to benefit from the security updates. I need ACR everyday so this is critical to me. You are forcing us to make a choice between ongoing security and feature updates and being able to use critical functionality. How does this serve your purpose of protecting users?!

This restriction also breaks the Call Announcer/Name Announcer apps.  Being able to have my phone calls announced by name is the main reason I am using an Android phone instead of an iPhone.  I just noticed that the latest ios software is now offering a Call Announcer feature.  I guess it's time to switch back.

"One more point. Because of this silly and unnecessary limitation I will refrain from updating my phone to Pie and won't be able to benefit from the security updates. I need ACR everyday so this is critical to me. You are forcing us to make a choice between ongoing security and feature updates and being able to use critical functionality. How does this serve your purpose of protecting users?!"

Same here, there is literally no point in updating my phone if it cripples my usage. This is a bad and stupid move on Google's part. You don't have to strong arm people. Just be clear in your communication with the end user. We're not stupid, just tell us exactly the concern is and let US choose.

And at the same time they continue to allow the use of Absher that improves the possibility to maintain social control over Saudi Arabian women.
If there was any logic they would ban Absher and allow ACR so people who are being harassed etc can document this.

What's the purpose of banning legitimate call recording apps like ACR? I'll download it from Samsung store for now, but will think twice before I buy my next phone. How come Apple provides more freedom to its developers and users than Android?!

FU Google. keep doing shitty things like you always do.

Wow this is very disappointing what do you think this is gonna accomplish do you think this is gonna increase androids market share all your doing is upsetting powerusers and judging from the amount of comments in this thread powerusers probably make up a larger percentage of your user base than you think.one of the big reason people use android over ios is because it's a more capable of that's offers a more diverse and unique selection of apps because of these extra permissions.we don't need another ios there was a time where you were actually to differentiate android from ios by offering more features and capabilities.now android is slowly just turning into ios even the design of Android pie looks more similar to ios.Android was always a more balanced os because it gave the user flexibility and choice but also kept users safe as well.example enabling sideloading apps completely optional if users wanted to sideload apps the system would warn them first but they could do it and if they didn't want to sideload well the option was toggled off by default thats the perfect way to do things give users choices.i don't understand why your axing all of these permissions all of the sudden.there are alot of angry people in the comments who are simply cursing at you,and while I understand there frustration angry comments are not gonna help so what I'm gonna do instead is offer some ideas that will help to ensure that the user is safe from malicious apps without removing  permissions for power users either.

-make users more aware of what permissions an app is asking for

-have the call log and sms permissions turned off by default and bury the permissions in the system settings so the average user won't know how to to toggle  them on and let powerusers turn these permissions on through the system settings so they could use apps that require these permissions.

-make users more aware of play protect

I hope you read this and actually consider it android has always strikes the perfect balance between freedom and safety and it catered to both average users and powerusers but now with these new changes your making lately your turning power users away from your platform please listen to the people that use your product.

Reverse the decision. Have disabled system and app updates for the time being, until this gets fixed. No security updates, but I guess that's what Google wants.

Hi,

Is there any way our app could be reviewed by some person. We are still getting a response from some robot saying that our app Callistics don't need access to calls and messages for main app functionality. It is funny for an app with Calls, messages and data statistics.

https://play.google.com/store/apps/details?id=cz.mobilesoft.callistics

more than 60 000 active users.

I have totally no idea what to do :-(

This is madness!!! I also use a call recorder (on legal advice) and your policy cripples my app. Please allow access for call recorders!

I object to the restriction/elimination of call recorder apps. Many commercial companies record conversations with their customers for "training and legal" purposes. I wish to have (and am legally allowed to have) my own copy of such conversations. I specifically switched from the IOS (Apple) platform to Android because Andriod is (or was) a more open platform which allowed this functionality. Please do not eliminate/restrict call recording apps.

Really... I'm all in favour of restricting misuse of my personal data through malicious apps but not through apps I WANT TO AUTHORIZE! You are not letting me choose! Make an opt-in procedure at least. Something like "All apps have no call log permission except the one I authorise on my phone". That was previously possible with permission management,. it was working, why change it?

As long as Google restrict my freedom of choice I will not pay for any Google service!!  - including my family and  friends.

Hola, por favor Google, no vuelva inútiles miles de apps con el bloqueo de número de llamada, si una app es legal y limpia no va a producir daño. De esta forma van a conseguir que Android cada vez sea más inútil, tanto peca lo mucho como lo poco. Es de sentido común.
Hello, please Google, do not make useless thousands of apps with blocking the number of call, if an app is legal and clean it will not cause damage. In this way they will make Android more and more useless, as much sins as little. It's common sense.

This decision will make me download  an alternative app from the phone maker app store, for the first time in my life. Very bad decision for me.

Empresa ridicula. Ganha dinheiro com a gente e acha que pode escolher o que é melhor pra gente. Se eu compro um App legítimo, pela PlayStore, pra tentar proteger mais o meu aparelho, já que o serviço de rastreamento da Google é um lixo, o mínimo que eu quero é poder usar todas as funções dele, inclusive os comandos SMS e log de chamadas, que agora não funciona devido a essas mudanças ai. Ta na cara que porque vocês não tem capacidade de fazer um App tão bom, ai ficam atrasando o lado da concorrência. Ridículo...E mais uma vez, o usuário que se dane...

I often use tasker in ways that require these permissions. Without them i will likely be forced to use third-party non-playstore apps. Nobody wants this

While everybody at Google is laughing, people who paid for apps are suffering.

Can anyone in Google Play Market explain what is this update  serving for?

+1 this is a problem! I'll switch to iOS or jailbreak if needed.

This, alone, will cause me to leave google.  This is ridiculous!!!  We need this!

Just adding my voice to the chorus telling Google that you did the wrong thing for the end-users. Apps that access phone call info ask for that permission upon installation, and that is perfectly acceptable. Allowing folks to develop applications that integrate with all functions of an Android device is one of the things that makes that platform desirable (vs. Apple). Please reconsider your policy here.

Bad move

Google, please reverse this decision. Call recording is very legal in many countries and  I chose Android as it gave me the most freedom of any mobile OS, this is a step backwards. And, by the way, it should be for user to deside what she/he allows apps to use.

Google alow users to make there own choices, allow us to choose! Alow phone number access to apps.