blob: 94397ab5f1af4ebf237cc9be4561ade6c0311732 [file] [log] [blame]
Remi NGUYEN VANc6f8fb02022-04-20 18:58:53 +09001# Make sure proguard keeps all connectivity classes
2# TODO: instead of keeping everything, consider listing only "entry points"
3# (service loader, JNI registered methods, etc) and letting the optimizer do its job
4-keep class android.net.** { *; }
5-keep class com.android.connectivity.** { *; }
6-keep class com.android.net.** { *; }
7-keep class !com.android.server.nearby.**,com.android.server.** { *; }
8
9# Prevent proguard from stripping out any nearby-service and fast-pair-lite-protos fields.
10-keep class com.android.server.nearby.NearbyService { *; }
11-keep class com.android.server.nearby.service.proto { *; }
12
13# The lite proto runtime uses reflection to access fields based on the names in
14# the schema, keep all the fields.
15# This replicates the base proguard rule used by the build by default
16# (proguard_basic_keeps.flags), but needs to be specified here because the
17# com.google.protobuf package is jarjared to the below package.
18-keepclassmembers class * extends com.android.connectivity.com.google.protobuf.MessageLite { <fields>; }