image v7.1.0

Author: marchbold

docs/image/_includes/add-manual-appdescriptor.mdx

@@ -23,12 +23,20 @@ add the following to your manifest additions:
 
 ```xml
 <manifest android:installLocation="auto">
+	<uses-sdk android:minSdkVersion="19" />
+
 	<uses-permission android:name="android.permission.INTERNET"/>
-	
+	<uses-permission android:name="android.permission.FOREGROUND_SERVICE"/>
+	<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION"/>
+
 	<application>
+		<service android:name="com.distriqt.extension.image.services.ScreenshotService"
+			android:foregroundServiceType="mediaProjection"
+			android:exported="false" />
+
 		<activity android:name="com.distriqt.core.auth.AuthorisationActivity" android:theme="@android:style/Theme.Translucent.NoTitleBar" android:exported="false" />
 	</application>
-	
+
 </manifest>
 ```
 

docs/image/capturing-a-screenshot.md

@@ -1,23 +1,55 @@
 ---
 title: Capturing a Screenshot
-sidebar_label: Capturing a Screenshot
 ---
 
 
 You can use this extension to capture a screenshot of your application as bitmap data and subsequently use that data as you require. 
 
 This is currently supported on iOS and Android API version 21 or higher. 
 
-To capture a screenshot you simply call `captureScreenshot` and await completion. 
+To capture a screenshot you simply call `captureScreenshot()` and await completion. 
 
 ```actionscript
-var success:Boolean = Image.service.captureScreenshot();
+Image.service.captureScreenshot();
+```
+
+`captureScreenshot()` may return `false` if the current platform is not supported or if a screenshot capture is currently in progress. You should avoid wherever possible capturing two screenshot simulataneously as this may have undesirable results.
+
+
+
+
+## Completion
+
+You can either use a callback or events to handle the completion of the screenshot.
+
+
+### Callback
+
+You can pass a callback function to the `captureScreenshot()` method:
+
+```actionscript
+Image.service.captureScreenshot(
+        function ( bitmap:BitmapData ):void
+        {
+            if (bitmap != null)
+            {
+                // bitmap will contain the bitmap data of the screenshot
+                trace( "captureScreenshot: complete" );
+            }
+            else
+            {
+                trace( "captureScreenshot: an error occurred" );
+            }
+        }
+);
 ```
 
-`captureScreenshot` may return `false` if the current platform is not supported or if a screenshot capture is currently in progress. You should avoid wherever possible capturing two screenshot simulataneously as this may have undesirable results.
+The callback function must be of the format: `function ( bitmap:BitmapData ):void`.
+
 
+### Events
 
-Completion is indicated by either a success event `ImageEvent.SCREENSHOT_COMPLETE` or an error `ImageEvent.SCREENSHOT_ERROR`. 
+You can listen for a success event `ImageEvent.SCREENSHOT_COMPLETE` or an error `ImageEvent.SCREENSHOT_ERROR`. 
 
 ```actionscript
 Image.service.addEventListener( ImageEvent.SCREENSHOT_COMPLETE, screenshot_completeHandler );
@@ -38,15 +70,43 @@ function screenshot_errorHandler( event:ImageEvent ):void
 ```
 
 
-## iOS
+
+## Platform Considerations
+
+There are some differences between the platforms here.
+
+
+### iOS
 
 On iOS your screenshot will be captured without any user interaction. It is not possible to get the current image of the status bar so only your application accessible content will be contained in the screenshot. 
 
 
-## Android 
+### Android 
+
+Since Android 26 we now have a method to capture the screen without user interaction and this is now the default operation of the extension. This approach won't capture the status or navigation bar elements similar to iOS however the operation will be much more seamless.
+
+
+If you wish to force the extension to use the older approach (with a media projection) you can pass `false` as the second parameter to the `captureScreenshot()` method, which will attempt to capture the full screen.
+
+```actionscript
+Image.service.captureScreenshot( null, false );
+```
 
-On Android, user permission is required to capture a screenshot. On calling `captureScreenshot` your user may be presented a permission dialog. If they accept then the screenshot will be captured and subsequent screenshots will not require interaction. If they deny the permission then the screenshot will fail with an error event and subsequent screenshot capture attempts will present the permission dialog again. 
+#### Permission 
+
+On Android, user permission is required to capture a screenshot of the full screen. On calling `captureScreenshot()` your user may be presented a permission dialog. If they accept then the screenshot will be captured. If they deny the permission then the screenshot will fail with an error event and subsequent screenshot capture attempts will present the permission dialog again. 
+
+On older versions of the Android the following permission request is shown: 
 
 ![](images/android-capturescreenshot-permission.png)
 
 
+With Android 26 and higher you are likely to see something like:
+
+![](images/android-capturescreenshot-permission-26.png)
+
+
+On Android 36 and higher, you will have to get the user to select the "Share entire screen" option:
+
+![](images/android-capturescreenshot-permission-36.png)
+

docs/image/changelog.md

@@ -1,3 +1,10 @@
+### 2025.12.15 [v7.1.0]
+
+```
+feat(android): add new capture screenshot functionality to capture application view without user interaction 
+fix(android): correct issue with crash on newer android versions while using media projection to capture full screen (resolves https://github.com/distriqt/ANE-Image/issues/57, resolves https://github.com/distriqt/ANE-Image/issues/56)
+```
+
 ### 2024.12.17 [v7.0.0]
 
 ```

docs/image/images/android-capturescreenshot-permission-26.png

@@ -13,5 +13,5 @@ Particularly due to all the file system changes in Android that require addition
 
 Migration should be relatively straight forward, just replace the `Image.service.saveToCameraRoll()` with `CameraRollExtended.service.addBitmapData()`.
 
-For more information see the documentation on the [CameraRollExtended](/docs/camerarollextended/adding-files.mdx).
+For more information see the documentation on the [CameraRollExtended](/docs/camerarollextended/adding-files).
 

docs/image/images/android-capturescreenshot-permission-36.png

@@ -0,0 +1,43 @@
+---
+title: Migrating to v7.1
+---
+
+import Tabs from '@theme/Tabs'
+import TabItem from '@theme/TabItem'
+
+This version makes some changes to the Android implementation to support capturing screenshots.
+
+We have changed the default operation to use a new method that doesn't require user interaction for permissions but only captures the application window (similar to iOS). 
+The previous method that captures the full screen including other applications is still available and has been improved to support the new requirements of using a foreground service but continues to require user permission via a system dialog.
+
+This update requires some changes to the manifest additions, so you will need to update your application descriptor accordingly. 
+
+If you are using [`apm`](https://github.com/airsdk/apm) to manage your extensions you can update your application descriptor automatically by following the instructions below.
+
+```
+apm update 
+apm generate app-descriptor 
+```
+
+If you are managing your application descriptor manually you will need to ensure your manifest additions contains the following:
+
+```xml
+<uses-permission android:name="android.permission.FOREGROUND_SERVICE"/>
+<uses-permission android:name="android.permission.FOREGROUND_SERVICE_MEDIA_PROJECTION"/>
+
+<application>
+    <service android:name="com.distriqt.extension.image.services.ScreenshotService"
+        android:foregroundServiceType="mediaProjection"
+        android:exported="false" />
+
+    <activity android:name="com.distriqt.core.auth.AuthorisationActivity" android:theme="@android:style/Theme.Translucent.NoTitleBar" android:exported="false" />
+</application>
+```
+
+
+As the default operation has changed to the new method that doesn't require user interaction, if you wish to continue to capture the full screen including other applications you will need to pass `false` to the second parameter of the `captureScreenshot()` method.
+
+```actionscript
+Image.service.captureScreenshot( callback, false );
+``` 
+

docs/image/images/android-capturescreenshot-permission.png

@@ -7,7 +7,7 @@ sidebar_label: Saving BitmapData to the Camera Roll
 :::warning
 This functionality has been deprecated and will be removed in an upcoming release. 
 
-You should move to the [CameraRollExtended](/docs/camerarollextended/adding-files.mdx) extension for adding images to the Camera Roll.
+You should move to the [CameraRollExtended](/docs/camerarollextended/adding-files) extension for adding images to the Camera Roll.
 
 Migration should be relatively straight forward, just replace the `Image.service.saveToCameraRoll()` with `CameraRollExtended.service.addBitmapData()`.
 :::

docs/image/migrating-to-v6.0.mdx

@@ -2063,7 +2063,12 @@ module.exports = {
     },
 
     {
-      Help: ["image/migrating-to-v5.2", "image/migrating-to-androidx"],
+      Help: [
+        "image/migrating-to-v7.1", 
+        "image/migrating-to-v6.0", 
+        "image/migrating-to-v5.2", 
+        "image/migrating-to-androidx"
+      ],
     },
     {
       Other: [