Unread indication for 2 messages rather than 1

[GoogleCodeExporter]

What steps will reproduce the problem?
1. A new text arrives
2. Smspopup notification bar icon indicates 2 unread texts 

What is the expected output? What do you see instead?
Indication for two unread messages rather than one.

After closing the popup, the icon indicates one unread message left (rather 
than disappearing). The sender is unknown and clicking on the message from the 
status bar leads to a blank message. This blank message doesn't really exist as 
it disappears when going back to the list of conversations.

What version of the product are you using? On what operating system?
V1.1.0
Android 2.1.A.0.435 (last official update for Xperia X10)

Please provide any additional information below.
- No other 3rd party sms app installed.
- Notification from native sms app deactivated and therefore not showing.
- Popup is ok and indicates only 1 unread message.
- Killing sms popup makes the blank unread message disappear.

Original issue reported on code.google.com by mathieu....@gmail.com on 19 Jul 2011 at 10:54

[GoogleCodeExporter]

I am experiencing the same issue and adding some clarification to how it occurs 
to me.

It is not fully reproducible because I don't know what makes the original 
message into a "phantom" message in the first place.  Here is what happened:
1. Received a text (hereafter called the "phantom" text) from an number not in 
my contacts.
2. Hit "Close" on popup notification for phantom text.
3. Phantom text never appeared in conversation list in native SMS app (and 
still doesn't, even though subsequent texts to/from the same phone # do.  SMS 
Backup and MightyText registered phantom text correctly.)
4. Every new text (from any number) since then shows the "2 unread message(s)" 
notification on the popup, and leaves a notification in the status bar for the 
phantom message, both as Mathieu noted.  Note that the number and text for the 
phantom text show up correctly in the status bar notification even though they 
don't in the conversation list or in step 5.
5. Selecting this status bar notification sends me to the "new message" screen 
with no number/sender preselected (what I think Mathieu means by "blank 
message" above).

Version/OS:
SMS Popup v1.1.0
Galaxy Nexus LTE unlocked/rooted, Android 4.0.2

Additional information:
- No other 3rd party SMS app installed, but I do have SMS Backup and 
MightyText, both of which registered the "phantom text" correctly.
- Notification from native sms app deactivated and therefore not showing.
- Removing SMS Popup from the ICS list of running apps does not make the 
phantom text disappear.
- Turning phone off then on again does not make the phantom text disappear.
- I have not tried uninstalling then reinstalling SMS Popup.  Please advise if 
I should.

Original comment by professo...@gmail.com on 15 Feb 2012 at 1:52

[GoogleCodeExporter]

A fully revamped version of SMS Popup is now available in the Google Play 
Store: 
https://play.google.com/store/apps/details?id=net.everythingandroid.smspopup

I am closing out all old issues/bugs that relate to SMS Popup <=1.10 as so much 
was changed in this version. Please create new issues if you see them in the 
latest update.

Original comment by adam.eve...@gmail.com on 14 Apr 2012 at 7:37

• Changed state: WontFix

[GoogleCodeExporter]

For future reference of people finding this via Google (as I did), the 
"phantom" message persisted across the upgrade to 1.2, but adding a "Delete" 
button to the popup and pressing that on the phantom message resolved the 
issue.  

(This wasn't possible in the previous version, because that one didn't have 
1.2's multi-message popup "stack" and would only display the phantom message in 
the notification bar.)

Original comment by professo...@gmail.com on 1 May 2012 at 4:14

[GoogleCodeExporter]

interesting, thanks. in v1.2.2 (not yet released but coming soon) i'm actually 
checking and trying to ignore the phantom messages altogether now I know what 
they look like (essentially empty values for all fields except the message id).

Original comment by adam.eve...@gmail.com on 1 May 2012 at 4:57