Solved Android 11+ storage permission issue in React Native

🚨 Attention App Developers 🚨 Google Play is updating its requirements and it will affect all app updates soon. What's Changing? Starting November 1, 2025, all Android apps must support 16 KB memory pages. If your app doesn’t meet this requirement, Google Play will reject your updates. - Pure Dart apps are unaffected. - Apps using native .so libraries through plugins must be rebuilt. Failing to comply can lead to install failures, crashes, or even Play Store rejection. From May 2026, no updates will be allowed without 16 KB page support. How to Prepare 1. Update your toolchain: Use AGP 8.5.1+, the latest Gradle version, and NDK r28+ 2. Upgrade your Flutter SDK and plugins—many already support 16 KB pages 3. Rebuild your app: flutter clean && flutter build appbundle 4. Test your device (Android 15+): adb shell getconf PAGE_SIZE This is mandatory; apps not compliant will be blocked from updating. We have already started updating our projects. Have you made sure your apps and dependencies are ready to? #Flutter #FlutterDev #AndroidDev #MobileApps #GooglePlay #AppUpdate

🚨 Android 15 introduces a new 16 KB page size — are your React Native apps ready? Starting November 1, 2025, Google Play will require all apps targeting Android 15+ to be built with 16 KB memory page alignment. Apps shipping misaligned native libraries (.so files) risk crashes, poor performance, or outright Play Store rejection. Why this matters: ⚡ Faster launches (up to 30% in some apps) 🔋 Better battery efficiency 📸 Improved camera startup times 🚀 Smoother system performance For React Native apps, this is critical since RN bundles multiple native .so libraries (libreactnativejni.so, libhermes.so, etc.). 🔧 How to prepare: Upgrade to React Native 0.76+ and Hermes 0.16+ (built with 16 KB alignment). Inspect .so files in your APK/AAB using llvm-objdump or readelf. Rebuild/update third-party native modules with -Wl,-z,max-page-size=0x4000. Add CI/CD checks to block misaligned .so files before release. 📌 Key takeaway: Don’t wait until Google enforces this. Start verifying and aligning your builds now to ensure your React Native apps remain Play Store ready, stable, and optimized. #ReactNative #Android15 #MobileDevelopment #PlayConsole #AppPerformance

Are you ready for the 16KB memory page update in Flutter apps? By November 1, 2025, Google Play will require this for all new and updated apps. This update is set to improve app performance and battery life. While pure Dart code is fine, native Android code in plugins needs attention. Here's what I'm doing: 1. Updating my toolchain to the latest versions. 2. Ensuring all plugins are 16KB-compatible. 3. Testing thoroughly on Android 15+ devices. This is a pivotal moment for developers. How are you tackling this change? Let's connect and share strategies! #TechTrends #FlutterDevelopers #AppInnovation

🚨 Important Update for Android Developers 🚨 Google Play has announced a new requirement: 👉 From May 1, 2026, all apps targeting Android 15+ must support 16 KB memory page sizes. 📌 If your app doesn’t support this, you won’t be able to release updates after the deadline. This change mainly impacts apps with native libraries (.so files). Many popular dependencies still need to update, so it’s critical for developers to: ✅ Check your .aab builds with bundletool ✅ Update or replace libraries that don’t support 16 KB pages ✅ Stay ahead before your app release pipeline gets blocked This is a big shift, and many developers may not be aware yet. Time to prepare now. #AndroidDev #GooglePlay #AppDevelopment #MobileApps #ReactNative #Android15

React Native Developers — Time to Get Ready for Android 15! Android 15 brings a major change: a 16 KB memory page size requirement. This update could affect how your React Native apps behave — especially if you're using native modules or custom libraries. In my latest blog, I cover: ✅ What this change means for React Native apps 🔍 How to check your app’s compatibility 🧩 Steps to ensure your app is future-proof 📖 Read the full article here: 👉 https://lnkd.in/gEtY7S2P Let’s stay ahead of platform changes and keep our apps running smoothly! 🚀 #ReactNative #Android15 #MobileDevelopment #TechBlog #SantoshBotre #AndroidDev #MemoryOptimization #ReactNativeTips

Exciting News for Android Developers and Flutter Enthusiasts! 📱 Starting Nov 1, 2025, a significant change is coming to the Android app development scene. Google has announced that all apps targeting Android 15+ (SDK 35+) must now support 16KB memory pages. Why does this matter? 🚀 - Enjoy faster app launches - Enhance your device's battery life - Experience quicker system boot times Here's what you need to do to stay ahead of the curve: 🛠️ 👨💻 For Android Developers: - Update NDK to version r26+ - Recompile native code - Test your app on Android 15 - Verify third-party libraries (.so files) 👨💻 For Flutter Developers: - Update Flutter/Dart - Refresh native plugins - Rebuild your app using the new NDK - Replace or fork outdated plugins Remember: ⚠️ Apps that are not ready for this transition risk rejection from Google Play. Ensure your app is aligned with the new requirements to avoid any setbacks. Is your team prepared for this 16KB shift? Share your thoughts and readiness in the comments below. Let's engage in a discussion on how this change will impact mobile development moving forward. ⬇️ #Android #Flutter #GooglePlay #MobileDevelopment #NDK #TechUpdate #Android15

⚠️ Big change coming for Android developers! If your app doesn’t support 16 KB memory pages, Google Play will block your updates starting November 2025. 🚨 Important Update for App Developers 🚨 Google Play has introduced a new requirement that will affect all Android app updates. 🔴 What’s Changing? ➡️ Starting November 1, 2025, all Android apps must support 16 KB memory pages ➡️ If your app isn’t ready, Google Play will reject your update ✅ Pure Dart apps are already safe ⚠️ Apps using plugins with native .so libraries must be rebuilt 📅 From May 2026, no app updates will be allowed without 16 KB compatibility. 🛠 Steps to Prepare: 1️⃣ Upgrade your toolchain → use AGP 8.5.1+, latest Gradle, and NDK r28+ 2️⃣ Update Flutter SDK + plugins (most already support 16 KB) 3️⃣ Rebuild your app: Command: flutter clean && flutter build appbundle 4️⃣ Test on Android 15 with: Command: adb shell getconf PAGE_SIZE ⚡ Don’t wait until the last moment—prepare now to avoid Play Store rejection. 👉 I’ve already started updating my projects. Have you checked your apps and dependencies yet? 📖 More details from Google: https://lnkd.in/dWymAWxZ #Flutter #FlutterDev #AndroidDev #MobileAppDevelopment #GooglePlay #AppUpdates #AndroidDevelopers #MobileApps #AppPublishing #NDK #Gradle #AppDevelopment #DevCommunity #TechUpdate #MobileDev

🚨 Important Update for Application Developers Google Play is changing the rules, and this will impact all app updates soon. Issue Starting from November 1, 2025, all Android Apps must support 16 KB Memory Pages. If your app build isn't ready within 16 KB Memory Pages, Google Play will reject your update. Pure Dart apps are safe. Apps using plugins with native .so libraries need rebuilding. lgnoring this can cause install failures, crashes, or Play Store rejection. From May 2026 onward, no app updates will go live without 16 KB support. Solution / How to Prepare Upgrade your toolchain use AGP 8.5.1+, latest Gradle, and NDK r28+ 1- Update Flutter SDK and plugins (most are already supporting 16 KB). 2- Rebuild your app: flutter clean && flutter build appbundle 3- Test on Android 15 with 16 KB Memory Pages: adb shell getconf PAGE_SIZE . This is not optional - if you dont act now your app updates will be blocked. I've already started preparing my projects for this. Have you checked whether your apps and plugins are ready? #Flutter #Dart #Cross_Platform_Development

📢Exciting news from portfolio company! We’re proud to announce the public launch of Darvin.dev, the world’s most accessible AI-native builder for real mobile apps. With Darvin, anyone can turn a simple idea— written in natural language into a fully functioning app, ready for the Google Play or App Store. No code. No setup. No barriers. 📌Why Darvin Matters • Built for non-developers: The interface is clean and jargon-free—no coding required. • Real native performance: Unlike React Native–based rivals such as a16z-backed Rork, Darvin generates Flutter apps that compile into true Android and iOS binaries—delivering smooth, reliable, native-quality experiences. • One-click store-ready binaries: Generate Android builds (iOS coming soon) instantly—no local tools, no setup. Learn more: https://darvin.dev/

I’ll eventually build native iOS and Android apps, but I also want the web version of my app to feel as close to native as possible. The challenge is that some small details on the web don’t fully match the native experience. Take a simple button, for example: in iOS, if you press down on a button but release your finger outside of it, the action is canceled. On the web, once you start pressing, the action always fires no matter where you release your touch, there’s no built-in way to cancel it. I worked on fixing this behavior for the web, and here’s the source code if you’d like to check it out: https://lnkd.in/d9rMMTM4