U-Verse App: Can't log in, stuck in endless authenticating loop

@roanwight 

Can you confirm you’re on latest version of Android available and same for U-verse app?

Yes, both are up to date. 

Same here. Reloaded on samsung phone and tablet. endless authentication  lop.not good and  frustrated

What worked on my android phone: create a new sub-account. The new sub-account is a new additional email account. You will then use the new email+password for the app login...

On a desktop/laptop/tablet login to att.com using your original primary ATT email address. Then create a new sub-account...

This got the uverse app working again for me after being locked out for two months.

I uninstalled and reinstalled the app on my android phone as a precaution before trying the new login. 

Hope this helps - Joe

Wow, seems like a tedious workaround to just to use an app for a service you pay lots of money for! But thank you for the suggestion; I will try tonight to see if it works for me.

@roanwight 

Personally I don’t see it that way.  Att is making us go back to the original login access when the app was first introduced, unlinked from all other emails we might have. I can understand this because U-verse TV now belongs to DirecTV and it’s likely important to keep things separated.   

While you’re poking around in the profile management section, reconfirm which email you used when first establishing service, aka your U-verse member ID.  All subaccounts will fall under this master userid.  

I can see your reasoning and might be more inclined to agree with you @gr8sho if AT&T had sent out any communication to this effect. The onus shouldn't be on the consumer to infer this intent from an app ceasing to work. 

@roanwight 

Increasingly, companies have become tight lipped about communication.  Atthelp has stated there is a problem.  Whether anything changes is anyone’s guess.  But if you really want to use the app now, there is a way.  Many of us can and are using it.  It’s your choice whether you want to make the effort to learn the method and get it working for yourself.  

Can you help me by showing me where AT&T has stated it understands there is a problem? And if it acknowledges a problem exists, why wouldn't it suggest a solution? Also, why would companies feel the need to be tight-lipped about communication, especially about something as minor, relatively speaking, as a workaround for an app?

<shrug> They have to answer for themselves.  Maybe its a new legal method to avoid perjuring themselves.  

But seriously why continue to grouse over the matter?  The system is working in a very specific way and its been explained in this forum innumerous times hints and tips how to make it work.  Use them or don't.  Good luck.  

No grousing here. Simply questions in response to your statement as to where I might find AT&T's acknowledgment of the problem, and where else such a solution has been explained, if not from AT&T directly. Sorry if this comes across as rhetorical; I'm asking sincerely: Where might I find this information you say exists? 

Can you help me by showing me where AT&T has stated it understands there is a problem? And if it acknowledges a problem exists, why wouldn't it suggest a solution? 

Posted 4 months ago to this thread:

After further investigation this seems to be a known problem. This has been reported and they are working to get this resolved.

 I know....4 months ago is ridiculous but it WAS posted.

Thank you, @skeeterintexas . Yes, four months is ridiculous! And it still doesn't appear AT&T offered a solution; rather, clever users had to figure it out for themselves, which is simply mind boggling. Like selling someone a car, disabling the start button and leaving it to the owner to figure out how to hotwire it. 

They may never change anything.  Uverse is at end of life.  You can sit and hope they do something, or deal with what we got and make the best of it.  The app has a remote control function that hasn’t worked since I can’t remember when.   Meh.  
There are other services out there BTW.  

As of last night same thing to me on app on iPad, phone

Obviously it’s a back end issue (or app needs update to macho IOS update?) please fix issue