Android check permission method, should not crash if we are trying to check a permission which does not exist on android

[ponomaretsm]

Before submitting a new issue

• I tested using the latest version of the library, as the bug might be already fixed.
• I tested using a supported version of react native.
• I checked for possible duplicate issues, with possible answers.

Bug summary

Calling check() with PERMISSIONS.IOS.APP_TRACKING_TRANSPARENCY on Android causes the app to crash or throw an error.
This seems unexpected — should the function not internally handle invalid platform permissions? I expected the library to safely ignore or warn about unsupported permissions for the current platform, instead of crashing.

Library version

5.4.0

Environment info

System:
  OS: macOS 14.6.1
  CPU: (10) arm64 Apple M1 Pro
  Memory: 116.11 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.20.2
    path: /private/var/folders/dw/xzbsqp2s2d7d5r1n4pxjskw80000gp/T/xfs-c9e396e7/node
  Yarn:
    version: 4.2.2
    path: /private/var/folders/dw/xzbsqp2s2d7d5r1n4pxjskw80000gp/T/xfs-c9e396e7/yarn
  npm:
    version: 10.5.0
    path: ~/.nvm/versions/node/v18.20.2/bin/npm
  Watchman:
    version: 2025.04.28.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/mponomarets/.rvm/rubies/ruby-2.7.5/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK:
    API Levels:
      - "28"
      - "29"
      - "30"
      - "31"
      - "32"
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 30.0.2
      - 30.0.3
      - 31.0.0
      - 33.0.0
      - 33.0.1
      - 34.0.0
      - 35.0.0
    System Images:
      - android-29 | Google APIs ARM 64 v8a
      - android-29 | Google Play ARM 64 v8a
      - android-31 | Google APIs ARM 64 v8a
      - android-32 | Google APIs ARM 64 v8a
      - android-33 | Google APIs ARM 64 v8a
      - android-33 | Google APIs Intel x86_64 Atom
      - android-34 | ARM 64 v8a
      - android-34 | Google APIs ARM 64 v8a
      - android-34 | Google Play ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.15989.150.2411.11948838
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.15
    path: /usr/bin/javac
  Ruby:
    version: 2.7.5
    path: /Users/mponomarets/.rvm/rubies/ruby-2.7.5/bin/ruby
npmPackages:
  "@react-native-community/cli": 15.0.1
  react: 18.3.1
  react-native: 0.76.9
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false

Steps to reproduce

1. Call check(PERMISSIONS.IOS.APP_TRACKING_TRANSPARENCY)
2. Run the app on Android
3. Observe the crash or exception.

Reproducible sample code

check(PERMISSIONS.IOS.APP_TRACKING_TRANSPARENCY)

[zoontek]

That's "kinda" logic. Explaining myself.

To reduce the library (and your bundle) size, I use a trick to not embed other platforms permission lists. To do so, there's one permissions.PLATFORM.ts file per platform: https://github.com/zoontek/react-native-permissions/tree/5.4.0/src
For example, this is the iOS permissions file. It avoids embedding the whole Android permissions list (which is bigger), or the even bigger Windows permissions list.

This means that if you perform a check(PERMISSIONS.IOS.APP_TRACKING_TRANSPARENCY) on Android, it performs a check(undefined), which error as React Native module layer expects a string.

[zoontek]

A good enough solution, using Proxy: v5.4.1.
It will not error, but instead resolves to unavailable (including in checkMultiple, requestMultiple)

[ponomaretsm]

A good enough solution, using Proxy: v5.4.1. It will not error, but instead resolves to unavailable (including in checkMultiple, requestMultiple)

Thank you! I was struggling with this issue, and your fix came just in time. Much appreciated! 🚀