If users want to enable code shrinking, obfuscation and optimization using ProGuard they can add this rule to the ProGuard file of their project. ProGuard removes some fields from mavsdk classes and native code present in the mavsdk-server module when the rule is not used.
This rule works for both mavsdk and mavsdk-server modules.
Alternatively, the ProGuard file can also be embedded in the jar, so that the users don't have to worry about adding the rules themselves. But I am yet to test that.
If users want to enable code shrinking, obfuscation and optimization using ProGuard they can add this rule to the ProGuard file of their project. ProGuard removes some fields from mavsdk classes and native code present in the mavsdk-server module when the rule is not used.
This rule works for both mavsdk and mavsdk-server modules.
Tested on Android Studio 4.2 with Gradle 7.0.2