3

I have been developing and testing an app to update to the google play store as requested in this ongoing issue Google Play recent review notification - APK HAS A PROMINENT DISCLOSURE BUT THE DISCLOSURE IS NOT ADEQUATE

Whilst testing the app I have noticed that Display.getInstance().sendSMS(phoneNumber, message, true); no longer opens the default SMS app of the device. Previous builds before at least the 23rd of August last week did not have this issue and would open the phone permission prompt for the user to allow before launching to the SMS app. Display.getInstance().dial(phoneNumber); still works however. Has there been any recent change server side that would affect this? Will I need to add the permission manually somehow? Any help will be greatly appreciated.

Denis Kisina
  • 350
  • 4
  • 19
James N
  • 435
  • 3
  • 8

1 Answers1

3

We're still dealing with the problem in the Google Play recent review notification - APK HAS A PROMINENT DISCLOSURE BUT THE DISCLOSURE IS NOT ADEQUATE issue so we're investigating a lot of things including the phone permission which we disabled by default to avoid a case of accidental activation.

To explicitly enable this you will now need the build hint android.readPhoneState=true.

Shai Almog
  • 51,749
  • 5
  • 35
  • 65
  • Hi thank you for the support, unfortunately adding this build hint hasn't invoked any permission requests. Is there anywhere else I need to go to enable the hint? – James N Sep 02 '21 at 07:42
  • Using "android.permission.READ_PHONE_STATE=true" I am able to enable the phone permission. However the SMS app still does not launch unfortunately – James N Sep 02 '21 at 09:02
  • I can confirm add this key for the build hint has resolved the issue "android.permission.READ_PHONE_STATE=true". The SMS app is now launched. Thank you for your help as always – James N Sep 02 '21 at 10:18
  • I'm guessing this is related to something that broke in moving to the newer API level but that happened much sooner. – Shai Almog Sep 03 '21 at 02:56