Fixed
Status Update
No update yet.
Comments
zo...@gmail.com
Can you provide the below requested information to better understand the issue:
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Please provide sample application or apk to reproduce the issue.
Also kindly mention the steps to reproduce the issue using the sample application or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What do you expect to occur?
Current output
What do you see instead?
Steps to reproduce
What steps do others need to take in order to reproduce the issue themselves?
Please provide sample application or apk to reproduce the issue.
Also kindly mention the steps to reproduce the issue using the sample application or apk.
Frequency
How frequently does this issue occur? (e.g 100% of the time, 10% of the time)
Expected output
What do you expect to occur?
Current output
What do you see instead?
am...@google.com
am...@google.com
Hi,
The issue happens 100% of the time when running espresso tests in the "ar_XB" locale. I am working on a sample app to show the issue.
Expected behavior would be successful rendering, but instead the app crashes when rendering the layout.
The issue happens 100% of the time when running espresso tests in the "ar_XB" locale. I am working on a sample app to show the issue.
Expected behavior would be successful rendering, but instead the app crashes when rendering the layout.
ch...@google.com
ch...@google.com
Hi,
I have added a sample project athttps://github.com/kkoser/SupportLibRTLCrash . The crash happens when running tests in the "ar_XB" (right to left psuedolocale) locale, but not in other RTL locales. The locale for the test is set in onStart() of the test runner. To reproduce this crash, just run the test in "ExampleInstrumentedTest.java" from Android Studio.
Let me know if there's any more information you need!
I have added a sample project at
Let me know if there's any more information you need!
zo...@gmail.com
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
Description
Setting the backgroundTintList via XML works fine however - the control changes color when the states change.
Attached is a sample program demoing this issue. It includes two FloatingActionButtons, and two Buttons. One of the FloatingActionButtons and one of the regular buttons have their backgroundTintList setup programmatically, the other is setup via XML in the layout files.
Clicking on any of the controls toggles it's selected state.
The background color state list for each control is setup to use a specific color (Blue) for the unselected state, and another color (Red) for the selected State.
As the demo app shows, only the FloatingActionButton that sets it's backgroundTintList value in XML works as expected. As a control, the regular buttons are both functional, so setting the backgroundTintList value programmatically is OK for that control/in general(?).