Issue with the Google Messenger app after recent app update?

[Sajo]

Has anyone else experienced an issue with the Unread / badge count not clearing on the Messenger app icon, after the most recent app updates? The app has been working great for me since I bought this phone, and previous updates have been good. The newest one was version 2.1.161, I believe. The new app update did claim that it added Unread message counts on supported phones. Since the Z series already has an unread count built-in, I think that's causing the issue. After updating yesterday the unread count will not clear after reading all new text messages. I tried the usual steps > clear app cache, clear app data, clear all app cache, clear system cache, reboot phone and had the same results. I opened the Message + app that also comes pre-installed on our Z phones, and selected Yes to use it as default, and the messages that were just read in Messenger were showing as unread in Message +. So I opened each one then switched back to Messenger as my default SMS app and the unread count would clear. It appears that the new Messenger app is not really marking the new texts as "read". There was another app update this morning (for me) and Google changed the app name to Android Messages, but the problem persisted. Tonight, I found an older version on APK Mirror and loaded it and the unread count feature is working correctly again. That kind of proves to me that it is the new app update that caused the problem. Just curious if anyone else (with or without a Z series phone) has experienced this also? If you use the stock Messenger app (the blue & white icon) and the unread count works good now, you might not want to update the app until Google fixes the app.

 

[Preach2k]

I had the same issue. I thought it was Tesla counter on the Nova Launcher causing the issue. It happened also with missed calls.

Sent from my Pixel XL using Tapatalk

 

[Jonny Kansas]

I had the same issue. I thought it was Tesla counter on the Nova Launcher causing the issue. It happened also with missed calls.

Sent from my Pixel XL using Tapatalk

If it happened with missed calls, that WOULD be the Tesla counter. Messages doesn't handle calls.

Sent from my Pixel XL

 

[Preach2k]

If it happened with missed calls, that WOULD be the Tesla counter. Messages doesn't handle calls.

Sent from my Pixel XL

When I cut off the the the Tesla the counter cleared. Kept it off for a few days cut it back on and the messenger counter is working again!


Sent from my Pixel XL using Tapatalk

 

[redbert31]

I don't have the unread/badge count appearing on my Google message app currently and I don't think I ever had it on this app. I have a Moto Z force and I will try what you did and see what happens..I don't mind not having the count displayed on the app but I like to get the app working like it should, so I'll try to correct it tomorrow when I have more time to play with it. Thanks for letting us know

Sent from my XT1650 using Tapatalk

 

[Sajo]

I don't have the unread/badge count appearing on my Google message app currently and I don't think I ever had it on this app. I have a Moto Z force and I will try what you did and see what happens..I don't mind not having the count displayed on the app but I like to get the app working like it should, so I'll try to correct it tomorrow when I have more time to play with it. Thanks for letting us know

Sent from my XT1650 using Tapatalk

I'm not sure I would do what I did in your situation. If it's not causing problems for you, maybe leave things alone? Just a thought.

Sent from my XT1650 using Tapatalk

 

[redbert31]

I'm not sure I would do what I did in your situation. If it's not causing problems for you, maybe leave things alone? Just a thought.

Sent from my XT1650 using Tapatalk

Good thought! Sometimes it's better not to fix what ain't broke!

Sent from my XT1650 using Tapatalk

 

[Sajo]

Looks like folks are starting to beat-up Google a little bit in the Play Store app review section; so this may affect more than just the Moto Z series phones. Hopefully they push out an app update soon to correct this. Just FYI: I am using version 2.0.768 and the Unread counter works correctly.

 

[chasman]

My z force is doing the same thing. Keeps the numbers in the text notification. The only app fix I found was to go to message+ app. This will show your text as unread. But once you read them the numbers go away. You must stay on message + because if you go back to message the numbers will start to grow with each received text.

 

[chasman]

the new software update 3/2/2017 did not fix the text notification number issue , software update NCL25.86-11-4-6-5

 

[Sajo]

the new software update 3/2/2017 did not fix the text notification number issue , software update NCL25.86-11-4-6-5

You received a new software update today?

The issue is in the app itself, so no phone software version update will fix it. Google will have to fix it with a new app update.

If you look at the app reviews on the play store you will see this is affecting multiple phone models, not just Moto.

Sent from my XT1650 using Tapatalk

 

[Sajo]

My z force is doing the same thing. Keeps the numbers in the text notification. The only app fix I found was to go to message+ app. This will show your text as unread. But once you read them the numbers go away. You must stay on message + because if you go back to message the numbers will start to grow with each received text.

If you really want a fix, download Google Messenger version 2.0.768 from APK Mirror and install it. Just don't let the Play Store app auto update it and the unread message count works great with that app version.

Sent from my XT1650 using Tapatalk

 

[k1ngr4t]

Ever since Nougat I have quite a few issues with notifications actually, including this one. Though I thought it was a Messaging bug moreso than a Nougat bug. But in fact I have quite a few issues. I don't want to complain too much cause I haven't done an FDR yet hoping some of them would sort themselves out like usual, but they haven't, so I probably will this weekend.

I never had any problems on my Turbo and only did 1 FDR the entire time I owned it, I've already done 2 for this Z Force within the first 6 months but something new keeps arising...frustrating! But still a great phone. I'll be keeping an eye on this thread though!

I did get an Android update today I'm about to install, we'll see how that goes...

 

[Sajo]

Ever since Nougat I have quite a few issues with notifications actually, including this one. Though I thought it was a Messaging bug moreso than a Nougat bug. But in fact I have quite a few issues. I don't want to complain too much cause I haven't done an FDR yet hoping some of them would sort themselves out like usual, but they haven't, so I probably will this weekend.

I never had any problems on my Turbo and only did 1 FDR the entire time I owned it, I've already done 2 for this Z Force within the first 6 months but something new keeps arising...frustrating! But still a great phone. I'll be keeping an eye on this thread though!

I did get an Android update today I'm about to install, we'll see how that goes...

The problems you are describing seem to be way more than just the Google Messenger issue. The update today was only a monthly security patch, so no bug fixes.

Sent from my XT1650 using Tapatalk

 

[k1ngr4t]

The problems you are describing seem to be way more than just the Google Messenger issue. The update today was only a monthly security patch, so no bug fixes.

Sent from my XT1650 using Tapatalk

Yeah I'm having various woes, but concerning the Messenger app I do have this one, and I'm fairly confident I remember the issue starting after getting my first FB message after a Messenger update, those repeat notifications I get in the notification bar include showing the "successfully updated" notification, so I do remember seeing it there a few times around the time the problem started, also around the time you started this thread. It happened for a few days, then I did something and it stopped, but it has recently started again after having a conversation the other day. Very strange indeed!