[BUG]: SSLHandshakeException in 29.63 with new network_security_config
Checklist
- [x] I made sure that there are no existing issues - open or closed - which I could contribute my information to.
- [x] I have read the FAQ and my problem isn't listed.
- [x] I have taken the time to fill in all the required details. I understand that the bug report will be dismissed otherwise.
- [x] This issue contains only one bug.
Affected version
29.63
Device Type
Smart TV/Box
Affected Android
Android TV 14
Steps to reproduce the bug
Using version 29.63 app opens fine, and shows the cards but when entering a Video it shows the following:
loadFormatlnfo error: IllegalStateException: javax.net.ssl.SSLHandshakeException: java.security.cert.CertPathValidatorException: Trust anchor for certification path not found. getResponse(RetrofitHelper.java:127)
It's an SSLHandshakeException due to the implementation of network security settings without proper certificate. This doesn't happen in previous version 29.62, so the change made to the new version is causing the problem.
Actual behavior
Video never plays and keeps showing a toast with the error.
Additional information
No response
I have the same error message on the first video loading after opening SmartTube for the first time today, Waiting a few minutes and the video will load, Then after the first video loads they all load right away on my end.
Well I was not entirely correct, I've noticed the live streams only play after a few minutes, Anything that's not a live stream doesn't play at all. This happens with both 29.63 Stable and 29.63 Beta.
For the time being I went back to 29.59 Beta, It still has a delay on the first video but no errors, Everything seems to play for me.
Yes, I had to use the previous version because this never played a video and kept showing the error. I didn't try a live video though like you did, just regular videos.
Which android version do you have?
I am running a Nvidia Shield with Android 9
I have the same error, Android 8 based smart TV. So it's broken, can we get a fix?
I have the same error, hope can fix is soon.
Did any of you solve the problem?