Home > Article > Backend Development > Share a python method to solve Android compatibility issues
This article mainly introduces Android compatibility issues: java.lang.UnsupportedOperationException solutions, friends in need can refer to it
In the development of the past few days, I encountered such a very There is a strange anomaly. Some mobile phones can run, but some mobile phones just crash. Today I will sort out this anomaly.
First of all, let’s post the exception information
E/AndroidRuntime: FATAL EXCEPTION: main android.view.InflateException: Binary XML file line #13: Error inflating class <unknown> at android.view.LayoutInflater.createView(LayoutInflater.java:613) at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56) at android.view.LayoutInflater.onCreateView(LayoutInflater.java:660) at android.view.LayoutInflater.createViewFromTag(LayoutInflater.java:685) at android.view.LayoutInflater.rInflate(LayoutInflater.java:746) at android.view.LayoutInflater.parseInclude(LayoutInflater.java:830) at android.view.LayoutInflater.rInflate(LayoutInflater.java:736) at android.view.LayoutInflater.rInflate(LayoutInflater.java:749) at android.view.LayoutInflater.inflate(LayoutInflater.java:489) at android.view.LayoutInflater.inflate(LayoutInflater.java:396) at com.hy.taotao.utils.GlobalUtils.inflate(GlobalUtils.java:91) at com.hy.taotao.base.BaseFragment.onCreateView(BaseFragment.java:59) ... Caused by: java.lang.reflect.InvocationTargetException at java.lang.reflect.Constructor.constructNative(Native Method) at java.lang.reflect.Constructor.newInstance(Constructor.java:417) at android.view.LayoutInflater.createView(LayoutInflater.java:587) at com.android.internal.policy.impl.PhoneLayoutInflater.onCreateView(PhoneLayoutInflater.java:56)? ... Caused by: java.lang.UnsupportedOperationException: Can't convert to dimension: type=0x1 at android.content.res.TypedArray.getDimensionPixelSize(TypedArray.java:468) at android.widget.TextView.<init>(TextView.java:944) at android.widget.TextView.<init>(TextView.java:605) at java.lang.reflect.Constructor.constructNative(Native Method)? at java.lang.reflect.Constructor.newInstance(Constructor.java:417)? at android.view.LayoutInflater.createView(LayoutInflater.java:587)? ...
I have sorted out the main exception information above. First, we can look at this sentence. The information we can get from the above is "xml file 13 The reason is that the element of type=0x1 cannot be found in the dimension file." Later, my colleague checked more information on the Internet and said that the default value was missing in values, and finally found the missing default value...
1. First look at the screenshot of the folder before the error is reported. You can see that some of the values-v19 files are not visible on values. The values-v19 folder is the file in this directory used by Api19 devices. folder, when the device cannot find the corresponding folder named values-*, it will look for the files in the default values folder. If it cannot be found, the above exception will occur. .
#2. Now that you know the problem, you have to solve it
1) Back up all values-*** and delete it.
2) Add the files in the backed-up values-*** to the default values folder.
3. In fact, this method in the above 2 is generally not recommended. If the mobile phone screen is adapted, of course you cannot only keep the default folder of values, but remember to add other values-* Folder elements must be present in the default values folder.
4. The following is a screenshot after simple processing
Summary:
1. Working as a third party When integrating etc., remember: elements in other values-* folders must be present in the default values folder.
【Related Recommendations】
1. Special Recommendation: "php Programmer Toolbox" V0.1 version download
3. Python object-oriented video tutorial
The above is the detailed content of Share a python method to solve Android compatibility issues. For more information, please follow other related articles on the PHP Chinese website!