My longest SMS thread no longer opens :(

[waqqas31]

The loading ellipses show up for 2 seconds, then the messages app closes altogether and I'm taken back to the Start screen.

I can still send a message to that contact, but I can only read incoming messages from them either via toast notifications or from the preview lines in the main messages app view.

Alas, after a lot of research, I gave up, deleted the thread and started a new one, which works as it should.

Mind you, ALL other threads opened like they should.

Has this happened to anyone else?

 

[rdubmu]

Turn your phone off than turn it back on
Sent from my Nokia Lumia 920 using Board Express

 

[Justin429]

Yes the same thing happened to me. I was in a panic, because I would receive messages and as you said, they were visible as toast, but I wouldn't see them when I opened the conversation. I tried everything including soft reset. The only thing that worked was deleting the thread. Didn't count the messages, but it is probably some power of two like 1024 or 2048 max before it stops adding additional messages to the conversation thread.

IMHO, the phone should delete messages from the top in order to make room for them at the bottom. Perhaps this is worthy of a bug report to Microsoft.

 

[Coolknight1968]

That is lousy... Thx for telling us!

 

[foxbat121]

Yes the same thing happened to me. I was in a panic, because I would receive messages and as you said, they were visible as toast, but I wouldn't see them when I opened the conversation. I tried everything including soft reset. The only thing that worked was deleting the thread. Didn't count the messages, but it is probably some power of two like 1024 or 2048 max before it stops adding additional messages to the conversation thread.

IMHO, the phone should delete messages from the top in order to make room for them at the bottom. Perhaps this is worthy of a bug report to Microsoft.

No, the messaging app probably run out of memory. It happens on other platform as well. Deleting messages automatically will be bad in many cases. You should keep your own messaging inbox clean. Old messages are not free meals. They take up memory and storage.

 

[Justin429]

No, the messaging app probably run out of memory. It happens on other platform as well. Deleting messages automatically will be bad in many cases. You should keep your own messaging inbox clean. Old messages are not free meals. They take up memory and storage.

Without getting too technical, this is what I said. That's why I mentioned the binary limit, e.g. address space.

 

[th0mas96]

Nope, it won't be too much messages from one contact (I have a conversation, maybe 5 months old, roughly 300 messages daily). Can you ask the person you've written with to show them your chat? Most likely it's some encoding stuff Windows Phone doesn't support, so if the other person sent something strange, contact Microsoft and they'll hopefully fix it.

btw, this really can happen. Even apple (I know, you all hate them ;p ) had a really funny bug in OSX: typing File:/// (the dialogue for accessing local files) would crash any app with a normal text input. So I really hope you can spot the thing that crashed the app (and maybe reproduce it? of course in a seperate chat). Good luck! But I really don't think it's the length of a message or the sum of it, I'm a real tet junkie and never had a problem ^^

 

[Coolknight1968]

Thx for picking this up, I cleared up a thread that is real important to me as to not lose it!

 

[waqqas31]

Nope, it won't be too much messages from one contact (I have a conversation, maybe 5 months old, roughly 300 messages daily). Can you ask the person you've written with to show them your chat? Most likely it's some encoding stuff Windows Phone doesn't support, so if the other person sent something strange, contact Microsoft and they'll hopefully fix it.

btw, this really can happen. Even apple (I know, you all hate them ;p ) had a really funny bug in OSX: typing File:/// (the dialogue for accessing local files) would crash any app with a normal text input. So I really hope you can spot the thing that crashed the app (and maybe reproduce it? of course in a seperate chat). Good luck! But I really don't think it's the length of a message or the sum of it, I'm a real tet junkie and never had a problem ^^

I will check this out tonight and post if I find anything funny!

 

[waqqas31]

I will check this out tonight and post if I find anything funny!

Just to let any new readers know, I did not end up finding anything out of the ordinary when investigating this.

I was quite upset, but decided to persevere with my Windows Phone 8 adventure.

 

[thesmithiz]

I had a similar thing happen yesterday with a group messaging involving pictures that I sent. I was taking picture of my son in the pool and sending them to my wife and daughter, as they replied and I replied back at a point I don't recall I was having difficulty typing...the screen would go back and forth between showing the keyboard display and then not. I closed the messaging app and cycled the power off and on which fixed that problem. After a couple of more pictures and dialog back and forth I was able to open the message thread, I could see the thread in the list and that they had replied but when I selected it to open and read it would briefly show the thread and then close. I could open any other thread in the list just not that one. I tried a soft reset twice and that didn't fix the problem so I deleted the thread and took another picture and sent again and the problem never started again. My 928 has the new update and group messaging is turned on....