Command "reply" not working, says "no match for <number>"

[GoogleCodeExporter]

I'm on FroYo (Android 2.2), on a HTC Desire.
When I receive an SMS, and I try to reply using the "reply" command, it won't 
work, and say, instead, "no match for +39xxxxxxxxxx"
The number IS, in fact, saved as one of my contacts.

Note that I live in Italy (+39 is the prefix for Italy).
I noticed that it adds the +39 part even if I didn't save the number with the 
prefix.
I tried to fix it by adding the prefix +39 to the contact whom I was trying to 
reply to, but it gives me the same error "no match for +39xxxxxxxxxx"
I can only use the "sms" command (sms:<contact name>:<message>) to write SMS, 
which is OK but not very quick when all I want is to reply to the last SMS I 
received.

----What steps will reproduce the problem?

1.I receive an SMS from one of my contacts, and TalkMyPhone shows it on screen: 
"SMS from MyGirlfriend: In the end, they didn't tell anyone about the new 
teacher"
2.type in GTalk "reply:I imagined that... try calling Emanuele, please, and let 
him know"

-----What is the expected output? What do you see instead?
I'd expect to see the following messages from TalkMyPhone:
"Sending sms to MyGirlfriend
SMS sent
SMS delivered"

instead, I see:
No match for "+39xxxxxxxxxx"

-----What version of TalkMyPhone are you using?
2.03-beta, downloaded from Market

Original issue reported on code.google.com by lozeno1...@gmail.com on 27 Sep 2010 at 2:26

[GoogleCodeExporter]

Issue 36 has been merged into this issue.

Original comment by chm.duquesne on 27 Sep 2010 at 5:44

[GoogleCodeExporter]

I am having the same issue in the US on Android 2.1 using both beta 2.03 and 
2.04.  My numbers are all saved in my phone as xxx-xxx-xxxx. I didn't have this 
problem as early as last Friday.  Thanks

Original comment by nmol...@gmail.com on 27 Sep 2010 at 6:55

[GoogleCodeExporter]

I have this issue as well.  US with a Droid X running Android 2.2.  This app is 
very promising, especially if these type of bugs get worked out!

Original comment by nat...@mynarcik.com on 27 Sep 2010 at 8:34

[GoogleCodeExporter]

Same issue today; do we know if there is a fix in the works?

Original comment by nmol...@gmail.com on 28 Sep 2010 at 11:34

[GoogleCodeExporter]

Maybe at the end of the week, next week for sure.

I'll remove pattern recognition for cellphone numbers. Then it will match with 
numbers containing only digits and possibly start with + 

Original comment by Florent....@gmail.com on 28 Sep 2010 at 12:20

[GoogleCodeExporter]

I have a HTC Hero (Sprint Version) running cm6 nightly 9-05.  I have version 
2.03 (installed from the marketplace installed).  I set up the app on my phone 
(only changes i made were entering my gmail address and it's password).  I am 
able to receive sms notifications fine.  But when I type "reply: x (where x is 
the message I am sending)" I get a response back saying "no match found for: y 
(where why is the contact's phone number)

Original comment by email...@gmail.com on 28 Sep 2010 at 11:12

[GoogleCodeExporter]

i have this issue as well, is it resolved?

Original comment by KevinR.O...@gmail.com on 29 Sep 2010 at 12:08

[GoogleCodeExporter]

Thanks for working on it! We are looking forward to the fix, for now it's not 
too much of a burden to type the contact name. 

Original comment by nmol...@gmail.com on 29 Sep 2010 at 11:58

[GoogleCodeExporter]

To be merged in main branch.
Accept all phone numbers

Original comment by Florent....@gmail.com on 30 Sep 2010 at 7:19

• Changed state: Fixed

[GoogleCodeExporter]

So, where's the update?

Original comment by anonym1970 on 4 Oct 2010 at 9:23

[GoogleCodeExporter]

anonym1970: If you want this update so bad, I suggest you checkout the code and 
write it yourself (you really can, it is open-source). I would be pleased to 
integrate your patches. Otherwise please be patient, updates are coming when we 
have time to write them.

Original comment by chm.duquesne on 4 Oct 2010 at 11:32

[GoogleCodeExporter]

To clear things up: Status says "fixed" but it is not?

Original comment by anonym1970 on 4 Oct 2010 at 11:37

[GoogleCodeExporter]

Alright, I had not seen that. Florent may have fixed this without me noticing. 
If his branch is stable, the change should come quickly.

Original comment by chm.duquesne on 4 Oct 2010 at 11:40

[GoogleCodeExporter]

Didn't mean to step on your toes.

Original comment by anonym1970 on 4 Oct 2010 at 11:41

[GoogleCodeExporter]

I'm in Denmark using Android 1.5 
Here the "reply:" works fine now.

Original comment by jen...@gmail.com on 4 Oct 2010 at 2:31

[GoogleCodeExporter]

In the US and with the current 2.05 BETA, I believe the "reply" command is 
working.

Android 2.2

Original comment by nat...@mynarcik.com on 4 Oct 2010 at 3:27

[GoogleCodeExporter]

In the US and with the current 2.05 BETA, Android 2.2 Reply command still 
outputs no match found.

Original comment by zache...@gmail.com on 5 Oct 2010 at 1:52

[GoogleCodeExporter]

Sorry, either some numberformats does not work, og the application have been 
changed.
Reply to a Danish number +45xxxxxxxx outputs: "No match found"
even xxxxxxxx outputs "No match found"

Original comment by jen...@gmail.com on 5 Oct 2010 at 3:30

[GoogleCodeExporter]

It's fixed but not released.
Wait for release 2.06 if tests are ok

Original comment by Florent....@gmail.com on 5 Oct 2010 at 3:49

[GoogleCodeExporter]

Issue 70 has been merged into this issue.

Original comment by chm.duquesne on 6 Oct 2010 at 1:40