I purchased a new Samsung (Q60A) smart TV and managed to successfully connect it on my Home app. However I'm unable to find the TV on certain android apps when I attempt to cast.
If I go to YouTube on my or my wife's devices I can find the TV. If I go to another app like Spotify, Facebook, etc. ; then I can't cast. Both my wife's mobile and mine are from different manufacturers. We both on the same WiFi as the new TV. We both are logged in properly on our respective Home apps and previously used chromecast to connect to our previous TV.
Sorry for the late response, but I wanted to drop in here to help.
I understand that this can be frustrating but I definitely wanted to stop by and see how I could help.
Just wanted to double check to see if you were still needing help on this? If so, what troubleshooting steps have you tried?
Please let me know.
Hi Garrett DS,
Thanks for the reply...
From my android phone I chose Facebook as a tester (global app) and cleared the cache and data, but issue still persists where when selecting cast within the app on a video I only pick up one of my Google Nests and not the TV.
Samsung TV software is up to date.
Apps on my android device are all up to date.
Netflix and YouTube on my ( and wife's) android device does show the TV when I want to cast on both our android devices. I just need to know if its an individual app issue or some configuration on Google Home, or maybe even a regional issue (we in South Africa).
Thanks for the information and apologies that you're still having issues with this.
What troubleshooting steps have you tried on your device besides clearing the cache and data?
Have you tried uninstalling and reinstalling the app? Or doing a factory reset on the device?
It could also be a regional issue as you mentioned, but I can't confirm that as we will want to make sure we have exhausted all the troubleshooting steps as mentioned previously.
I look forward to hearing from you.
No resolution as yet as factory resetting both our devices isn't feasible for us.
However, it seems to be an issue also reported on Samsung forums:
I think we can close this pending resolution from Samsung?