Redth
commented
5 years ago So, we do include the proguard.txt file that is in the original .aar:
# Copyright (C) 2015 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
# Preference objects are inflated via reflection
-keep public class android.support.v7.preference.Preference {
public <init>(android.content.Context, android.util.AttributeSet);
}
-keep public class * extends android.support.v7.preference.Preference {
public <init>(android.content.Context, android.util.AttributeSet);
}This doesn't look obviously the same as your rule set. Would you be able to share a diagnostic build log (or better yet a binlog) of your project? I'd like to see / ensure that the .aar file we do ship is being considered in the proguard call.
leonluc-dev
luryus
yaliashkevich
moljac
Xamarin.Android Version (eg: 6.0):
9.1.4.2
Operating System & Version (eg: Mac OSX 10.11):
Windows 10 (1809)
Support Libraries Version (eg: 23.3.0):
28.0.0
Describe your Issue:
This is a followup to issue #96 After updating to version 28.0.0 a few new issues started popping up.
Among others
android.support.v7.widget.FitWindowsFrameLayoutandandroid.support.v7.preference.PreferenceCategoryare giving issues during inflation. I've adjusted my proguard configuration file to explicitly include (the packages of) these classes, but these rules are supposed to be included with the support library itself (at least they are in Android Studio).Steps to Reproduce (with link to sample solution if possible):
Build a project with Proguard enabled and use the (for example) PreferenceCategory class in a xml file. Then inflate said xml file in code.
Temporary workaround
Add the following to the ProGuard configuration file:
Example stack trace