Fixed
Status Update
Comments
ja...@gmail.com <ja...@gmail.com> #2
I confirm. There is such problem for version 25.3.0.
ar...@google.com <ar...@google.com> #3
We have passed this defect on to the development team and will update this issue with more information as it becomes available.
ki...@google.com <ki...@google.com>
ai...@gmail.com <ai...@gmail.com> #5
Please fix this problem
ko...@gmail.com <ko...@gmail.com> #6
Are you kidding me? The "fix" is that you increase min SDK level to 14? I base this assumption on the fact that 26.0.0 alpha 1 is out and it states that the min level is set to 14, anything below that should just die peacefully. If it's true, then it's even more ridiculous than deploying lib versions without actually testing them...
pe...@gmail.com <pe...@gmail.com> #7
Could somebody from the team please confirm whether this issue is indeed the reason for bumping the min SDK to 14 in 26.0.0-alpha1?
ca...@gmail.com <ca...@gmail.com> #8
I also need to target SDK 10, so I'm bumping back to version 25.2.0 until there is a "good" fix.
ro...@gmail.com <ro...@gmail.com> #9
Apparently this is fixed in 25.3.1.
li...@gmail.com <li...@gmail.com> #10
Well, this costed me a day of work. Can confirm that it has been fixed in 25.3.1
do...@gmail.com <do...@gmail.com> #11
There is Switch in api 14, then why we need SwitchCompat...?
gy...@gmail.com <gy...@gmail.com> #12
SwitchCompat is part of the appcompat lib, so it provides material design on pre-Lollilop devices. I guess the native switch does not do that.
ko...@gmail.com <ko...@gmail.com> #13
This bug is back in 25.4.0. The 25.x.x is supposed to be compatible with pre-14 devices, only 26.x.x should drop support.
cp...@gmail.com <cp...@gmail.com> #14
Confirm regression, bug is back in 25.4.0
Description
Version used: 25.3.0
Theme used: N/A
Devices/Android versions reproduced on: API 13 and below
As per the documentation of SwitchCompat (
The support lib revisions page does not contain any info about deprecation nor removal of this element from API (7-)9-13 devices. If it is not being supported on devices below API 14, the appropriate classes should be modified to implement a different widget or a custom implementation.