Are there any specific permissions required for using the Pushwoosh plugin in MvvmCross

1. Firebase Cloud Messaging (FCM) Setup: To integrate Pushwoosh, you need to set up Firebase Cloud Messaging (FCM) in your Android project. This involves connecting your project to Firebase through Android Studio and following the setup wizard, which adds necessary dependencies to your `build.gradle` files[2].

2. Permissions in AndroidManifest.xml: You need to add specific metadata to your `AndroidManifest.xml` file. This includes `com.pushwoosh.appid`, `com.pushwoosh.apitoken`, and `com.pushwoosh.senderid` (which is typically set as `fcm_sender_id` in your `strings.xml` file)[2].

3. Required Permissions: For Pushwoosh to work correctly, your app needs to have the necessary permissions declared in the `AndroidManifest.xml` file. However, the specific permissions required by Pushwoosh itself are not explicitly listed. Generally, for push notifications, you might need permissions related to internet access and receiving broadcasts, but these are typically handled by the Firebase setup.

4. Runtime Permissions: Starting from Android Marshmallow (API level 23), apps need to request certain permissions at runtime. While Pushwoosh itself might not require specific runtime permissions, other features in your app might. You should ensure that any required permissions are requested appropriately using the Android permission model[1].

5. MvvmCross Integration: When integrating Pushwoosh with MvvmCross, you should follow the guidelines for setting up the Pushwoosh plugin. This typically involves adding the plugin to your project and configuring it according to the Pushwoosh documentation[4].

In summary, while Pushwoosh itself does not require specific permissions beyond those handled by Firebase, your app may need to request additional permissions depending on its features. Always ensure that you comply with Android's permission model for any features that require user consent.