<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Hasnain Mirrani on Medium]]></title>
        <description><![CDATA[Stories by Hasnain Mirrani on Medium]]></description>
        <link>https://medium.com/@hasnainmirrani?source=rss-3cbdcddab1e5------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*3op8lCCOjK8PnI8SnPgTKg.jpeg</url>
            <title>Stories by Hasnain Mirrani on Medium</title>
            <link>https://medium.com/@hasnainmirrani?source=rss-3cbdcddab1e5------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 20:10:30 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@hasnainmirrani/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[The sandbox is not in sync with the Podfile.lock.]]></title>
            <link>https://hasnainmirrani.medium.com/the-sandbox-is-not-in-sync-with-the-podfile-lock-ef92285ac929?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ef92285ac929</guid>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 17:30:50 GMT</pubDate>
            <atom:updated>2026-07-22T17:30:50.384Z</atom:updated>
            <content:encoded><![CDATA[<h3>The sandbox is not in sync with the Podfile.lock. Run ‘pod install’ or update your CocoaPods installation.</h3><p>flutter clean<br>flutter pub get<br>cd ios<br>rm -rf Pods Podfile.lock<br>pod deintegrate<br>pod cache clean — all<br>pod install</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ef92285ac929" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Run Prepare Flutter Framework Script]]></title>
            <link>https://hasnainmirrani.medium.com/showing-recent-issues-run-pre-actions-schemeaction-run-prepare-flutter-framework-script-b7051bd36953?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b7051bd36953</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[build-issue]]></category>
            <category><![CDATA[showing-recent]]></category>
            <category><![CDATA[xcode]]></category>
            <category><![CDATA[ios]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Wed, 22 Jul 2026 17:23:08 GMT</pubDate>
            <atom:updated>2026-07-22T17:26:26.783Z</atom:updated>
            <content:encoded><![CDATA[<p>Showing Recent Issues Run pre-actions SchemeAction Run\ Prepare\ Flutter\ Framework\ Script /var/folders/gm/dl6z1p_16lj33vvdgcss9kfm0000gn/T/SchemeScriptAction-0XVMJi.sh</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FpPE8JDIy5BgTzWnTGbZ0w.png" /></figure><p>The Fix</p><ol><li>Open your project in <strong>Xcode</strong>.</li><li>Go to the top menu and select <strong>Product</strong> &gt; <strong>Scheme</strong> &gt; <strong>Edit Scheme…</strong> (or press Cmd + &lt;).</li><li>On the left sidebar, expand the <strong>Build</strong> menu and click on <strong>Pre-actions</strong>.</li><li>Look for the script titled <strong>Run Prepare Flutter Framework Script</strong>.</li><li>Ensure the <strong>Provide build settings from</strong> dropdown is set to your <strong>Runner</strong> target (instead of “None”).</li><li>Update the text script box to explicitly include Flutter’s configuration file. Replace or update the script content with this:</li></ol><pre>if [ -f &quot;$FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh&quot; ]; then<br>    /bin/sh &quot;$FLUTTER_ROOT/packages/flutter_tools/bin/xcode_backend.sh&quot; prepare<br>fi</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uMQ31VQwWg2bIOetFEQheA.png" /><figcaption>flutter clean<br>flutter pub get<br>cd ios &amp;&amp; pod install</figcaption></figure><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b7051bd36953" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Say Goodbye to OTPs: Implementing Firebase One-Tap Phone Verification in Flutter and React Native]]></title>
            <link>https://hasnainmirrani.medium.com/say-goodbye-to-otps-implementing-firebase-one-tap-phone-verification-in-react-native-4606cab956b2?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4606cab956b2</guid>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[firebaseauthentication]]></category>
            <category><![CDATA[otp-verification]]></category>
            <category><![CDATA[mobile]]></category>
            <category><![CDATA[firebase-phone-number]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Tue, 07 Jul 2026 06:23:30 GMT</pubDate>
            <atom:updated>2026-07-07T06:26:45.696Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*6_UDbQW9uR2WPJtEOPJlgA.png" /></figure><p>User onboarding can make or break a mobile application. Traditional SMS One-Time Passwords (OTPs) have long been the industry standard, but they come with a high cognitive load and significant user friction. We have all experienced the frustration of waiting for an SMS, switching apps to copy a code, dealing with typos, or requesting multiple codes when the first one fails to arrive. Every second of delay increases your app’s abandonment rate.</p><p>Firebase <strong>Phone Number Verification (PNV)</strong> changes the game for Android development. For users on supported cellular networks, Firebase can now verify a phone number silently in the background with a single tap. If the carrier does not support this feature, the system automatically and seamlessly falls back to the traditional SMS OTP method. This hybrid approach ensures zero drop-offs while drastically speeding up the onboarding flow.</p><p>How Firebase Phone Number Verification Works</p><ol><li><strong>User Initiates Sign-In</strong>: The user enters their phone number and taps “Verify”.</li><li><strong>Carrier Check</strong>: Firebase communicates with the cellular network operator to verify the device’s SIM card directly.</li><li><strong>Instant Token Issuance</strong>: If verified by the carrier, Firebase issues an authentication token instantly — no SMS sent, no code entered.</li><li><strong>Automatic Fallback</strong>: If the carrier network is unsupported or the user is on Wi-Fi without a cellular data connection, Firebase automatically sends a standard SMS OTP.</li></ol><p>Step-by-Step Implementation Guide</p><p>To implement this seamless verification flow in a React Native Android application, you will use the official @react-native-firebase/auth package.</p><p><strong>1. Prerequisites &amp; Configuration</strong></p><ul><li>Ensure your Android app is connected to a Firebase project.</li><li>Enable <strong>Phone Authentication</strong> in the Firebase Console under <strong>Authentication &gt; Sign-in method</strong>.</li><li>Add your app’s <strong>SHA-1 and SHA-256 fingerprints</strong> to your Firebase project settings. This is mandatory for cellular verification to function safely.</li></ul><p><strong>2. The Implementation Code</strong></p><p>The following functional component handles both the silent carrier verification and the manual SMS fallback using a single Firebase method: signInWithPhoneNumber.</p><pre>import &#39;package:firebase_auth/firebase_auth.dart&#39;;<br><br>class PhoneAuthService {<br>  final FirebaseAuth _auth = FirebaseAuth.instance;<br><br>  Future&lt;void&gt; startPhoneVerification(String phoneNumber) async {<br>    await _auth.verifyPhoneNumber(<br>      phoneNumber: phoneNumber,<br>      <br>      // 1. Silent Carrier Verification Success (One-Tap)<br>      // If the cellular network supports PNV, this triggers immediately.<br>      // No SMS is sent, and you get authenticated without manual code entry.<br>      verificationCompleted: (PhoneAuthCredential credential) async {<br>        await _auth.signInWithCredential(credential);<br>        print(&quot;Success: Verified silently via carrier without an OTP!&quot;);<br>      },<br><br>      // 2. Carrier Verification Fails / Fallback (SMS Sent)<br>      // If the carrier does not support PNV, Firebase automatically drops back<br>      // to standard SMS and provides you the verificationId to handle manual entry.<br>      codeSent: (String verificationId, int? resendToken) {<br>        print(&quot;Fallback: Carrier PNV unsupported. SMS code sent to device.&quot;);<br>        // Save verificationId and navigate user to your OTP entry screen<br>      },<br><br>      // 3. Handling Configuration Errors<br>      verificationFailed: (FirebaseAuthException e) {<br>        print(&quot;Verification failed: ${e.message}&quot;);<br>      },<br><br>      // 4. Timeout callback for Android devices<br>      codeAutoRetrievalTimeout: (String verificationId) {<br>        print(&quot;Auto retrieval timeout reached.&quot;);<br>      },<br>    );<br>  }<br>}</pre><pre>[ User Enters Phone Number ]<br>                            │<br>               _auth.verifyPhoneNumber()<br>                            │<br>            ┌───────────────┴───────────────┐<br>            ▼                               ▼<br>    [ Carrier Check ]              [ Carrier Check ]<br>     👉 Supported                   ❌ Unsupported<br>            │                               │<br>            ▼                               ▼<br>  verificationCompleted                 codeSent<br>            │                               │<br>  ⚡ Silent Authentication        💬 SMS OTP Sent<br>            │                               │</pre><h3>▼</h3><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4606cab956b2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[CocoaPods vs Swift Package Manager (SPM) in Flutter iOS]]></title>
            <link>https://hasnainmirrani.medium.com/cocoapods-vs-swift-package-manager-spm-in-flutter-ios-13f61121e166?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/13f61121e166</guid>
            <category><![CDATA[swift-package-manager]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[spm]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[cocoapods]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Thu, 07 May 2026 08:09:10 GMT</pubDate>
            <atom:updated>2026-05-07T08:09:10.556Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Future of Dependency Management for Flutter Developers</h3><p>Flutter iOS development is evolving rapidly, and one of the biggest changes introduced in recent Flutter releases is support for <strong>Swift Package Manager (SPM)</strong> alongside the traditional <strong>CocoaPods</strong> dependency manager.</p><p>For years, CocoaPods has been the default package manager for Flutter iOS projects. But now, Apple’s native dependency solution — Swift Package Manager — is becoming a strong alternative.</p><p>If you’re a Flutter developer working on iOS apps, understanding the differences, migration strategy, hybrid approaches, and potential pitfalls is essential.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*L6bvxpe4VeTDQRYPTdB_zw.png" /></figure><h3>What is CocoaPods?</h3><p>CocoaPods is a dependency manager built specifically for Objective-C and Swift projects.</p><p>Flutter has historically relied on CocoaPods to integrate iOS plugins into Flutter applications.</p><h3>Advantages of CocoaPods</h3><ul><li>Mature ecosystem</li><li>Wide Flutter plugin support</li><li>Extensive community adoption</li><li>Stable integration with older projects</li><li>Handles complex dependency trees well</li></ul><h3>Disadvantages of CocoaPods</h3><ul><li>Slower dependency resolution</li><li>Ruby dependency issues</li><li>Frequent pod install/update conflicts</li><li>Can increase build times</li><li>Xcode integration sometimes breaks after updates</li></ul><h3>What is Swift Package Manager (SPM)?</h3><p>Swift Package Manager is Apple’s official dependency management system integrated directly into Xcode.</p><p>Flutter 3.24+ introduced experimental support for SPM-based plugin integration.</p><h3>Advantages of SPM</h3><ul><li>Native Xcode integration</li><li>Faster dependency resolution</li><li>No Ruby installation required</li><li>Cleaner project structure</li><li>Better compatibility with Apple ecosystem updates</li><li>Reduced maintenance overhead</li></ul><h3>Disadvantages of SPM</h3><ul><li>Not all Flutter plugins support it yet</li><li>Some plugins still rely on CocoaPods internally</li><li>Limited documentation compared to CocoaPods</li><li>Migration can introduce build configuration issues</li></ul><h3>CocoaPods vs SPM — Comparison Table</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*X4hFMRBBjVGS4bspp-va3A.png" /><figcaption>Why Flutter is Moving Toward SPM</figcaption></figure><p>Apple strongly encourages developers to adopt SPM because it is deeply integrated into Xcode and simplifies dependency management.</p><p>Flutter is gradually adding support to reduce reliance on CocoaPods and improve iOS build performance.</p><p>Benefits Flutter developers may notice:</p><ul><li>Faster iOS build times</li><li>Cleaner iOS project structure</li><li>Reduced pod-related conflicts</li><li>Better future compatibility with Xcode updates</li></ul><h3>How to Enable Swift Package Manager in Flutter</h3><p>Proceed as follows to migrate from CocoaPods to SPM for your Flutter project.</p><h3>Step 1. Update your Flutter SDK</h3><p>Ensure you’re using Flutter 3.24 or later, as SPM support is only available in recent releases.</p><pre>flutter upgrade</pre><pre>Then enable Swift Package Manager support:</pre><pre>flutter config --enable-swift-package-manager</pre><h3>Step 2. Verify Plugin Support for SPMNot all Flutter plugins currently support SPM.</h3><p>To verify compatibility:</p><ul><li>Review the plugin’s GitHub repository</li><li>Check plugin documentation</li><li>Look for a Package.swift file</li><li>Confirm SPM installation instructions exist</li></ul><p>If a plugin does not support SPM, Flutter will automatically fall back to CocoaPods.</p><h3>Step 3. Test Your Project with SPM</h3><p>Run your Flutter project:flutter run</p><ul><li>Download compatible SPM dependencies</li><li>Resolve package versions</li><li>Build iOS packages through Xcode</li></ul><p>Carefully monitor build logs for:</p><ul><li>Missing package errors</li><li>Duplicate framework issues</li><li>Architecture conflicts</li></ul><h3>Step 4. Disable CocoaPods (Optional)</h3><p>If all plugins support SPM, you can fully remove CocoaPods.</p><h3>Remove Pod Files</h3><pre>rm -rf ios/Pods<br>rm -rf ios/Podfile<br>rm -rf ios/Podfile.lock<br></pre><h3>Clean Flutter Project</h3><pre>flutter clean<br>flutter pub get<br>flutter run</pre><h3>Hybrid Approach — Using CocoaPods + SPM Together</h3><p>One of the most practical strategies today is using a <strong>hybrid dependency management approach</strong>.</p><p>In this model:</p><ul><li>SPM handles supported plugins</li><li>CocoaPods handles unsupported plugins</li></ul><p>Flutter can work with both systems simultaneously.</p><p>This is currently the safest migration strategy for production apps.Potential Challenges and Solutions</p><h3>1. Mixed Dependency Management</h3><p>When certain dependencies use SPM while others use CocoaPods, Flutter will work with both systems at the same time.</p><p>However, this may introduce:</p><ul><li>Duplicate frameworks</li><li>Build setting conflicts</li><li>Linking issues</li><li>Dependency version mismatches</li></ul><h3>Solution</h3><ul><li>Ensure dependencies are uniquely configured</li><li>Avoid duplicate native SDK imports</li><li>Keep plugin versions updated</li><li>Validate framework linking inside Xcode</li></ul><h3>2. Build Failures</h3><p>Errors may occur if plugin SPM configurations are incomplete.</p><h3>Common Issues</h3><ul><li>Invalid Package.swift</li><li>Unsupported architectures</li><li>Missing binary targets</li><li>Incorrect Swift tools version</li></ul><h3>Solution</h3><ul><li>Verify plugin repository versions</li><li>Use latest stable plugin releases</li><li>Open issues with plugin maintainers</li><li>Clear derived data:</li></ul><pre>rm -rf ~/Library/Developer/Xcode/DerivedData</pre><h3>3. Missing Dependencies</h3><p>Some Flutter plugins still lack SPM support.</p><p>This is especially common with:</p><ul><li>Older plugins</li><li>Plugins wrapping legacy iOS SDKs</li><li>Plugins depending heavily on CocoaPods scripts</li></ul><h3>Solution</h3><ul><li>Continue using CocoaPods temporarily</li><li>Use hybrid dependency management</li><li>Fork and add SPM support manually if needed</li></ul><h3>Recommended Migration Strategy</h3><p>For production Flutter applications:</p><h3>Recommended Path</h3><ol><li>Upgrade Flutter SDK</li><li>Enable SPM</li><li>Test plugin compatibility</li><li>Start with hybrid mode</li><li>Gradually reduce CocoaPods usage</li><li>Fully migrate when ecosystem support improves</li></ol><p>This minimizes risk while allowing teams to benefit from modern dependency management.</p><h3>When Should You Stay with CocoaPods?</h3><p>You should continue using CocoaPods if:</p><ul><li>Your project depends on older plugins</li><li>Your CI/CD pipeline is tightly coupled with pods</li><li>You rely on complex native iOS integrations</li><li>Your application is enterprise-scale and stability-critical</li></ul><h3>When Should You Move to SPM?</h3><p>SPM is ideal if:</p><ul><li>You’re starting a new Flutter project</li><li>Your plugins support SPM</li><li>You want faster builds</li><li>You prefer cleaner native integration</li><li>Your team primarily develops for Apple platforms</li></ul><h3>Final Thoughts</h3><p>Flutter support for Swift Package Manager represents an important shift toward Apple-native tooling.</p><p>However, the Flutter ecosystem is still in transition.</p><p>Right now, the best practical strategy for most teams is a <strong>hybrid CocoaPods + SPM approach</strong>, gradually moving toward full SPM adoption as plugin support matures.</p><p>Teams that plan migrations carefully can reduce build complexity, improve performance, and future-proof their iOS development workflow.</p><ul><li>Flutter</li><li>iOS</li><li>Swift</li><li>SwiftPackageManager</li><li>CocoaPods</li><li>MobileDevelopment</li><li>FlutterDev</li><li>iOSDevelopment</li><li>Xcode</li><li>SoftwareEngineering</li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=13f61121e166" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[/imagegallerysaver/ImageGallerySaverPlugin.kt:21:48 Unresolved reference ‘Registrar’.]]></title>
            <link>https://hasnainmirrani.medium.com/imagegallerysaver-imagegallerysaverplugin-kt-21-48-unresolved-reference-registrar-ac8574f31ab1?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ac8574f31ab1</guid>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 11:06:31 GMT</pubDate>
            <atom:updated>2025-09-21T11:06:31.654Z</atom:updated>
            <content:encoded><![CDATA[<p>Got it 👍<br> The root cause is exactly this part of the error:</p><pre>Unresolved reference &#39;Registrar&#39;</pre><p>That means <strong>image_gallery_saver is still using the old Flutter v1 Android embedding API</strong>, which exposes Registrar.<br> Since you’re now on Flutter 3.27 + Kotlin 1.9 + AGP 8.x, that API is completely removed → so the plugin will never compile as-is.</p><h3>✅ Fix Options</h3><pre>import &#39;package:gallery_saver/gallery_saver.dart&#39;;</pre><p>👉 This is the fastest and most future-proof fix.</p><h4>Option 2 → Patch image_gallery_saver yourself</h4><p>If you <em>must</em> keep image_gallery_saver, you’ll need to <strong>edit the plugin source</strong>:</p><ol><li>Navigate to:</li></ol><ul><li>~/.pub-cache/hosted/pub.dev/image_gallery_saver-2.0.3/android/src/main/kotlin/com/example/imagegallerysaver/ImageGallerySaverPlugin.kt</li></ul><ol><li>Replace the old Registrar-based implementation with the new v2 embedding:</li></ol><pre>package com.example.imagegallerysaver</pre><pre>import android.content.Context<br>import androidx.annotation.NonNull<br>import io.flutter.embedding.engine.plugins.FlutterPlugin<br>import io.flutter.plugin.common.MethodCall<br>import io.flutter.plugin.common.MethodChannel</pre><pre>class ImageGallerySaverPlugin : FlutterPlugin, MethodChannel.MethodCallHandler {<br>    private lateinit var channel: MethodChannel<br>    private lateinit var context: Context</pre><pre>    override fun onAttachedToEngine(@NonNull flutterPluginBinding: FlutterPlugin.FlutterPluginBinding) {<br>        context = flutterPluginBinding.applicationContext<br>        channel = MethodChannel(flutterPluginBinding.binaryMessenger, &quot;image_gallery_saver&quot;)<br>        channel.setMethodCallHandler(this)<br>    }</pre><pre>    override fun onDetachedFromEngine(@NonNull binding: FlutterPlugin.FlutterPluginBinding) {<br>        channel.setMethodCallHandler(null)<br>    }</pre><pre>    override fun onMethodCall(call: MethodCall, result: MethodChannel.Result) {<br>        // Implement your save logic here<br>        if (call.method == &quot;saveFile&quot;) {<br>            // TODO: handle saving<br>            result.success(true)<br>        } else {<br>            result.notImplemented()<br>        }<br>    }<br>}</pre><ol><li>Then rebuild your project:</li></ol><pre>flutter clean<br>flutter pub get<br>flutter run</pre><p>👉 If you don’t have custom code tied to image_gallery_saver, <strong>switching to </strong><strong>gallery_saver is by far the cleanest solution</strong>.<br> If you want, I can give you a <strong>step-by-step migration guide</strong> (replace all ImageGallerySaver.saveFile(...) calls with GallerySaver.saveImage(...) / saveVideo(...)).</p><p>Do you want me to prepare that migration guide for you?</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ac8574f31ab1" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android API Level 36 Migration Guide: Complete Flutter App Update for Android 16]]></title>
            <link>https://hasnainmirrani.medium.com/android-api-level-36-migration-guide-complete-flutter-app-update-for-android-16-346c3ca8fdf9?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/346c3ca8fdf9</guid>
            <category><![CDATA[apilevel36]]></category>
            <category><![CDATA[android-new-update]]></category>
            <category><![CDATA[edge-to-edge]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[android]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Sun, 21 Sep 2025 11:05:22 GMT</pubDate>
            <atom:updated>2025-09-21T11:05:22.285Z</atom:updated>
            <content:encoded><![CDATA[<h3>Introduction</h3><p>Android 16 (API level 36) introduces mandatory edge-to-edge display and stricter requirements. This guide covers the changes and how to migrate a Flutter app.</p><h3>What’s New in API Level 36</h3><h3>1. Mandatory Edge-to-Edge Display</h3><ul><li>Content must extend behind system bars</li><li>Apps must handle display cutouts</li><li>System bars can overlay content</li></ul><h3>2. Enhanced Security</h3><ul><li>Stricter intent redirection protections</li><li>Improved app isolation</li><li>Stronger runtime checks</li></ul><h3>3. Performance Optimizations</h3><ul><li>Better background task scheduling</li><li>Improved memory management</li><li>Faster app startup</li></ul><h3>Step-by-Step Migration Guide</h3><h3>Step 1: Update Build Configuration</h3><p>Update your android/app/build.gradle:</p><p>gradle app level</p><pre>android {<br>compileSdkVersion 36 // Changed from 35<br>ndkVersion &quot;26.1.10909125&quot;<br>defaultConfig {<br>minSdkVersion 24<br>targetSdkVersion 36 // Changed from 35<br>// … other configurations<br>}<br>}</pre><h3>Step 2: Enhance MainActivity</h3><p>Update your MainActivity.kt for edge-to-edge support:</p><p>kotlin</p><p>MainActivity.kt<br>write this lines inside main</p><pre>override fun configureFlutterEngine(flutterEngine: FlutterEngine) {<br>super.configureFlutterEngine(flutterEngine)<br>       // For API level 36, ensure edge-to-edge enforcement<br>            if (Build.VERSION.SDK_INT &gt;= 36) {<br>                // Additional configuration for Android 16 (API level 36)<br>                window.setFlags(<br>                    WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS,<br>                    WindowManager.LayoutParams.FLAG_LAYOUT_NO_LIMITS<br>                )<br>            }</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a-DucGGnkRs9eNHGCTkBdA.png" /></figure><p>Step 3: Update AndroidManifest.xml</p><p>Add predictive back gesture support:</p><p>menifest file<br>android:enableOnBackInvokedCallback=”true”</p><p>due to this when we press native back button on our app it show preview dalog if we allow then go back</p><p>but in flutter case</p><p>but it will not impact on your UI because if you are using WillpopScope it will override native code</p><p>Predictive back isn’t showing because:</p><ol><li>WillPopScope intercepts the back press</li><li>Custom navigation logic runs immediately</li><li>Flutter’s back handling takes precedence</li><li>The system preview is bypassed</li></ol><p>This is expected behavior with your current navigation setup.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*a4JXl8uZKChD8svgrUHh2g.png" /></figure><pre>&lt;activity<br>android:name=&quot;.MainActivity&quot;<br>android:configChanges=&quot;orientation|keyboardHidden|keyboard|screenSize|smallestScreenSize|locale|layoutDirection|fontScale|screenLayout|density|uiMode&quot;<br>android:exported=&quot;true&quot;<br>android:hardwareAccelerated=&quot;true&quot;<br>android:launchMode=&quot;singleTask&quot;<br>android:theme=&quot;@style/LaunchTheme&quot;<br>android:screenOrientation=&quot;portrait&quot;<br>android:windowSoftInputMode=&quot;adjustResize&quot;<br>android:enableOnBackInvokedCallback=&quot;true&quot;<br>&gt;</pre><h3>Step 4: Create API Level 36 Style Files</h3><p>Create android/app/src/main/res/values-v36/styles.xml:</p><p>xml</p><pre>&lt;item name=&quot;android:windowOptOutEdgeToEdgeEnforcement&quot;&gt;false&lt;/item&gt;</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HU-6ABFvDjlIONCty2YLmg.png" /></figure><pre>just for exmaple code<br><br>&lt;?xml version=&quot;1.0&quot; encoding=&quot;utf-8&quot;?&gt;<br>&lt;resources&gt;<br>&lt;! - Theme applied to the Android Window while the process is starting when the OS&#39;s Dark Mode setting is on →<br>&lt;style name=&quot;LaunchTheme&quot; parent=&quot;Theme.AppCompat.NoActionBar&quot;&gt;<br>&lt;item name=&quot;android:forceDarkAllowed&quot;&gt;false&lt;/item&gt;<br>&lt;item name=&quot;android:windowFullscreen&quot;&gt;true&lt;/item&gt;<br>&lt;item name=&quot;android:windowDrawsSystemBarBackgrounds&quot;&gt;true&lt;/item&gt;<br>&lt;item name=&quot;android:windowLayoutInDisplayCutoutMode&quot;&gt;shortEdges&lt;/item&gt;<br>&lt;item name=&quot;android:windowSplashScreenBackground&quot;&gt;#000000&lt;/item&gt;<br>&lt;item name=&quot;android:windowSplashScreenAnimatedIcon&quot;&gt;@drawable/android12splash&lt;/item&gt;<br>&lt;item name=&quot;android:windowSplashScreenIconBackgroundColor&quot;&gt;#000000&lt;/item&gt;<br>&lt;! - API Level 36 specific: Ensure edge-to-edge enforcement →<br>&lt;item name=&quot;android:windowOptOutEdgeToEdgeEnforcement&quot;&gt;false&lt;/item&gt;<br>&lt;/style&gt;<br>&lt;! - Theme applied to the Android Window as soon as the process has started →<br>&lt;style name=&quot;NormalTheme&quot; parent=&quot;Theme.AppCompat.Light.NoActionBar&quot;&gt;<br>&lt;item name=&quot;android:windowBackground&quot;&gt;?android:colorBackground&lt;/item&gt;<br>&lt;item name=&quot;android:windowLayoutInDisplayCutoutMode&quot;&gt;shortEdges&lt;/item&gt;<br>&lt;! - API Level 36 specific: Ensure edge-to-edge enforcement →<br>&lt;item name=&quot;android:windowOptOutEdgeToEdgeEnforcement&quot;&gt;false&lt;/item&gt;<br>&lt;/style&gt;<br>&lt;/resources&gt;</pre><h3>Understanding Edge-to-Edge Enforcement</h3><h3>What is windowOptOutEdgeToEdgeEnforcement?</h3><p>xml</p><p><em>&lt;! — OLD (API 35 and below) →</em></p><p>&lt;item name=”android:windowOptOutEdgeToEdgeEnforcement”&gt;true&lt;/item&gt;</p><p><em>&lt;! — This means: “Don’t force edge-to-edge on me” →</em></p><p><em>&lt;! — NEW (API 36) →</em></p><p>&lt;item name=”android:windowOptOutEdgeToEdgeEnforcement”&gt;false&lt;/item&gt;</p><p><em>&lt;! — This means: “Yes, I support edge-to-edge” →</em></p><h3>Why This is Required</h3><ul><li>Google Play requires edge-to-edge for API 36</li><li>System bars can overlay content</li><li>Apps must handle display cutouts</li></ul><h3>Flutter-Specific Considerations</h3><h3>Edge-to-Edge in Flutter</h3><p>Your Flutter code should already handle edge-to-edge:</p><p>dart</p><pre>@override<br>Widget build(BuildContext context) {<br>SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(<br>statusBarColor: Colors.transparent,<br>statusBarIconBrightness: Brightness.dark<br>));<br>SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge);<br>// … rest of your code<br>}</pre><h3>Predictive Back Gesture</h3><p>Note: Predictive back gesture may not show in Flutter apps because:</p><ul><li>WillPopScope intercepts back presses</li><li>Custom navigation logic runs immediately</li><li>System preview is bypassed</li></ul><p>This is expected and doesn’t affect functionality.</p><h3>Testing Your Migration</h3><h3>2. Test on Android 16 Devices</h3><ul><li>Verify edge-to-edge display</li><li>Check UI elements for overlap</li><li>Test landscape and portrait orientations</li><li>Confirm all features work</li></ul><h3>3. Common Issues and Solutions</h3><h4>Issue: UI Elements Overlapping System Bars</h4><p>Solution: Wrap content with SafeArea:</p><p>dart</p><pre>SafeArea(<br>child: YourWidget(),<br>)</pre><h4>Issue: Bottom Navigation Hidden</h4><p>Solution: Use extendBody: true in Scaffold:</p><p>dart</p><pre>Scaffold(<br>extendBody: true,<br>bottomNavigationBar: BottomNavigationBar(…),<br>)</pre><h3>Benefits of API Level 36</h3><h3>1. Google Play Compliance</h3><ul><li>Meets current requirements</li><li>Avoids rejection</li><li>Aligns with platform standards</li></ul><h3>2. Enhanced User Experience</h3><ul><li>Full-screen display</li><li>Better performance</li><li>Improved security</li></ul><h3>3. Future-Proofing</h3><ul><li>Ready for upcoming Android versions</li><li>Competitive advantage</li><li>Better user retention</li></ul><h3>Migration Checklist</h3><p>[ ] Update compileSdkVersion to 36</p><ul><li>[ ] Update targetSdkVersion to 36</li><li>[ ] Enhance MainActivity with edge-to-edge configuration</li><li>[ ] Add enableOnBackInvokedCallback=”true” to AndroidManifest.xml</li><li>[ ] Create values-v36/styles.xml files</li><li>[ ] Add windowOptOutEdgeToEdgeEnforcement=”false”</li><li>[ ] Test on Android 16 devices</li><li>[ ] Verify edge-to-edge display</li><li>[ ] Check all app features</li><li>[ ] Test different screen sizes and orientations</li></ul><h3>Conclusion</h3><p>Migrating to API level 36 is straightforward. The main changes are:</p><ol><li>Update build configuration</li><li>Enhance MainActivity for edge-to-edge</li><li>Add predictive back gesture support</li><li>Create API level 36 style files</li></ol><p>These updates ensure compliance, improve UX, and prepare the app for future Android versions.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=346c3ca8fdf9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Android 15 Edge-to-Edge Enforcement: A Complete Fix Guide for Flutter Apps]]></title>
            <link>https://hasnainmirrani.medium.com/android-15-edge-to-edge-enforcement-a-complete-fix-guide-for-flutter-apps-68820fe0ca32?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/68820fe0ca32</guid>
            <category><![CDATA[android-15]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[flutter]]></category>
            <category><![CDATA[edge-to-edge]]></category>
            <category><![CDATA[google]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Sat, 20 Sep 2025 06:20:19 GMT</pubDate>
            <atom:updated>2025-09-20T06:20:22.901Z</atom:updated>
            <content:encoded><![CDATA[<h3>The Problem That’s Breaking Your Google Play Console Uploads</h3><p>If you’re a Flutter developer who recently tried to upload your app to Google Play Console and got rejected with edge-to-edge enforcement errors, you’re not alone. Google’s Android 15 (API level 35) has introduced mandatory edge-to-edge enforcement that’s breaking thousands of apps.</p><p>In this article, I’ll walk you through exactly what’s happening, why it’s affecting your app, and provide a minimal-impact solution that fixes the issue without touching your Flutter code.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1002/1*VUX70TRjnSCabuUNmloVzQ.png" /></figure><h3>What is Edge-to-Edge Enforcement?</h3><p>Edge-to-edge display means your app content extends behind system bars (status bar and navigation bar) and you must handle the insets properly. Previously, this was optional, but Android 15 makes it mandatory for all apps targeting API level 35.</p><h3>The Technical Details</h3><p>Status Bar: The top bar showing time, battery, notifications</p><ul><li>Navigation Bar: The bottom bar with back/home/recent buttons</li><li>Edge-to-Edge: Your content draws behind these bars</li><li>Insets: The safe areas where your content should avoid overlapping</li></ul><h3>Why Your App is Affected</h3><p>Most Flutter apps are affected because they use one of these patterns:</p><p>Opt-out enforcement: android:windowOptOutEdgeToEdgeEnforcement=”true” in Android themes</p><ol><li>Legacy splash screen configuration: Not compatible with edge-to-edge</li><li>Missing display cutout handling: For devices with notches/punch holes</li></ol><h3>The Google Play Console Error</h3><p>You’ll see errors like:</p><ul><li>“Edge-to-edge enforcement is required for apps targeting Android 15”</li><li>“App crashes on launch due to splash screen configuration”</li><li>“UI elements are occluded by system bars”</li></ul><h3>The Solution: Minimal Native Android Changes</h3><p>Good news: If your Flutter code already uses SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge), you likely don’t need to change any Dart code!</p><p>The fix is primarily in your Android native configuration.</p><h3>Step 1: Remove Opt-Out Enforcement</h3><p>Update all your Android theme files to remove the opt-out and add proper cutout handling:</p><p>File: android/app/src/main/res/values/styles.xml</p><p>xml</p><pre>&lt;style name=&quot;NormalTheme&quot; parent=&quot;Theme.AppCompat.Light.NoActionBar&quot;&gt;<br>&lt;item name=&quot;android:windowBackground&quot;&gt;@drawable/splash&lt;/item&gt;<br>&lt;! - Remove this line: →<br>&lt;! - &lt;item name=&quot;android:windowOptOutEdgeToEdgeEnforcement&quot;&gt;true&lt;/item&gt; →<br>&lt;! - Add this line: →<br>&lt;item name=&quot;android:windowLayoutInDisplayCutoutMode&quot;&gt;shortEdges&lt;/item&gt;<br>&lt;/style&gt;</pre><p>Repeat for:</p><ul><li>android/app/src/main/res/values-v31/styles.xml</li><li>android/app/src/main/res/values-night/styles.xml</li><li>android/app/src/main/res/values-night-v31/styles.xml</li></ul><h3>Step 2: Update MainActivity (Optional but Recommended)</h3><p>Add minimal edge-to-edge configuration to your MainActivity:</p><p>File: android/app/src/main/kotlin/…/MainActivity.kt</p><p>kotlin</p><pre>import android.os.Build<br>// … existing imports<br>class MainActivity : FlutterFragmentActivity() {<br>override fun configureFlutterEngine(flutterEngine: FlutterEngine) {<br>super.configureFlutterEngine(flutterEngine)<br>// Configure edge-to-edge for Android 15+ compatibility<br>configureEdgeToEdge()<br>// … rest of your existing code<br>}<br>/**<br>* Configure edge-to-edge display for Android 15+ compatibility<br>*/<br>private fun configureEdgeToEdge() {<br>if (Build.VERSION.SDK_INT &gt;= 35) { // Android 15 (API level 35)<br>window.attributes.layoutInDisplayCutoutMode =<br>WindowManager.LayoutParams.LAYOUT_IN_DISPLAY_CUTOUT_MODE_SHORT_EDGES<br>}<br>}<br>}</pre><h3>Step 3: Verify Your Flutter Code</h3><p>Check that your lib/main.dart has proper edge-to-edge setup:</p><p>dart</p><pre>@override<br>Widget build(BuildContext context) {<br>SystemChrome.setSystemUIOverlayStyle(const SystemUiOverlayStyle(<br>statusBarColor: Colors.transparent,<br>statusBarIconBrightness: Brightness.dark<br>));<br>SystemChrome.setEnabledSystemUIMode(SystemUiMode.edgeToEdge);<br>// … rest of your code<br>}</pre><p>If you have this, don’t change it — it’s correct!</p><h3>What This Fix Accomplishes</h3><p>✅ Resolves Google Play Console rejection</p><p>✅ Prevents splash screen crashes on Android 15</p><p>✅ Ensures proper display cutout handling</p><p>✅ Maintains all existing app functionality</p><p>✅ Zero performance impact</p><h3>Common Issues and Solutions</h3><h3>Issue: App Still Crashes on Launch</h3><p>Solution: Check your splash screen configuration. If using flutter_native_splash, ensure it’s compatible with edge-to-edge.</p><h3>Issue: UI Elements Overlap System Bars</h3><p>Solution: Add SafeArea widgets around content that might overlap:</p><p>dart</p><pre>SafeArea(<br>child: YourWidget(),<br>)</pre><h3>Issue: Bottom Navigation Hidden</h3><p>Solution: Ensure your bottom navigation handles insets properly:</p><p>dart</p><pre>Scaffold(<br>extendBody: true, // Allows content behind bottom bar<br>bottomNavigationBar: BottomNavigationBar(<br>// Your navigation bar<br>),<br>)</pre><h3>Testing Your Fix</h3><p>Build your app with the changes</p><ol><li>Test on Android 15 device or emulator</li><li>Check all screens for UI overlap issues</li><li>Verify splash screen loads without crashes</li><li>Test edge cases: landscape mode, different screen sizes</li></ol><h3>Performance Impact</h3><p>Zero impact on:</p><ul><li>App startup time</li><li>Memory usage</li><li>Battery life</li><li>Existing functionality</li></ul><p>The changes are purely configuration-based and don’t affect your app’s runtime performance.</p><h3>Migration Timeline</h3><p>Android 15: Edge-to-edge enforcement begins</p><ul><li>Google Play: Rejecting apps without proper configuration</li><li>Deadline: Immediate for new uploads targeting API 35</li></ul><h3>Additional Resources</h3><ul><li><a href="https://developer.android.com/develop/ui/views/layout/edge-to-edge">Display content edge-to-edge in views | Views | Android Developers</a></li><li><a href="https://api.flutter.dev/flutter/services/SystemChrome-class.html">SystemChrome class - services library - Dart API</a></li></ul><p><a href="https://developer.android.com/about/versions/15/behavior-changes-15">https://developer.android.com/about/versions/15/behavior-changes-15</a></p><h3>Conclusion</h3><p>The Android 15 edge-to-edge enforcement is a significant change, but the fix is straightforward. By making minimal native Android configuration changes, you can resolve Google Play Console rejections without touching your Flutter code.</p><p>The key is understanding that this is primarily a system-level configuration issue, not a Flutter framework problem. Your Flutter edge-to-edge code was likely already correct — it just needed the Android system to stop blocking it.</p><p>Remember: Test thoroughly on Android 15 devices before submitting to Google Play Console. The edge-to-edge enforcement is strict, and any UI overlap issues will cause rejection.</p><p><em>Have you encountered this issue? Share your experience in the comments below. If this article helped you, please give it a clap and share it with your fellow developers!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68820fe0ca32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Preparing Your Flutter Apps for Android’s 16 KB Page Size]]></title>
            <link>https://hasnainmirrani.medium.com/preparing-your-flutter-apps-for-androids-16-kb-page-size-b0ba3b5ac448?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/b0ba3b5ac448</guid>
            <category><![CDATA[16-kb]]></category>
            <category><![CDATA[dart]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[16-kb-page-size]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Sat, 20 Sep 2025 05:15:24 GMT</pubDate>
            <atom:updated>2025-09-20T05:15:52.882Z</atom:updated>
            <content:encoded><![CDATA[<p>Google is introducing a major update to Android’s memory management. Starting <strong>November 1, 2025</strong>, <strong>Google Play will require all new apps and updates targeting Android 15 (API level 36) or higher to support 16 KB memory pages</strong>.</p><p>If you’re a Flutter developer, you might be wondering:<br> 👉 Does this affect my app?<br> 👉 Do I need to make code changes?<br> 👉 How can I prepare in advance?</p><p>This article gives you a <strong>step-by-step guide</strong>, tailored for Flutter projects, so you can confidently meet this new requirement.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0plb4P8tH-uO1_tXOz-7FQ.png" /></figure><h3>🔎 What is the 16 KB Page Size?</h3><p>A <strong>page</strong> is the smallest unit of memory allocation in an operating system.</p><ul><li>Historically, Android has used <strong>4 KB pages</strong>.</li><li>Android 15 introduces support for <strong>16 KB pages</strong>.</li><li>Benefits: better performance for modern devices, reduced overhead in memory translation, and future scalability.</li></ul><p>For most apps, this is invisible. But if your app (or its dependencies) include <strong>native libraries (</strong><strong>.so files)</strong>, you need to ensure they’re compatible with 16 KB pages.</p><p>👀 Who is Affected?</p><p>✅ <strong>Not affected (usually):</strong> Pure-Dart Flutter apps with no native dependencies.</p><p>⚠️ <strong>Affected:</strong></p><ul><li>Apps that include .so binaries (either directly or via plugins/SDKs).</li><li>Common examples: game engines, camera/video SDKs, analytics/ads libraries, crypto/DB libraries (e.g., SQLCipher, OpenSSL).</li></ul><p>💡 <strong>Pro tip:</strong> Even if you don’t write native code, many Flutter plugins ship with native binaries. Always check!</p><h3>🛠️ Step-by-Step Guide for Flutter Developers</h3><h3>1. Audit Your Build</h3><p>Check if your app contains native libraries:</p><pre>unzip -l build/app/outputs/bundle/release/app-release.aab | grep &#39;\.so$&#39;</pre><p>If you see .so files, you’re affected.</p><h3>2. Update Your Toolchain</h3><ul><li><strong>Flutter</strong> → Update to the latest stable release.</li><li><strong>Android Gradle Plugin (AGP)</strong> → Use version <strong>8.5.1+</strong>.</li><li><strong>NDK</strong> → Install <strong>r28+</strong>.</li><li><strong>Gradle</strong> → Upgrade to the version required by your AGP.</li></ul><p>In android/gradle.properties:</p><pre>android.ndkVersion=28.0.12433566</pre><h3>3. Rebuild Your App</h3><pre>flutter clean<br>flutter build appbundle --target-platform android-arm64,android-arm,android-x64</pre><h3>4. Test on a 16 KB Device/Emulator</h3><p>Verify page size:</p><pre>adb shell getconf PAGE_SIZE<br># Expected output: 16384</pre><p>If your app runs without crashes — you’re good!</p><p>🧪 Debugging Checklist</p><ul><li>Test on an <strong>Android 15 emulator</strong> with 16 KB pages.</li><li>On real devices, enable developer option: <em>Boot with 16 KB page size</em>.</li><li>If Play Console rejects your build, check the <strong>App Bundle Explorer</strong> for non-aligned .so files.</li></ul><h3>📌 Key Takeaways</h3><ul><li><strong>Deadline:</strong> Nov 1, 2025.</li><li><strong>Safe if:</strong> Your Flutter app has no native libs.</li><li><strong>Action if:</strong> You or your plugins use .so files → rebuild with AGP 8.5.1+, NDK r28+, and Flutter stable.</li><li><strong>Always test</strong> on a 16 KB device/emulator before publishing.</li></ul><h3>📚 References</h3><ul><li>Android Developer Docs: Support 16 KB Page Sizes</li><li>Android Developers Blog: Prepare your apps for 16 KB page size</li><li>NDK r28 Release Notes</li></ul><p>✍️ <em>Written by Hasnain Mirrani</em><br> 📱 Flutter &amp; Mobile Dev | 🚀 Sharing practical guides for developers</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b0ba3b5ac448" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Fixing iOS Build Error in Flutter: “Profile doesn’t match the entitlements file’s value for the…]]></title>
            <link>https://hasnainmirrani.medium.com/fixing-ios-build-error-in-flutter-profile-doesnt-match-the-entitlements-file-s-value-for-the-4b5d5db2f0bd?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b5d5db2f0bd</guid>
            <category><![CDATA[entitlement]]></category>
            <category><![CDATA[profiledoesntmatch]]></category>
            <category><![CDATA[ios]]></category>
            <category><![CDATA[build-error]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 12:26:45 GMT</pubDate>
            <atom:updated>2025-08-29T15:26:51.775Z</atom:updated>
            <content:encoded><![CDATA[<h3>Failed to install embedded profile for mg.telma.mvolaapp : 0xe800801f (Attempted to install a Beta profile without the proper entitlement.</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*FX9co83qQ7ZvYdSC9ic-VA.png" /></figure><p>Profile doesn’t match the entitlements file’s value for the application-identifier entitlement</p><p>This usually happens because your <strong>provisioning profile</strong> and the <strong>entitlements file</strong> don’t align with your configured signing settings. In simple words: Xcode/Flutter is trying to sign your app with mismatched credentials.</p><h3>✅ The Fix</h3><p>I solved this issue by enabling <strong>“Automatically manage signing”</strong> in Xcode for both <strong>Debug</strong> and <strong>Release</strong> build configurations.</p><h3>Steps:</h3><p>Open your project in <strong>Xcode</strong> (ios/Runner.xcworkspace).</p><p>Select the <strong>Runner project</strong> in the sidebar.</p><p>Go to the <strong>Signing &amp; Capabilities</strong> tab.</p><p>For both <strong>Debug</strong> and <strong>Release</strong>:</p><p>✅ Check <strong>Automatically manage signing</strong>.Select your <strong>Team</strong> (Apple Developer Account).</p><p>flutter clean<br>flutter pub get<br>flutter run</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b5d5db2f0bd" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Warning: The plugin camera_android requires Android SDK version 36 or higher.]]></title>
            <link>https://hasnainmirrani.medium.com/warning-the-plugin-camera-android-requires-android-sdk-version-36-or-higher-ec56f8f91a8b?source=rss-3cbdcddab1e5------2</link>
            <guid isPermaLink="false">https://medium.com/p/ec56f8f91a8b</guid>
            <category><![CDATA[sdk]]></category>
            <category><![CDATA[android]]></category>
            <category><![CDATA[higher]]></category>
            <category><![CDATA[android-sdk]]></category>
            <category><![CDATA[version]]></category>
            <dc:creator><![CDATA[Hasnain Mirrani]]></dc:creator>
            <pubDate>Fri, 29 Aug 2025 10:24:09 GMT</pubDate>
            <atom:updated>2025-08-29T10:24:09.148Z</atom:updated>
            <content:encoded><![CDATA[<p>teps to update the Android SDK:</p><ul><li><strong>Open Android Studio:</strong> Launch your Android Studio IDE.</li><li><strong>Access SDK Manager:</strong> Navigate to Tools &gt; SDK Manager.</li><li><strong>Select SDK Platforms:</strong> In the “SDK Platforms” tab, locate and select “Android SDK Platform 36” (or the latest available version higher than 36).</li><li><strong>Select SDK Tools (if needed):</strong> In the “SDK Tools” tab, ensure that the necessary build tools and platform tools are updated to compatible versions with the new SDK platform.</li><li><strong>Apply Changes:</strong> Click “Apply” or “OK” to download and install the selected SDK components.</li><li><strong>Update Project Configuration (if necessary):</strong> After updating the SDK, you might need to adjust the compileSdkVersion in your project&#39;s build.gradle file (located in android/app/build.gradle for Flutter projects) to match the newly installed SDK version (e.g., compileSdkVersion 36).</li></ul><p>By updating the Android SDK to the required version, the camera_android plugin will find the necessary platform support and the warning should no longer appear during compilation.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=ec56f8f91a8b" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>