2 Messages
U-verse App on iPhone shows “Wifi Network not Found
Using iPhone 8 w/ software 14.8. Error message shows up immediately once Remote and Receiver pressed to select.
Attempts to fix:
-Reboot Wireless receiver
-Reboot Wired receiver
-Removed App on phone, and reloaded
-Power down and restart phone.
Noticed problem on Sunday, Oct 17,2021. On Oct 15th working as usual. WiFi itself does connect / work with phone.
gr8sho
ACE - Professor
•
1.5K Messages
3 years ago
@dsebenson
Go to the AppStore and leave a review there.
0
0
hcc319
2 Messages
3 years ago
Same problem. Running 15.2 on new 13 Max Pro. Have rebooted everything. iPhone on same network as AT&T receiver. Following channel 9301 instructions is no help. (Instructions say to select receiver from list when u-verse app launches but never given that option because “Wi-Fi network not found.”)
I’ve tried everything I can think of. Incredibly frustrating. Will next try to v evert to order OS. 🤬
0
0
parksandrec
Tutor
•
6 Messages
3 years ago
DO NOTHING. Your system is fine.
This is a known issue with app, version 6.4.4 build 1. No excuse that this has yet to be resolved with an app update, they have been aware of this for two and a half months plus.
0
hcc319
2 Messages
3 years ago
Thanks! Standing by.
0
0
Deborahdemick
1 Message
3 years ago
It’s been like that on my iPhone 12 and my previous iPhone. Cannot use the installed remote on the app for almost a year. “Cannot connect to wifi”. So frustrating. Get with the times AT&T
0
0
gr8sho
ACE - Professor
•
1.5K Messages
3 years ago
@Deborahdemick
Interestingly I got hit with login bug this morning and my recourse was to fully delete the U-verse app and reinstall it. Login was successful. I went to check on the remote function and instead of searching for settop boxes and failing, the app gave up immediately and said WiFi network not found. I then checked in Settings on my iPhone for the U-verse app and the option to permit access for local network is no longer present when it was there previously. Another customer had made the same observation not too long ago, and now I see it for myself. It’s up to att or directv to deal with this once and for all.
0
0