<?xml version="1.0" encoding="utf-8"?>
<manifest xmlns:android="http://schemas.android.com/apk/res/android">
    <!--
      The SDK's entire job is to deliver events over the network, so the SDK
      declares the permission for it. Library manifests merge into the host
      app, so consuming apps inherit this and cannot silently ship an analytics
      build with no way to transmit.

      WHY THIS FILE HAS CONTENT (2026-08-04): it was an empty <manifest/> tag
      declaring nothing. React Native's app template does include INTERNET in
      its MAIN manifest, so this is less acute than the Flutter case — where
      the template had it in the DEBUG manifest only, so a release build merged
      to no INTERNET at all and silently transmitted nothing (layers/sdks#209).
      But depending on the host template is exactly the fragility that caused
      that, and being self-sufficient costs nothing. ACCESS_NETWORK_STATE is
      declared for the same reason: the delivery layer checks connectivity
      before draining the queue.

      Deliberately NOT declared here: com.google.android.gms.permission.AD_ID.
      It merges in transitively from play-services-ads-identifier's own AAR
      manifest, so it appears only when that library is actually present.
      Declaring it unconditionally would add an advertising-ID permission to
      apps that excluded the dependency and collect no advertising ID — a Play
      Console data-safety discrepancy rather than a convenience.
    -->
    <uses-permission android:name="android.permission.INTERNET" />
    <uses-permission android:name="android.permission.ACCESS_NETWORK_STATE" />
</manifest>
