proguard - Should I keep android.support.v4.app.Fragment and its derived classes when building a release version of my app? -


i read answer , undestood why should keep names of services, activities, , custom views. should keep classes derive android.support.v4.app.fragment?

i took @ defualt proguard config file %sdk_dir%\sdk\tools\proguard\proguard-android.txt, , there no rules regarding fragments.

the main reason why need keep class, because accessed via reflection.

fragments not accessed via reflection, don't have keep them.

except if reference them directly in layout files (because parsing layout files uses reflection).


Comments

Popular posts from this blog

ios - RestKit 0.20 — CoreData: error: Failed to call designated initializer on NSManagedObject class (again) -

java - Digest auth with Spring Security using javaconfig -

laravel - PDOException in Connector.php line 55: SQLSTATE[HY000] [1045] Access denied for user 'root'@'localhost' (using password: YES) -