Edgar Cervantes / Android Authority
Tl;
- A Redditor has discovered that the second generation of Chromecast has an expired certificate authority, which causes it to fail the authentication of devices and stop working and being set up.
- As a solution, users can bypass unit approval by following the steps mentioned below.
- If you have a factory reset Chromecast, you can set your phone’s date back to 8 March 2025 and potentially continue with the layout. When you finish setting up Chromecast, you can correct your phone’s date.
Second generation Chromecast and chromecast audio devices have not worked For users the last couple of days. The units are Failing to cast contentFrustrating users who depend on them for their role crew. Google is aware of the problem and is working to fix it. Meanwhile, the company advises users not to reset the factory’s reset of the non-functional chromecasts. If you scratch your head about what is happening, we have more information to share, including possible solutions for enthusiasts.
Why is the second generation chromecast not able to cast anymore?
Reddit -User Tchebb Spent some time troubleshooting the reason to fail chromecasts. According to the Redditor’s survey, Google issued an intermediate Ca (certificate authority) with a validity period of just 10 years for the second generation of Chromecast units, and about has expired. Consequently, Google apps that rely on this CA manage not to validate Chromecast as a real device and refuse to communicate with it, including during the first layout.
Redditor mentions that Google has a few routes to solve the problem, although all of these are technical and out of the scope of this article. Long story short, Google needs some time to solve the problem, as it is likely to require synchronization with the release cycles of Chrome, the Google Play Services and the Google Home app. iOS apps involving the role crew SDK can take even longer to solve the problem.
Redditor mentions that they checked their first generation Chromecast, and the CA certificate has a 20-year validity, which is why the older unit continues to work while the relatively newer faces issues. Oddly enough, until 2016, it seems that Chromium’s certificate verification code did not validate expiry time at all. So the one who issued these certificates probably did not expect validation to be checked, which chromium (and possibly other Google clients and apps) began to check later according to the Convention.
Solutions to fix Chromecast -approval issues
Redditor has posted a few solutions that allow users to throw back on the second generation of Chromecast. Google will publish the final solution, but you can try these solutions if you have technical knowledge and can’t wait for the official solution.
Fix Casting from Android (GUI method)
- Download and install an Activity Manager app, as free and open source code Activity manager app.
- Start the app and select Intention From the drop -down menu in the upper right.
- Tap edit icon next to Action Field and type/paste this: com.google.android.gms.Cast.settings.Casteting Collapsingdebugaction
- On Android 11 and below, enter/paste this instead: com.google.android.gms.Cast.settings.Castetingsdebugaction
- Let the other fields be empty and press Check button in the lower right corner.
- In molded troubleshooting setting panel that pops up, scroll down to Connection and activate The bypass unit auth.
This solution forces the opening of cast troubleshooting settings and allows you to enable the Bypass device option (ie it allows you to turn off device approval) and partially fix the problem. You should now be able to cast from apps, and the Google Home app will also partially work.
When Google rolls out a solution, you can convert the steps above to disable the option and return to the original settings.
Other methods
Redditor has also shared other methods. You can do the same steps above, but use ADB instead of an Activity Launcher app. If you trust Chrome and browser-related casting, you can add the expired certificate as a root to trust, which bypasses expiry date-checks. You can check out the original post for instructions on these methods, as the GUI method is the easiest to follow and should work for most use cases.
Solution to fix device setup with the Google Home Android app
If you ended up the factory resetting chromecast, you must re -set it before you can use the steps above. While we recommend waiting for Google to issue a solution, there is a solution that you can try out if you are impatient.
The simple solution for setting up Chromecast with your phone is to set your phone’s date before March 9, 2025. This should then allow you to go through the Chromecast setup process without throwing authentication errors.
When Chromecast is set up, you can set the phone’s date correctly and follow the solutions mentioned above to fix the casting problem. The success rate of this solution is a mixed bag, so try your luck.
Did these solutions help to fix your casting problems on the second generation of chromecast and chromecast sound? Let’s know what worked in the comments below!