Improve androidmanifest code examples

Author: pinkeshmars

docs/ff-concepts/adding-customization/configuration-files.md

@@ -114,8 +114,8 @@ For more complex changes, you can enable **Manual Edit Mode**, which essentially
 
 To manually edit native files, navigate to **Custom Code** (from the left-side menu) > **Configuration Files**, select the file you want to edit, and click the **lock** button to unlock it. You can now freely modify the file.
 
-:::tip
-Once unlocked, the file stays in manual editing mode until you lock it again. Locking it will reset the file to a version generated by FlutterFlow.
+:::warning
+Once unlocked, the file stays in manual editing mode until you lock it again. Re-locking it will reset the file to a version generated by FlutterFlow, which will overwrite any manual changes you've made.
 :::
 
 <div style={{
@@ -226,7 +226,19 @@ Here are some scenarios where you may need to modify the `AndroidManifest.xml` f
 For including additional screens (activities), background processes (services), or listeners (broadcast receivers), you must declare them in `AndroidManifest.xml`.
 
 ```xml
-<activity android:name=".NewScreenActivity"/>
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    package="com.example.app">
+
+    <application
+        android:icon="@mipmap/ic_launcher"
+        android:label="@string/app_name">
+
+        <!-- Add your activity here -->
+        <activity android:name=".NewScreenActivity" />
+        
+    </application>
+
+</manifest>
 ```
 
 This registers `NewScreenActivity` so the system knows it exists.
@@ -236,8 +248,23 @@ This registers `NewScreenActivity` so the system knows it exists.
 If your app requires access to restricted resources like wake locks (to keep the device awake) or audio recording, you must declare the necessary permissions in `AndroidManifest.xml` by [manually editing](#option-2-manual-edit-mode) the file. **Tip:** You can also add custom permissions directly through the [**Permission Settings**](../../resources/projects/settings/project-setup.md#adding-custom-permission) in FlutterFlow.
 
 ```xml
-<uses-permission android:name="android.permission.WAKE_LOCK"/>
-<uses-permission android:name="android.permission.RECORD_AUDIO"/>
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+          package="com.example.yourappname">
+
+    <!-- Permissions -->
+    <uses-permission android:name="android.permission.WAKE_LOCK"/>
+    <uses-permission android:name="android.permission.RECORD_AUDIO"/>
+
+    <application
+        android:label=""
+        tools:replace="android:label"
+        android:icon="@mipmap/ic_launcher"
+        android:requestLegacyExternalStorage="true">
+
+        <activity android:name=".NewScreenActivity"/>
+
+    </application>
+</manifest>
 ```
 
 Without these, the app cannot keep the device awake or record audio.
@@ -247,37 +274,66 @@ Without these, the app cannot keep the device awake or record audio.
 Many third-party packages (Google Maps, Firebase, AdMob, etc.) require `<meta-data>` tag in `AndroidManifest.xml` to pass configuration values. For example, the [**Mapbox Flutter**](https://pub.dev/packages/mapbox_flutter) plugin requires adding your Mapbox access token as a metadata entry for initialization. A real example: to initialize Mapbox, you’d add:
 
 ```xml
-<meta-data
-    android:name="com.mapbox.token"
-    android:value="YOUR_MAPBOX_ACCESS_TOKEN"/>
-```
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    package="com.example.app">
 
-**Example 4: Configuring Play Asset Delivery**
+    <application
+        android:icon="@mipmap/ic_launcher"
+        android:label="@string/app_name">
 
-If your app has large assets (e.g., high-resolution textures, large media files), you may need Play Asset Delivery.
+        <!-- Your snippet goes here -->
+        <meta-data
+            android:name="com.example.MAPS_API_KEY"
+            android:value="YOUR_API_KEY" />
 
-```xml
-<meta-data
-    android:name="com.google.android.play.assetdelivery"
-    android:value="install-time"/>
+    </application>
+</manifest>
 ```
 
-This tells Google Play how to handle large assets.
-
-**Example 5: Restricting the App to Specific Devices**
+**Example 4: Restricting the App to Specific Devices**
 
 You can specify device hardware requirements (e.g., GPS, camera, touchscreen) to ensure the app only installs on compatible devices.
 
 ```xml
-<uses-feature android:name="android.hardware.camera" android:required="true"/>
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    package="com.example.app">
+
+    <!-- Your snippet goes here -->
+    <uses-feature android:name="android.hardware.camera" />
+
+    <application
+        android:icon="@mipmap/ic_launcher"
+        android:label="@string/app_name">
+        
+        <!-- other components -->
+
+    </application>
+
+</manifest>
 ```
 
 This prevents installation on devices without a camera.
 
-**Example 6: Enabling Cleartext Traffic**
+**Example 5: Enabling Cleartext Traffic**
 
 If your app needs to communicate over HTTP (unencrypted) for testing or legacy reasons, you might need to add `android:usesCleartextTraffic="true"` in the `<application>` tag. This is to relax network security for HTTP URLs.
 
+```xml
+<manifest xmlns:android="http://schemas.android.com/apk/res/android"
+    package="com.example.app">
+
+    <application
+        android:icon="@mipmap/ic_launcher"
+        android:label="@string/app_name"
+        android:usesCleartextTraffic="true"> <!-- Add this line -->
+
+        <!-- Other components -->
+
+    </application>
+
+</manifest>
+```
+
 :::tip
 You can modify the `AndroidManifest.xml` file by either [**adding a snippet**](#snippet-placement-for-android) or [**editing it manually**](#option-2-manual-edit-mode).
 :::