What could cause access of CAPTURE_SECURE_VIDEO_OUTPUT, CAPTURE_VIDEO_OUTPUT, READ_FRAME_BUFFER ?

[Rollo62 502]

Hi there,

I've got suspicious log messages, with an Android App under Rx11.3.

Quote

2023.11.22 13:10:19.770    W    com.example.app    24748    24748    com.example.app    Accessing hidden field Landroid/Manifest$permission;->CAPTURE_SECURE_VIDEO_OUTPUT:Ljava/lang/String; (max-target-r, JNI, denied)
2023.11.22 13:10:19.770    W    com.example.app    24748    24748    com.example.app    Accessing hidden field Landroid/Manifest$permission;->CAPTURE_VIDEO_OUTPUT:Ljava/lang/String; (max-target-r, JNI, denied)
2023.11.22 13:10:19.770    W    com.example.app    24748    24748    com.example.app    Accessing hidden field Landroid/Manifest$permission;->READ_FRAME_BUFFER:Ljava/lang/String; (max-target-r, JNI, denied)

I am not using any 3rd Party frameworks, nor can I imagine what could cause this warning.
When I check, these fieds seems to be deprecated since Android 10, related to accessing screen contents.
https://developer.android.com/about/versions/10/privacy/changes#screen-contents

 

In the sources under FMX.Platform.Screen.Android, there seems to be a possible relation to DisplayManager, maybe this is doing something with the display.

https://developer.android.com/reference/kotlin/android/hardware/display/DisplayManager#virtual_display_flag_auto_mirror

https://developer.android.com/reference/kotlin/android/hardware/display/DisplayManager#virtual_display_flag_secure

or maybe RestrictedScreenReading has to do with it ...
https://source.android.com/docs/core/permissions/restricted-screen-reading?hl=en

FMX.Platform.Screen.Android:

  TAndroidScreenServices = class(TInterfacedObject, IFMXMultiDisplayService, IFMXScreenService, IFMXDeviceMetricsService, IFMXFullScreenWindowService)
...
  public
    property DisplayManager: JDisplayManager read FDisplayManager;
    property IsPrimaryDisplayDefined: Boolean read FIsPrimaryDisplayDefined;
    property PrimaryDisplay: TDisplay read FPrimaryDisplay;
  end;

But that is a rough guess.

 

The app seems to behave normally, but I wonder if that might cause probems in the future.

I'm testing under Android 14 now.
If anyone knows how to get rid of these warnings, or at least a hint where this could be related to, please let me know.

 

 

 

Edited November 22, 2023 by Rollo62

[Dave Nottage 493]

8 hours ago, Rollo62 said:

If anyone knows how to get rid of these warnings

Yes - update to Delphi 12. If that's not an option, and unless you're having problems with Play Store due to the warnings, it's pointless to do anything.

[Rollo62 502]

Oh my, I wanted to make an urgent update, before porting to D12.
I expect many new issues in apps, under D12, probably 1-2 weeks to get it stable again.
How is your experience, is it more or less smooth to migrate, for mobile stuff?

Ok, it seems I have to look into D12 sooner than I hoped.

[Dave Nottage 493]

21 minutes ago, Rollo62 said:

How is your experience, is it more or less smooth to migrate, for mobile stuff?

More or less, yes 🙂

21 minutes ago, Rollo62 said:

Ok, it seems I have to look into D12 sooner than I hoped.

Updating would be for far more important factors than those warnings