Digits

only the digits line that is set up is sending and receiving texts, my normal line come to my normal number and the ring through with the notification setting just fine. It is the digits number that dose not.

The 2nd line was disconnected from the other phone

I have never received notifications since I have switched the number to the digits line...only phone calls

Yeah, I just tried the latest rev of the PC Digits app, and the web-app, once more.  The PC app started to sign in, got 3 message threads with 1-2 messages in each thread, and the displayed a connection failure: "We are having trouble with connectivity, some system notifications may not be available"

The web-app has been signing in for >10 minutes now, across three different browser attempts (Edge, Chrome, Firefox), nada, it just fails out, eventually.

I don't understand why T-Mobile doesn't seem to apply many dev/test/PM resources to this, but it sure looks like they do not, from my s/w and h/w design background.  I also don't understand why anyone would be motivated to use this.  

@BongoBob You could simply use the Google Messages app for that 2nd line and use messages.google.com on other interfaces (PC, tablet, whatever), and not hassle with this mess, but that’s a personal decision I suppose.  

I remain disappointed in what I thought would evolve into a nifty-usable interface ,some years ago now.  Given that timespan, I wouldn't hold my breath here...

Un-assigning the line did it !! Thank you so much...That was driving me absolutely crazy !

YAY!!! I love when a simple toggle gets it working again. Thanks for working through it with me :) 

@HeavenM Hmm, I went through and unassigned my line as well, logged back in, and I got 4 total messaging threads, with 1-5 messages in each.  They aren't even the most current threads, seemingly a random assortment.

Then, I cleared out all the app-cache in the WIn-Folders, re-launched the Digits app, logged back in, and I get this (see below). I de-installed and re-installed the app, same deal.  I used the Reload, and the Back→History drop-down menu items (until it was wound all the way back).  This appears to be a simple instantiation/hosting of the web-control in the PC-app version, basically?

I'll start my own thread on this I suppose (don't want to hijack this one), but I just want to show what has always been my experience with the Digits app (per my comments above), on PC, Android or web plug-in, it's incredibly, predictably, consistently inconsistent.  Maybe it's a provisioning problem with my line, but I have zero issues using Messages on my phone or the web-plug-in, otherwise, across many years now.

Maybe this works great or at least okay, if you have an iOS device; I'd expect feature/version/stability-parity across platforms for something like this, from a vendor like T-Mobile, honestly.  The 2.8 score in the Store seems to indicate otherwise, and the comments indicate similar stability issues, across many, many reviews...

Yep, @HeavenM I agree, there shouldn’t be anything else in that stack to interfere; I’d expect the Digits app to work bar-none in this case, regardless, as TMo has full access to their entire stack, unlike any other party’s app(s).

Google’s web-messaging has worked flawlessly in this regard, for a LOT of years now, and every single time I try to use the Digits (app, web, etc.), I get a few message threads with only a handful of messages on each, I’ve never gotten past that state.

As a (mostly sorta' semi-retired) full stack s/w and h/w (lots of driver/kernel test and similar) I 100% get how the parity should work here, and why the Android stack should lend itself more readily.  What I don't get is why not, and since Google's web-RCS tool works SO well, I've mostly abandoned trying to get Digits to work, until setting this thread and giving it another go.  I could set up a debugger/Wireshark on both my phone and the win-app, send simple messages to myself, and probably come up with a likely cause of the failure, but then what, what am I going to do with a pile of stack-traces, perhaps bad pointer dereferences or similar, and packet debugs?

I don't have much social presence anymore, other than FB and LinkedIn, I'm sort of an intentional non-user based on the fact I think that some of this is horribly bad for most societies (the misuse, not the use, but these days they're almost equivalent, unless  you're a very savvy user/consumer of that info, IMHO/IME).  My FB is pretty locked down, I suppose I could post there and tag them (I did do this maybe 3-4 years ago when I was really trying to get this to work, got nowhere with that team, it just trailed off eventually), and try that route again, ugh.  

Mostly, it just seems like it shouldn’t be this hard to get the carriers’ version of this to work, again, looking at the stacks of bad reviews in the store, to this end...

Hmm, so I tried to set this up on my actual phone (Pixel 8 Pro, not that it matters much), and I have zero lines eligible for use.

On ALL other devices and web-interfaces I’ve tested (tested two Android tablets, an old phone that’s basically a tablet, and 2 PCs), it allows me to set up the number (shows me all our numbers), and then shows 4 threads (the random set mentioned above), with 1-5 messages, on each.

@HeavenM I’d be perfectly happy to work with someone to debug this, at a reasonable level, but I’m not interested in multiple factory resets (already did this on one older tablet and the 2nd phone here, same deal, mostly did it so I could say it’s been done on >1 device) on my primary phone, I have a ton of customizations that I’m just not excited about reconfiguring, not that that’s likely to fix this app problem (the freshly installed app on this device) anyway…

I can set up a remote debug bridge, or an remote app-debug on Win, or whatever someone could use, that’s all very doable, in terms of that side.

I honestly have trouble believing the Android app has been put through a serious set of unit-tests and any sort of broad lab-based testing, with a variety of device/account types, but that’s speculative, obviously.

That is a lot of work for you to already put in and it is quite encouraging to see that you are still willing to do all the testing and debugging. 

I can appreciate not wanting to be neck deep in Social Media stuff. The easiest way to engage that team is to use the FB link at the bottom of this page and then selecting to send a direct message. If you post on the public page, you are leaving your name and post right out there for the world to see and could potentially start getting posts or messages from other people too. 

If you do send a message to our T-force team to have them take a look at the digits stuff, they shouldn't make you do any factory resets because you can prove that the issue is not device specific. You can copy and paste all the hard work you have mentioned here to them, or you can share the link for this post, and I am sure they would be happy to review it all and save you some effort. 

You have done so much already. If they cannot find the missing link to get the Digits working for your account, they have a ticket system that they can use to engage the right teams to do all that debugging and review on the backend. That way you don't have to put in any extra work, and we can try to find out what is going on. 

@HeavenM Hmm, so I just nuked the Digits app on my main device and reinstalled.  Same deal, the "You don't have any Digits lines"…

The ONLY way to reach this team is a PM via Social Media, for support?  Yes, that's correct, I don't want to do a public posting for whomever just happens to check my FB posts, that'd be a weird deal, but I didn't think about the PM contact.

Looking at the (Google) Play Store for the Digits app it gets an even lower rating of 2.4/5, from 5800 reviews, so that's not exactly encouraging.  At this point I was curious, so I looked at the iOS app-store, where it gets a 1.9/5 rating, at a whopping 50 reviews (this part seems a little odd, not sure if Apple prunes reviews after a time period or something), which would seem to indicate that use on iOS is nearly non-existent, probably because everyone uses Apple Messages and/or because it's so poorly supported?

We’re at:

Windows Play Store: 2.8/5 (119 ratings)

Android Play Store: 2.4/5 (5670 ratings)

iOS Store: 1.9/5 (50 ratings).

Hmm.