<?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 RANVIR GORAI on Medium]]></title>
        <description><![CDATA[Stories by RANVIR GORAI on Medium]]></description>
        <link>https://medium.com/@gorairanvir?source=rss-3c69826fc791------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*pFrAXM2ecFw5yRzvK-lXXQ.png</url>
            <title>Stories by RANVIR GORAI on Medium</title>
            <link>https://medium.com/@gorairanvir?source=rss-3c69826fc791------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sat, 21 Nov 2026 13:26:10 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@gorairanvir/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 Android Tool That Finally Got My Phone Out of the Way]]></title>
            <link>https://medium.com/@gorairanvir/the-android-tool-that-finally-got-my-phone-out-of-the-way-4fb3d7f03977?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/4fb3d7f03977</guid>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sat, 29 Aug 2026 16:11:42 GMT</pubDate>
            <atom:updated>2026-08-29T16:13:09.591Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GeLEn56SQtvVuEQVC0MFQQ.png" /></figure><p>As an Mobile App developer, I spend a lot of time jumping between my editor, terminal, browser, and a physical Android device.</p><p>And honestly, debugging on a real device can sometimes be more distracting than productive.</p><p>I recently ran into exactly that problem.</p><p>I wanted to keep my focus on my development machine while still having complete access to my Android device.</p><p>That’s when I found <strong>AYA</strong>.</p><p>And it fit my workflow surprisingly well.</p><p>The problem I was trying to solve</p><p>My usual setup involved running an Android emulator/AVD whenever I needed to test something.</p><p>The problem was that an emulator isn’t always the best option.</p><p>For some workflows, I need:</p><ul><li>Real hardware behavior</li><li>Actual device performance</li><li>Device-specific UI</li><li>Physical keyboard/input behavior</li><li>Real Android system behavior</li><li>Device logs</li><li>UI hierarchy inspection</li></ul><p>I had already created a few CLI commands to automate repetitive tasks, which helped.</p><p>But I was still switching between:</p><p>Laptop → Phone → Terminal → Phone → Laptop</p><p>And sharing my physical device screen during a video call wasn’t particularly convenient either.</p><p>I wanted something simpler:</p><p>Keep the phone on my desk, but make it feel like another window on my computer.</p><p>That’s where AYA came in.</p><h3>What is AYA?</h3><p>AYA is an open-source Android ADB desktop application that provides a graphical interface for controlling and inspecting Android devices.</p><p>The project describes itself as a GUI wrapper around ADB, but that description undersells how useful it can be in a day-to-day development workflow.</p><p>It brings several Android-development tasks into one desktop interface:</p><ul><li>Screen mirroring</li><li>Keyboard and mouse control</li><li>Screenshots</li><li>Screen recording</li><li>File explorer</li><li>Application management</li><li>Process monitoring</li><li>Performance monitoring</li><li>Layout inspection</li><li>Logcat</li><li>Interactive shell</li><li>Remote/wireless device connections</li></ul><p>And that’s exactly what I was looking for.</p><h3>My favorite setup</h3><p>My current mental model for debuging app is pretty simple:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TmRa1_7_5nQS8NktfhMjeg.png" /></figure><h3>Final thoughts</h3><p>The best developer tools aren’t necessarily the ones with the most features.</p><p>They’re the ones that remove friction from things you already do every day.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4fb3d7f03977" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ I Built a Production-Ready RAG Agent That Understands PDFs, Documentation, and Internal…]]></title>
            <link>https://medium.com/@gorairanvir/i-built-a-production-ready-rag-agent-that-understands-pdfs-documentation-and-internal-c62ec20bfbf0?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/c62ec20bfbf0</guid>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sun, 31 May 2026 06:20:56 GMT</pubDate>
            <atom:updated>2026-05-31T06:20:56.134Z</atom:updated>
            <content:encoded><![CDATA[<h3>🚀 I Built a Production-Ready RAG Agent That Understands PDFs, Documentation, and Internal Knowledge, Running 100% On-Premise</h3><p>No cloud. No API keys. No data leaving my machine.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xdlr6V7YCP8DTw30DNOP1A.png" /></figure><p>Large Language Models are great, until you need answers from your own documents.</p><p>Whether it’s a 500-page PDF, an internal wiki, API documentation, compliance manuals, research papers, or engineering runbooks, finding the right information often means spending more time searching than actually working.</p><p>Cloud-based AI tools can help, but they introduce a new challenge:</p><p>Do you really want to upload confidential company documents, internal SOPs, customer data, or proprietary knowledge to a third-party service?</p><p>I didn’t.</p><p>So I built a Production-Ready RAG (Retrieval-Augmented Generation) Agent that can ingest PDFs, documentation websites, and knowledge bases, then answer questions with grounded responses and source citations, all while running entirely on my laptop.</p><ul><li>No OpenAI API</li><li>No cloud infrastructure.</li><li>No recurring costs.</li><li>No data leaving the machine.</li></ul><p>Just a private AI knowledge assistant powered by local models, a vector database, and a modern RAG architecture.</p><h3>What is qa-agent?</h3><p>qa-agent is an on-premise AI assistant designed to transform static documents into a searchable knowledge system.</p><p>Instead of manually digging through PDFs and documentation, you simply ask questions in natural language.</p><p>The system retrieves relevant information from your documents and generates answers based only on that context.</p><h3>Supported Knowledge Sources</h3><ul><li>📄 PDFs</li><li>🌐 Documentation websites</li><li>📚 Technical manuals</li><li>🔧 API documentation</li><li>📋 Internal SOPs</li><li>🏢 Company knowledge bases</li><li>📑 Research papers</li><li>📖 Product documentation</li></ul><h3>Key Features</h3><ul><li>✅ Fully On-Premise Deployment</li><li>✅ Production-Ready RAG Architecture</li><li>✅ Source-Cited Responses</li><li>✅ Local LLM Inference with Ollama</li><li>✅ Vector Search with Qdrant</li><li>✅ Streaming Responses</li><li>✅ No Hallucination-First Design</li><li>✅ Re-ingest Documents Without Duplicates</li><li>✅ Works Offline</li><li>✅ Enterprise-Friendly Privacy</li></ul><p>Think of it as ChatGPT for your private knowledge , but entirely under your control.</p><p><strong>Real-World Use Cases</strong></p><p><strong>Engineering Teams</strong><br>Ask:<br>“How do we deploy the authentication service?”<br>Instead of searching through hundreds of pages of documentation.</p><p><strong>Customer Support</strong><br>Ask:<br>“What is the refund policy for enterprise customers?”<br>and receive answers directly from support documentation.</p><p><strong>Compliance &amp; Legal</strong><br>Search thousands of pages of policies and regulatory documents instantly.</p><p><strong>Research Teams</strong><br>Query large collections of whitepapers and research documents using natural language.<br>Internal Knowledge Assistants<br>Turn company documentation into an AI-powered help desk.</p><p><strong>Product Teams</strong><br>Ask questions across release notes, product specifications, and technical requirements.<br>This is where a private RAG Agent becomes incredibly valuable.</p><p><strong>My biggest takeaway:</strong> a production-ready RAG agent isn’t just an AI chatbot it’s a knowledge platform that helps people find the right information faster, while keeping data secure and under their control.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c62ec20bfbf0" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Practical Guide to Flutter Development]]></title>
            <link>https://medium.com/@gorairanvir/a-practical-guide-to-flutter-development-5bea2caeb080?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/5bea2caeb080</guid>
            <category><![CDATA[apps]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <category><![CDATA[flutter-app-development]]></category>
            <category><![CDATA[flutter]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sat, 17 Jan 2026 03:18:24 GMT</pubDate>
            <atom:updated>2026-01-17T03:18:24.343Z</atom:updated>
            <content:encoded><![CDATA[<p>Before diving into the actual setup of Flutter on your machine, it’s important to understand what Flutter is and why it’s worth learning. Having this context will make the setup process and your learning journey, much smoother.</p><p><strong>What is Flutter?</strong></p><p>Flutter is an open-source UI framework used to build cross-platform applications from a single codebase. With Flutter, you can create apps for Android, iOS, web, desktop (Windows, macOS, Linux) without writing separate code for each platform.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*uUERGjS0F9p02romVoAxgg.jpeg" /></figure><p>At its core, Flutter provides:<br> • A rich set of pre-built UI widgets<br> • A reactive rendering engine<br> • A fast development experience with Hot Reload</p><p>Instead of relying on native UI components, Flutter renders everything itself using its own high-performance engine. This allows developers to achieve consistent UI and behavior across platforms while maintaining near-native performance.</p><p>Flutter applications are written in <strong>Dart</strong>, a modern programming language designed for building fast, scalable user interfaces. Dart is easy to learn, especially if you have prior experience with JavaScript, Java, or other object-oriented languages.</p><p><strong>Why Flutter?</strong></p><p>Flutter is popular because it:<br> • 🚀 Speeds up development with a single codebase<br> • 🎨 Makes it easy to build beautiful, custom UIs<br> • ⚡ Offers excellent performance close to native apps<br> • 🔥 Provides Hot Reload for faster iteration</p><p>Because of these advantages, Flutter is widely used by startups and large companies alike for building production-ready applications.</p><h4><strong>Easy Steps to Set Up Flutter on Your MAC System</strong></h4><p>Setting up Flutter is straightforward and doesn’t take much time. Follow the steps below to get your development environment ready.</p><p><strong>1. Install Git<br></strong>Flutter uses Git internally to manage and update its SDK.<br>If Git is not already installed on your system, install it first.Install Xcode Command Line Tools (macOS)</p><p><strong>2. Install Xcode Command Line Tools </strong><br>by running the following command in your terminal:</p><pre>xcode-select --install</pre><p><strong>3. Install Visual Studio Code &amp; extension</strong><br>Download and install Visual Studio Code (VS Code) , a lightweight and popular code editor widely used for Flutter development.<br>Open VS Code and install the following extensions:<br> • <a href="https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter">Flutter</a><br> • Dart</p><p><strong>4. Create a New Flutter Project</strong><br>Once the extensions are installed:<br> 1. Open VS Code<br> 2. Press Cmd + Shift + P (macOS) or Ctrl + Shift + P (Windows/Linux)<br> 3. Select Flutter: New Project</p><p><strong>5. Run Your First Flutter App 🎉</strong><br>After the setup is complete:<br> • Create a new Flutter project<br> • Select a device or emulator<br> • Run the app</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ppH082GgkHBl5fosS0m7Lw.png" /></figure><p><strong>Conclusion<br></strong>In this article, we learned what Flutter is and how to set it up to run applications on our system. With the environment ready, you can now start building cross-platform apps using Flutter.</p><p>Happy coding! 🚀</p><p><strong>References</strong><br> • Flutter Official Documentation: <a href="https://docs.flutter.dev/">https://docs.flutter.dev</a><br> • Flutter Installation Guide: <a href="https://docs.flutter.dev/get-started/install">https://docs.flutter.dev/get-started/install</a><br> • Dart Programming Language: <a href="https://dart.dev/">https://dart.dev</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5bea2caeb080" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native CLI vs Expo in 2026: What Should You Choose?]]></title>
            <link>https://medium.com/@gorairanvir/react-native-cli-vs-expo-in-2026-what-should-you-choose-c8e161ced13b?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/c8e161ced13b</guid>
            <category><![CDATA[expo]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[mobile-app-development]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Tue, 13 Jan 2026 07:02:04 GMT</pubDate>
            <atom:updated>2026-01-13T07:02:04.752Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="RN VS EXPO" src="https://cdn-images-1.medium.com/max/1000/1*_f0n7Qzru6-FrtfmvKPyow.png" /></figure><p>If you’re starting a new React Native app in 2026, one question almost always comes up:</p><p><strong>Should I use React Native CLI or Expo?</strong></p><p>If you follow the official React Native documentation, you’ll notice a strong recommendation toward Expo. And honestly, it makes sense. Expo has matured a lot over the years and is no longer “just for demos.”</p><p>But here’s the truth:</p><p>👉 Expo is not the only option, and<br>👉 React Native CLI still plays a very important role in real-world production apps.</p><p>Let’s break this down in a practical, no-hype way.</p><p>When Expo Feels Like Magic ✨</p><p>If you’re building:<br> • APOC<br> • Ademo app<br> • Ahackathon project</p><p>Expo is an excellent choice.</p><p>Why Expo shines:<br> • ⚡ Super fast setup, you’re productive in minutes<br> • 📱 No Android Studio or Xcode required initially<br> • 🔁 Hot reload &amp; live preview with Expo Go<br> • 🧰 Tons of APIs out of the box (camera, media, sensors, etc.)<br> • 🚀 Easy deployment with Expo services</p><p>For learning, experimenting, or showcasing an idea quickly, Expo is unbeatable.</p><p>No arguments there.</p><p>But What About Production Apps? 🤔</p><p>This is where the discussion gets interesting.</p><p>If you’re planning to build a serious, long-term, production-ready app especially one that:<br> • Requires deep native customization<br> • Includes platform-specific logic<br> • Has a custom build pipeline<br> • Or needs full architectural control</p><p>👉 React Native CLI still has a strong edge.</p><p>Why Many Teams Still Choose React Native CLI</p><p>1. Full Control, Zero Abstraction</p><p>React Native CLI gives you a clean, minimal setup , no extra layers unless you add them.<br> • You design your own architecture<br> • You decide the folder structure<br> • You create your own design system<br> • You control every dependency</p><p>No hidden magic. No surprises.</p><p>2. Native Code Is the Reality</p><p>Let’s be honest: Almost every real-world React Native app touches native code at some point.</p><p>Whether it’s:<br> • Custom SDK integration<br> • Performance optimizations<br> • Native UI components<br> • Platform-specific features</p><p>React Native CLI handles Android &amp; iOS native code naturally, without workarounds or ejecting.</p><p>3. Fewer Dependency Surprises</p><p>Expo has improved massively, but it still:<br> • Adds an extra dependency layer<br> • Depends on Expo-managed APIs<br> • May introduce version constraints</p><p>With React Native CLI:<br> • Fewer moving parts<br> • Direct dependency control<br> • Easier long-term maintenance for large teams</p><p>4. Custom CI/CD &amp; Build Pipelines</p><p>For companies that:<br> • Use custom CI/CD<br> • Have multiple environments<br> • Need custom signing &amp; deployment<br> • Integrate with internal tools</p><p>React Native CLI fits perfectly.</p><p>You can:<br> • Plug into any CI system<br> • Control build flavors<br> • Customize deployment strategies<br> • Avoid platform limitations</p><p><strong>Final Thoughts</strong></p><p>Expo has evolved , and it deserves the love it gets in 2026.<br>But React Native CLI is far from obsolete.</p><p>They’re not competitors anymore.<br>They’re tools for different stages and needs.</p><p>The best engineers don’t blindly follow recommendations , they choose based on context, scale, and long-term vision.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c8e161ced13b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Server Components Vulnerability ( CVE-2025–55182 )]]></title>
            <link>https://medium.com/@gorairanvir/react-server-components-vulnerability-cve-2025-55182-90f0c8c624c2?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/90f0c8c624c2</guid>
            <category><![CDATA[vulnerability]]></category>
            <category><![CDATA[reactjs]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sun, 21 Dec 2025 11:46:40 GMT</pubDate>
            <atom:updated>2025-12-21T11:46:40.784Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Img" src="https://cdn-images-1.medium.com/max/1024/1*wSMTaYWTtw4Mt60F3CWsdw.png" /></figure><p>Recently, a critical security vulnerability was discovered in React Server Components, identified as CVE 2025 55182. This vulnerability has a severity rating of 10 out of 10, making it one of the most serious security issues reported in the React ecosystem.</p><p>CVE stands for Common Vulnerabilities and Exposures, a standard used to identify and track publicly known security issues. A rating of 10 indicates maximum impact and risk.</p><p><strong>Affected React Versions: </strong>Applications running the following React versions are impacted:<br>React 19.0<br>React 19.1.0<br>React 19.1.1<br>React 19.2.0</p><h4>Why This Vulnerability Is So Dangerous</h4><p>This vulnerability is extremely malicious in nature. If exploited, a client can gain deep access to the server environment running React Server Components.</p><p><strong>An attacker could potentially:</strong></p><ul><li>Execute arbitrary server side code</li><li>Log or manipulate server data</li><li>Access environment variables</li><li>Create or delete files on the server</li><li>Completely compromise the server environment</li></ul><p><strong>How the Attack Works</strong></p><p>Once a React application using Server Components is running, an attacker can:</p><ul><li>Open the browser developer console</li><li>Trigger a specially crafted API request</li><li>Pass a malicious payload to the React Server endpoint</li></ul><p>By doing this, the attacker can break out of the expected execution flow and gain access to internal server logic. This is possible because the vulnerable versions do not properly validate and isolate incoming payloads.</p><p>I created a proof of concept locally to validate this behavior. However, the exact exploit code is intentionally not shared publicly to avoid misuse.</p><p>The most concerning part is that the attack originates from the client side, targeting the React Server Components runtime.</p><p><strong>How to Fix the Issue</strong></p><p>The solution is straightforward and strongly recommended:</p><p>Upgrade React immediately</p><p>Updating React to 19.0.1, 19.1.2, 19.2.1 or later fully patches this vulnerability. The fix ensures proper validation and isolation of server side execution in React Server Components.</p><p>If upgrading is not immediately possible, consider temporarily disabling React Server Components until the update can be applied.</p><p>However, some cloud platforms such as AWS, GCP and CloudFront can help mitigate this scenario by detecting and blocking certain malicious payloads at the infrastructure level. That said, relying solely on cloud-level protections is not sufficient. The most effective and recommended approach is to fix the vulnerability at the application level by upgrading and properly securing the React implementation.</p><p><strong>Final Thoughts</strong></p><p>This vulnerability is a strong reminder that server side rendering and server components must be treated as critical infrastructure, not just frontend features.</p><p>If your application uses React Server Components, treat this update as urgent. A delay in patching could result in full server compromise.</p><p>Security updates are not optional. They are a core part of responsible software development.</p><p>Source: <br><a href="https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components">https://react.dev/blog/2025/12/03/critical-security-vulnerability-in-react-server-components</a></p><p><a href="https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc">https://github.com/lachlan2k/React2Shell-CVE-2025-55182-original-poc</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=90f0c8c624c2" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[ Upgrading React Native to Support Android 16KB Page Size]]></title>
            <link>https://medium.com/@gorairanvir/upgrading-react-native-to-support-android-16kb-page-size-c5abbbbe1d32?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/c5abbbbe1d32</guid>
            <category><![CDATA[16-kb-page-size]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sun, 14 Dec 2025 02:32:21 GMT</pubDate>
            <atom:updated>2025-12-14T02:32:21.555Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/909/1*lCA4qDy4B0-ZXW31HqRgFw.png" /></figure><p>⚠️ Solve The Problem: Android 16KB Page Size Warning</p><p>A few months ago, we started receiving a warning from the Google Play Console: <strong>Your app must support Android 16KB page size</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/950/1*c0CyNkADhlWHA2snIJh3Eg.png" /></figure><p>We often ignore tech debt, especially dependency upgrades, until it becomes absolutely necessary.<br>This story is about one such moment , and how we handled it.</p><p>This is a hard requirement for newer Android versions and future Play Store compliance.</p><p>✅ The Requirement: To support 16KB page size:</p><p>Your app must use React Native ≥ 0.77, React Native 0.81 is recommended as it’s stable and fully compliant</p><p>🔧 The Challenge with Older React Native Versions</p><p>Our app was running on React Native 0.69.3. Upgrading directly to 0.81 is not straightforward, because, older versions rely on the Bridge architecture, newer versions use the New Architecture (JSI / TurboModules / Fabric)</p><p>There is no direct jump from Bridge-only → New Architecture</p><p>The Solution: Two-Step Upgrade Strategy</p><p>To make this safe and manageable, we followed a two-step upgrade path:</p><p>🚀 Step 1: Upgrade to React Native 0.76.8, Why 0.76.8?</p><p>Supports both, Legacy Bridge and New Architecture (JSI)</p><p>This makes it the perfect transition version.</p><p>🚀 Step 2:</p><p>Upgraded React Native app from <strong>version 0.69.3 to 0.76.8</strong>. After the upgrade, the app was generally stable, however, a few native dependencies required updates, most notably <strong>react-native-camera</strong>, <strong>react-native-skia</strong>, and some other supporting libraries.</p><p>In parallel, we migrated all <strong>custom native bridge modules</strong> to <strong>JSI</strong> and thoroughly tested the app in <strong>bridgeless mode</strong>. The app continued to function as expected, confirming that the new architecture migration was successful.</p><p>Now we are ready to verify whether our app is properly aligned with the Android 16KB page size requirement.<br>Since the app is functioning correctly, the next step is to confirm that all native libraries are compatible with the 16KB page size. To do this, we need to generate a release or debug build and validate the native binaries.</p><p>Create a <strong>check_elf_alignment.sh </strong>file copy this code to it.</p><pre>#!/bin/bash<br>progname=&quot;${0##*/}&quot;<br>progname=&quot;${progname%.sh}&quot;<br><br># usage: check_elf_alignment.sh [path to *.so files|path to *.apk]<br><br>cleanup_trap() {<br>  if [ -n &quot;${tmp}&quot; -a -d &quot;${tmp}&quot; ]; then<br>    rm -rf ${tmp}<br>  fi<br>  exit $1<br>}<br><br>usage() {<br>  echo &quot;Host side script to check the ELF alignment of shared libraries.&quot;<br>  echo &quot;Shared libraries are reported ALIGNED when their ELF regions are&quot;<br>  echo &quot;16 KB or 64 KB aligned. Otherwise they are reported as UNALIGNED.&quot;<br>  echo<br>  echo &quot;Usage: ${progname} [input-path|input-APK|input-APEX]&quot;<br>}<br><br>if [ ${#} -ne 1 ]; then<br>  usage<br>  exit<br>fi<br><br>case ${1} in<br>  --help | -h | -\?)<br>    usage<br>    exit<br>    ;;<br><br>  *)<br>    dir=&quot;${1}&quot;<br>    ;;<br>esac<br><br>if ! [ -f &quot;${dir}&quot; -o -d &quot;${dir}&quot; ]; then<br>  echo &quot;Invalid file: ${dir}&quot; &gt;&amp;2<br>  exit 1<br>fi<br><br>if [[ &quot;${dir}&quot; == *.apk ]]; then<br>  trap &#39;cleanup_trap&#39; EXIT<br><br>  echo<br>  echo &quot;Recursively analyzing $dir&quot;<br>  echo<br><br>  if { zipalign --help 2&gt;&amp;1 | grep -q &quot;\-P &lt;pagesize_kb&gt;&quot;; }; then<br>    echo &quot;=== APK zip-alignment ===&quot;<br>    zipalign -v -c -P 16 4 &quot;${dir}&quot; | egrep &#39;lib/arm64-v8a|lib/x86_64|Verification&#39;<br>    echo &quot;=========================&quot;<br>  else<br>    echo &quot;NOTICE: Zip alignment check requires build-tools version 35.0.0-rc3 or higher.&quot;<br>    echo &quot;  You can install the latest build-tools by running the below command&quot;<br>    echo &quot;  and updating your \$PATH:&quot;<br>    echo<br>    echo &quot;    sdkmanager \&quot;build-tools;35.0.0-rc3\&quot;&quot;<br>  fi<br><br>  dir_filename=$(basename &quot;${dir}&quot;)<br>  tmp=$(mktemp -d -t &quot;${dir_filename%.apk}_out_XXXXX&quot;)<br>  unzip &quot;${dir}&quot; lib/* -d &quot;${tmp}&quot; &gt;/dev/null 2&gt;&amp;1<br>  dir=&quot;${tmp}&quot;<br>fi<br><br>if [[ &quot;${dir}&quot; == *.apex ]]; then<br>  trap &#39;cleanup_trap&#39; EXIT<br><br>  echo<br>  echo &quot;Recursively analyzing $dir&quot;<br>  echo<br><br>  dir_filename=$(basename &quot;${dir}&quot;)<br>  tmp=$(mktemp -d -t &quot;${dir_filename%.apex}_out_XXXXX&quot;)<br>  deapexer extract &quot;${dir}&quot; &quot;${tmp}&quot; || { echo &quot;Failed to deapex.&quot; &amp;&amp; exit 1; }<br>  dir=&quot;${tmp}&quot;<br>fi<br><br>RED=&quot;\e[31m&quot;<br>GREEN=&quot;\e[32m&quot;<br>ENDCOLOR=&quot;\e[0m&quot;<br><br>unaligned_libs=()<br><br>echo<br>echo &quot;=== ELF alignment ===&quot;<br><br>matches=&quot;$(find &quot;${dir}&quot; -type f)&quot;<br>IFS=$&#39;\n&#39;<br>for match in $matches; do<br>  # We could recursively call this script or rewrite it to though.<br>  [[ &quot;${match}&quot; == *&quot;.apk&quot; ]] &amp;&amp; echo &quot;WARNING: doesn&#39;t recursively inspect .apk file: ${match}&quot;<br>  [[ &quot;${match}&quot; == *&quot;.apex&quot; ]] &amp;&amp; echo &quot;WARNING: doesn&#39;t recursively inspect .apex file: ${match}&quot;<br><br>  [[ $(file &quot;${match}&quot;) == *&quot;ELF&quot;* ]] || continue<br><br>  res=&quot;$(objdump -p &quot;${match}&quot; | grep LOAD | awk &#39;{ print $NF }&#39; | head -1)&quot;<br>  if [[ $res =~ 2\*\*(1[4-9]|[2-9][0-9]|[1-9][0-9]{2,}) ]]; then<br>    echo -e &quot;${match}: ${GREEN}ALIGNED${ENDCOLOR} ($res)&quot;<br>  else<br>    echo -e &quot;${match}: ${RED}UNALIGNED${ENDCOLOR} ($res)&quot;<br>    unaligned_libs+=(&quot;${match}&quot;)<br>  fi<br>done<br><br>if [ ${#unaligned_libs[@]} -gt 0 ]; then<br>  echo -e &quot;${RED}Found ${#unaligned_libs[@]} unaligned libs (only arm64-v8a/x86_64 libs need to be aligned).${ENDCOLOR}&quot;<br>elif [ -n &quot;${dir_filename}&quot; ]; then<br>  echo -e &quot;ELF Verification Successful&quot;<br>fi<br>echo &quot;=====================&quot;</pre><p>Now run the folowing command in the terminal</p><p>Make this file executable in system.</p><pre>chmod 777 check_elf_alignment.sh</pre><p>Now run</p><pre>check_elf_alignment.sh path/of/your/app.apk</pre><p>The script will give idea about either ALIGNED or UNALIGNED for all the arm64-v8a shared libraries.</p><p>This process helps us identify which native libraries are not aligned with the 16KB page size. Once identified, we can update or replace those libraries, generate a new release build, and verify the alignment again. After fixing these issues, the Android 16KB page size warning is resolved.</p><p>🏁 Final Takeaway</p><p>⚠️ Ignoring dependency upgrades can lead to last-minute compliance risks<br>✅ A phased upgrade strategy saves time and reduces production risk<br>🚀 React Native 0.81 + New Architecture is the right long-term choice</p><p>If you’re still on an older React Native version, start early, future Android requirements will only get stricter.</p><p>Source: <a href="https://developer.android.com/guide/practices/page-sizes#build">https://developer.android.com/guide/practices/page-sizes#build</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c5abbbbe1d32" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A Comprehensive Guide to Setting Up and Using Appium and Appium Inspector]]></title>
            <link>https://medium.com/@gorairanvir/a-comprehensive-guide-to-setting-up-and-using-appium-and-appium-inspector-249055ebbf91?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/249055ebbf91</guid>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Thu, 13 Apr 2023 14:23:23 GMT</pubDate>
            <atom:updated>2023-04-13T14:23:23.541Z</atom:updated>
            <content:encoded><![CDATA[<p>Hello everyone,</p><p>After a long time I am here to share some insights about test automation tools for mobile apps!</p><p>As you know, ensuring that our apps are functioning correctly and reliably is critical to our success, and that’s where test automation comes in.</p><p>With the rise of mobile applications, there is a growing need for testing tools that can help ensure the quality of the apps. Appium is one such tool that has gained immense popularity among developers and testers alike.</p><p>Appium is an open-source tool for automating mobile application testing across multiple platforms, including iOS and Android. It allows you to write automated tests using your preferred programming language, making it easy for both developers and testers to use. Additionally, Appium Inspector is a graphical user interface (GUI) tool that can be used to inspect the elements of an application, making it easier to create test scripts.</p><p>In this guide, I will provide a comprehensive overview of how to set up and use Appium and Appium Inspector. Whether you are a developer, tester, or someone who is simply interested in mobile application testing, this guide will help you get started with Appium and Appium Inspector. So, let’s dive in!</p><p>first go to <a href="https://github.com/appium/appium-desktop/releases">https://github.com/appium/appium-desktop/releases</a></p><p>and download Appium app for your system and install it.</p><p>Then go to <a href="https://github.com/appium/appium-inspector/releases">https://github.com/appium/appium-inspector/releases</a></p><p>and download appium inspector and install it.</p><p>Now open appium desktop you will get below interface.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IM2C1iyi_t6S7F41u_hpAw.png" /><figcaption>Appium Desktop</figcaption></figure><p>Change the server <strong>port</strong> or keep as it is, then hit start, now appium server should start.</p><p>Now you will get below screen</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*gUNxQR4AVaDTDHB3aM6jQg.png" /><figcaption>Appium server (Running)</figcaption></figure><p>Now it on search button, if appium inspector is already installed it will start the appium inspector or open appium inspector, you will get a interface like below.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*oY9_RHi1ts-9wZsVZxgFYQ.png" /></figure><h4>There is three main configuration is required</h4><ol><li><strong>Port </strong>: We need to set the same port as we have set on time of running our appium server</li><li><strong>Remote path</strong> : This is very important without remote path appium inspector will run but we will able to see any data. by default this path is <strong>/wd/hub</strong></li><li><strong>Capability</strong> : This is main configuration to invoke our app in appium inspectors, here we define which app need to open in which simulators also simulator properties.</li></ol><p>below it the bare minimum capability sample</p><pre>{<br>&quot;platformName&quot;: &quot;Android&quot;,<br>&quot;appium:platformVersion&quot;: &quot;13&quot;,<br>&quot;appium:deviceName&quot;: &quot;pixel_4&quot;,<br>&quot;appium:automationName&quot;: &quot;UiAutomator2&quot;,<br>&quot;appium:app&quot;: &quot;./path/app.apk&quot;,<br>}</pre><p>After setting this all just hit the <strong>start session</strong> button, you will get screen like below along with screen shot</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/772/1*LX2Xevhi92SuDXXhjsI0mQ.png" /><figcaption>Appium inspector (Running)</figcaption></figure><p>From the above screen we can inspect any screen and element of our app.</p><ul><li>Can see accessibility label or Xpath of any element.</li><li>Also we can get coordinate of any element to run touch interaction on any element.</li><li>Can navigate to any level of app element</li><li>Can perform any user interaction</li></ul><p>And list goes on…</p><h3>Conclusion</h3><p>Appium Desktop is a robust platform that empowers users to effortlessly manage automated testing for web, native, and hybrid applications. With its user-friendly interface, Appium Inspector simplifies the task of inspecting application elements, allowing for seamless creation of test scripts. The flexibility of Appium’s framework enables tests to be run on multiple real mobile devices, providing a level of accuracy that is unparalleled in the industry. By testing under real user conditions, Appium ensures that your application is functioning optimally and meets the expectations of your users. With Appium, you can be confident in the quality and reliability of your application.</p><p>Feel free to connect me on any platform @gorairanvir</p><p>Thankyou !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=249055ebbf91" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How to set up your system for react native development.]]></title>
            <link>https://medium.com/@gorairanvir/how-to-set-up-your-system-for-react-native-development-3ed75892158f?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/3ed75892158f</guid>
            <category><![CDATA[ranvir-gorai]]></category>
            <category><![CDATA[system]]></category>
            <category><![CDATA[jsr]]></category>
            <category><![CDATA[setup]]></category>
            <category><![CDATA[react-native]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Mon, 04 Apr 2022 05:02:07 GMT</pubDate>
            <atom:updated>2022-04-04T05:02:07.260Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/508/1*i9b3a7937dqGB86JMmvynA.jpeg" /><figcaption>System setup for React Native</figcaption></figure><p>Hello, I am Ranvir Gorai, I am a React Native Developer. This post is going to help new and experienced developers as well. Because as an experienced developer I also struggled when I received a new machine and my mind was full of common questions such as Where to start? What to do with my new machine?</p><p>But no worries! I am here to help you out.</p><p>So, to develop a react native app we will make use of the below tools:</p><ul><li><strong>Nvm</strong> — We will use <strong>Nvm</strong> is the <strong>Node Version Manager </strong>tool that will help you to switch between the node js version. By using <strong>NVM</strong> we can install a multiped node js version in the same system. Also, we can set up the default node js version using NVM.</li></ul><pre>curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash</pre><ul><li><strong>Node JS </strong>— Using NVM we can install multiped node js version in same system. also we can setup default node js version using NVM.</li></ul><pre>curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.1/install.sh | bash</pre><ul><li><strong>Vs code</strong> — For code editing and debugging.</li><li><strong>Xcode</strong> — For environment to run then app and debug for iOS.</li><li><strong>Android Studio </strong>— For environment to run then app and debug for Android.</li><li><strong>Item2</strong>- This tool will help you in terminal coding in same screen by splitting it horizontals and vertically.</li><li><strong>Brew</strong>- This tool will help you to install any dependency in for system.</li><li><strong>Cocoapods</strong> — this tool will help you to install pos for xcode projects.</li></ul><p>Thank you !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3ed75892158f" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React-Native with redux-saga]]></title>
            <link>https://medium.com/@gorairanvir/react-native-with-redux-saga-c51f9f39797c?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/c51f9f39797c</guid>
            <category><![CDATA[redux]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sun, 22 Jul 2018 20:41:38 GMT</pubDate>
            <atom:updated>2018-07-22T20:41:38.147Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*BmXdRwIPFMkyScgD2JDJlg.png" /><figcaption>Redux-Saga</figcaption></figure><p>For a good application where lots of API calls are going to happen simultaneously and many calculations take place, we need a robust project <strong>architecture</strong>, So we can have the flexibility to manage API calls from anywhere in the application and data as we needed, as we know that in react application when we use redux, we have another option for API call is to use redux-thunk which help as to make async network calls, but problem is there, the action got impure, because their network calls are made in action, so there <strong>Redux-Saga</strong> comes in role</p><p>Note: for complete setup <a href="https://blog.ranvirgorai.com/react-native-with-redux-saga/">click here</a></p><blockquote>The difference between Redux-Thunk and Redux-Saga is, Redux-Thunk based upon the action dispatch, where is <strong>redux-saga</strong> work as action watcher and work independently to action.</blockquote><p><a href="https://blog.ranvirgorai.com/react-native-with-redux-saga/">Application data flow after configured to redux-saga</a> <br><strong>Installation</strong></p><pre>npm install — save redux-saga</pre><p>Now it is time to create your <strong>sagas.js</strong></p><pre>import { FETCHING_CONFIG } from ‘appRoot/constants’;<br>import { makeRequest } from ‘./helper’<br>import { fetchConfigSuccess, fetchConfigError} from ‘appRoot/saga’<br>import { call, put, takeEvery } from ‘redux-saga/effects’;</pre><pre>function* fetchConfig(action) {<br> try {<br> const data = yield call(makeRequest,’yourUrl’);<br> yield put(fetchConfigSuccess(data));<br> } catch (error) {<br> yield put(fetchConfigError(error));<br> }<br>}</pre><pre>function* configSaga() {<br> yield takeEvery(FETCHING_CONFIG, fetchConfig);<br>}</pre><pre>export default configSaga;</pre><p>now we are done with saga implementation, now we need some configuration in existing code.</p><p>configure in <strong>store.js</strong></p><pre>import { createStore, applyMiddleware } from ‘redux’;<br>import app from ‘appRoot/reducers’;</pre><pre>import createSagaMiddleware from ‘redux-saga’;<br>import dataSaga from ‘appRoot/sagas’;</pre><pre>creating saga middleware instance<br>const sagaMiddleware = createSagaMiddleware();</pre><pre>export default function configureStore() {<br> const store = createStore(app, applyMiddleware(sagaMiddleware)); <br> sagaMiddleware.run(dataSaga);<br> return store;<br>}</pre><p>there is no any changes need in <strong>app.js</strong> where provider and store are configured.</p><p>Note: for complete setup <a href="https://blog.ranvirgorai.com/react-native-with-redux-saga/">click here</a></p><blockquote><strong>Conclusion:</strong> By leveraging <strong>redux-saga</strong> we can make a robust application, <strong>redux-saga</strong> help when our project grows because it is less complex.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c51f9f39797c" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[React Native persist data (Redux-persist)]]></title>
            <link>https://medium.com/@gorairanvir/2-react-native-persist-data-redux-persist-68b7e47fe69c?source=rss-3c69826fc791------2</link>
            <guid isPermaLink="false">https://medium.com/p/68b7e47fe69c</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-native]]></category>
            <category><![CDATA[jamshedpur]]></category>
            <category><![CDATA[mumbai]]></category>
            <dc:creator><![CDATA[RANVIR GORAI]]></dc:creator>
            <pubDate>Sun, 24 Jun 2018 18:53:48 GMT</pubDate>
            <atom:updated>2018-06-24T19:08:28.947Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*UnyxmBF5jR_15mroxGbMdw.jpeg" /><figcaption>Redux-persist</figcaption></figure><p>In every app, there must be some data which we have to keep during entire app lifespan, or some data need to keep for future use. Like user details, an authentication token to manage session of the user. sometimes we need to keep data of users last state, because once the user comes back to the app after some time so the user should be in the same state from where he did leave. so let&#39;s begin, by considering that redux is already set up and working fine so we need to some changes in existing file. Can read the full story <a href="http://blog.ranvirgorai.com/react-native-persist-app-data/">here</a></p><p><strong>Note: </strong>Here persist is done based on reducer so, we can white list and black list multiple reducers, so we have to make provision for that before so we can separate state which needs to persist. then whitelist it.</p><p>Full story: <a href="http://blog.ranvirgorai.com/react-native-persist-app-data/">http://blog.ranvirgorai.com/react-native-persist-app-data/</a></p><p>First, install the redux-presist</p><pre>npm install --save redux-presist</pre><p>Then make changes in <strong>store.js</strong></p><pre>...<br>// Necessary imports <br>import { persistStore,persistReducer} from &#39;redux-persist&#39;;<br>import storage from &#39;redux-persist/lib/storage&#39;;<br>import reducers from &#39;your/reducer/path&#39;</pre><pre><em>// Persistor Configuration to whitelist and blacklist any reducer<br>const</em> persistConfig = {<br>  key: &#39;root&#39;,<br>  storage,<br>  whitelist: [&#39;auth&#39;]<br>};</pre><pre><em>const</em> persistedReducer = persistCombineReducers(persistConfig,reducers);</pre><pre>export default () <em>=&gt;</em> {<br><em>const</em> store = createStore(persistedReducer, applyMiddleware(thunk));<br><em>const</em> persistor = persistStore(store);<br>return { store, persistor };<br>};</pre><p>Make some changes in root file <strong>App.js</strong> or <strong>index.js</strong></p><pre>...<br>import { PersistGate } from &#39;redux-persist/integration/react&#39;;<br>import configureStore from &#39;./app/store&#39;;<br>import { Provider } from &#39;react-redux&#39;;<br>...</pre><pre>//get store and presist store from configure store</pre><pre><em>const</em> { store, persistor } = configureStore();</pre><pre><em>function</em> Root() {<br>return (<br>&lt;<em>Provider</em> store={store}&gt;<br> &lt;<em>PersistGate</em> loading={null} persistor={persistor}&gt;<br>   &lt;<em>App</em> /&gt;<br> &lt;/<em>PersistGate</em>&gt;<br>&lt;/<em>Provider</em>&gt;);<br>}<br>export default Root;</pre><p>Here <strong><em>PersistGate, </em></strong><em>hold the app until loading it completely so, in loading props we can pass any loader component that will be displayed until loads.</em></p><p><strong>Conclusion: </strong>By using redux persist we can save applications data to the device without any hassle, it takes care of presenting data and make us free from overhead thinking of write time-frequency and write event (when to persist).</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=68b7e47fe69c" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>