iOS 5 Messaging issue

[caderousse]

I'm having this issue with text messages. I have an iPhone 4 running iOs 5.0.1.

Here is the issue: I'm on the screen reading a text from someone, say "Steve".

Then, I get another text from Steve and instead of it just adding it to the scrolling list of existing messages, I have to click "Messages(1)" (which brings me out of the Steve conversation) and see it, as if the text was from someone else.

So I guess what I'm saying is, texts from the person I'm currently texting appear as texts from other people while I'm in the main text screen.

Hope this is not confusing. Anyone else have this issue?

 

[700-Grizz]

LOL my name is steve!

Anyway mine has done that a few times and then just starts acting normal. I would first delete the conversation thread and then do a hard restart on your phone- hold power and home down till apple logo comes back on

 

[caderousse]

Ha ha thanks Steve! I will try that today.

 

[Jason black]

It think it's better that way, so it doesn't interrupt what you're reading if its a long message.

 

[BiggAW]

It think it's better that way, so it doesn't interrupt what you're reading if its a long message.

Agreed. It takes some of the chaos out of a text storm.

 

[Arelunde]

Normally, if I'm replying to a text message and the person sends another one while I'm typing, it just appears in the bubble list. The notification sound doesn't always make noise - sometimes, it's just the whoosh sound as though you just sent one yourself.

I'd have to agree that maybe a hard reset might fix what you are facing.

 

[WordMasterRice]

The problem you are having has to do with whatever the person you are talking to has set the "Caller ID" setting to in the messages settings. If you send the iMessage to their cell number then they will get it, but when they reply and the Caller ID is set to their appleID then it will look like it is coming from their email rather than the phone number, so it starts a new thread since the email is not the phone number. It isn't really even a bug, that's how it should work.

Above all, it isn't anything that a reset will fix.