<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Bipin Vishwakarma</title>
    <description>The latest articles on DEV Community by Bipin Vishwakarma (@techiejester).</description>
    <link>https://dev.to/techiejester</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4257540%2F2405aeac-4a9f-48f2-9f11-f99801db3254.jpeg</url>
      <title>DEV Community: Bipin Vishwakarma</title>
      <link>https://dev.to/techiejester</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/techiejester"/>
    <language>en</language>
    <item>
      <title>Shipping a Flutter app with no INTERNET permission: the plugins that tried to add it back</title>
      <dc:creator>Bipin Vishwakarma</dc:creator>
      <pubDate>Sat, 21 Nov 2026 15:37:48 +0000</pubDate>
      <link>https://dev.to/techiejester/shipping-a-flutter-app-with-no-internet-permission-the-plugins-that-tried-to-add-it-back-n4b</link>
      <guid>https://dev.to/techiejester/shipping-a-flutter-app-with-no-internet-permission-the-plugins-that-tried-to-add-it-back-n4b</guid>
      <description>&lt;p&gt;I've just shipped an offline card vault in Flutter, where "no internet" is the whole promise: the Android app must not even request the permission. Here's what that took.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Plugins merge permissions into your manifest.&lt;/strong&gt; The Play Billing library adds &lt;code&gt;INTERNET&lt;/code&gt;. The &lt;code&gt;camera&lt;/code&gt; plugin adds &lt;code&gt;RECORD_AUDIO&lt;/code&gt; and storage access. You remove them in &lt;code&gt;android/app/src/main/AndroidManifest.xml&lt;/code&gt;:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;uses-permission&lt;/span&gt; &lt;span class="na"&gt;android:name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"android.permission.INTERNET"&lt;/span&gt; &lt;span class="na"&gt;tools:node&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"remove"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;uses-permission&lt;/span&gt; &lt;span class="na"&gt;android:name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"android.permission.RECORD_AUDIO"&lt;/span&gt; &lt;span class="na"&gt;tools:node&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"remove"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;uses-permission&lt;/span&gt; &lt;span class="na"&gt;android:name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"android.permission.WRITE_EXTERNAL_STORAGE"&lt;/span&gt; &lt;span class="na"&gt;tools:node&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"remove"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;span class="nt"&gt;&amp;lt;uses-permission&lt;/span&gt; &lt;span class="na"&gt;android:name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"android.permission.READ_EXTERNAL_STORAGE"&lt;/span&gt; &lt;span class="na"&gt;tools:node&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"remove"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;Billing still works without &lt;code&gt;INTERNET&lt;/code&gt;: the library talks to the Play Store app, and the Play Store does the networking.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Camera permission implies camera hardware.&lt;/strong&gt; Declaring &lt;code&gt;CAMERA&lt;/code&gt; makes Play treat a camera as required, so declare it optional:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;uses-feature&lt;/span&gt; &lt;span class="na"&gt;android:name&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"android.hardware.camera"&lt;/span&gt; &lt;span class="na"&gt;android:required&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="s"&gt;"false"&lt;/span&gt; &lt;span class="nt"&gt;/&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;3. What stays: &lt;code&gt;ACCESS_NETWORK_STATE&lt;/code&gt;.&lt;/strong&gt; Google's data transport library (from Play Billing) and media3 (from the camera) add it. It only tells an app whether the phone is online; it can't send or receive anything. Google Play lists it as "view network connections", so explain it to your users before they ask.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. A release check, so it never comes back.&lt;/strong&gt; Every release APK goes through a script that fails if &lt;code&gt;INTERNET&lt;/code&gt; reappears after a plugin update:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight shell"&gt;&lt;code&gt;&lt;span class="nv"&gt;perms&lt;/span&gt;&lt;span class="o"&gt;=&lt;/span&gt;&lt;span class="nv"&gt;$(&lt;/span&gt;aapt2 dump permissions build/app/outputs/flutter-apk/app-release.apk&lt;span class="o"&gt;)&lt;/span&gt;
&lt;span class="k"&gt;if&lt;/span&gt; grep -q &lt;span class="s2"&gt;"android.permission.INTERNET"&lt;/span&gt; &lt;span class="o"&gt;&amp;lt;&amp;lt;&amp;lt;&lt;/span&gt;&lt;span class="s2"&gt;"$perms"&lt;/span&gt;&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="k"&gt;then&lt;/span&gt;
  &lt;span class="nb"&gt;echo&lt;/span&gt; &lt;span class="s2"&gt;"FAIL: release APK requests INTERNET"&lt;/span&gt; &lt;span class="o"&gt;&amp;gt;&amp;amp;&lt;/span&gt;2&lt;span class="o"&gt;;&lt;/span&gt; &lt;span class="nb"&gt;exit&lt;/span&gt; 1
&lt;span class="k"&gt;fi&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;&lt;strong&gt;5. Crypto with libsodium from Dart&lt;/strong&gt; (the &lt;code&gt;sodium&lt;/code&gt; package): Argon2id for the master password (128 MiB, 4 passes: about 0.8 s on a mid-range phone), XChaCha20-Poly1305 for the vault, secretstream for backup files.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;6. Two bugs worth knowing about:&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Bytes that come back over a platform channel are read-only. Our fingerprint unlock tried to wipe the key in place and spun forever. Copy them first, then wipe the copy.&lt;/li&gt;
&lt;li&gt;The vault can auto-lock during any &lt;code&gt;await&lt;/code&gt;. Passing an already-disposed key to libsodium crashes the app, so every use of the key after an &lt;code&gt;await&lt;/code&gt; checks first that the vault is still open.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;strong&gt;7. iOS:&lt;/strong&gt; there's no permission to remove, so the app simply contains no networking code, and the App Store privacy label reads "Data Not Collected". Purchases go through StoreKit 2, which Apple runs.&lt;/p&gt;

&lt;p&gt;Happy to go deeper on any part in the comments.&lt;/p&gt;

&lt;p&gt;&lt;em&gt;The app is Treepisode Card Box, an offline card vault (closed source): &lt;a href="https://treepisode.com/card-box?utm_source=devto" rel="noopener noreferrer"&gt;https://treepisode.com/card-box?utm_source=devto&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>flutter</category>
      <category>android</category>
      <category>privacy</category>
      <category>security</category>
    </item>
  </channel>
</rss>
