You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 20, 2018. It is now read-only.
As I understand it, the activity io.cordova.reactnative.cordovaplugin is the one actually registering these plugin permissions.
The problem is when multiple apps are installed that use this package to add React Native plugins, since then multiple apps will have the same permission name. When this happens, installation fails.
Do you have any suggestions of how to namespace these permissions better?
Ideas:
Access the React Native project's MainActivity package name to set $PACKAGE_NAME somehow
Use a variable passed in when installing the plugin to set $PACKAGE_NAME (e.g. /cordova-plugin add ___ --variable PACKAGE_NAME="com.some.package")
I'm not sure how feasible the ideas above are, but if I get some feedback I can look into working on this (I need this resolved myself).
Thanks!
The text was updated successfully, but these errors were encountered:
Some plugins add permissions that depend on package names. One is Pushwoosh Push Notification Plugin.
Example permission:
As I understand it, the activity
io.cordova.reactnative.cordovaplugin
is the one actually registering these plugin permissions.The problem is when multiple apps are installed that use this package to add React Native plugins, since then multiple apps will have the same permission name. When this happens, installation fails.
Do you have any suggestions of how to namespace these permissions better?
Ideas:
I'm not sure how feasible the ideas above are, but if I get some feedback I can look into working on this (I need this resolved myself).
Thanks!
The text was updated successfully, but these errors were encountered: