Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

unread messages ? its not in the right spot #41

Open
GoogleCodeExporter opened this issue Apr 11, 2015 · 3 comments
Open

unread messages ? its not in the right spot #41

GoogleCodeExporter opened this issue Apr 11, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

What steps will reproduce the problem?
1.
Collection<SMSThread> smsThreads = voice.getSMSThreads(voice.getUnreadSMS());
        for (SMSThread t : smsThreads)
        {
            Collection<SMS> allsms = t.getAllSMS();

            for (SMS smsind : allsms)
            {
                if (smsind.getContent().contains(passcode))
                {
                    String emergencyMsg = smsind.getContent().replaceAll(passcode, "");
                    OsisUserDatabase oInsertOsisDatabase = new OsisUserDatabase();
                    List<String> phn = oInsertOsisDatabase.getAllPhoneNumbersSendSMS();
                    for (String oPhn : phn)
                    {
                        String destinationNumber = oPhn;
                        voice.sendSMS(destinationNumber, emergencyMsg);
                    }
                }

                voice.markAsRead(t.getId());
            }
        }

2.
3.

What is the expected output? What do you see instead?


I expect to on get a collection of unread messages

What version of the product are you using? On what operating system?

1.14

Please provide any additional information below.


There must be a way to parse out the unread messages.  It would be good if you 
could add a function instead of getAllSMS to just getALLUNREADSMS

Original issue reported on code.google.com by stevenco...@gmail.com on 3 May 2012 at 3:45

@GoogleCodeExporter
Copy link
Author

[deleted comment]

1 similar comment
@GoogleCodeExporter
Copy link
Author

[deleted comment]

@GoogleCodeExporter
Copy link
Author

I think this is more a feature request than a bug.  Am I incorrect here?  It 
seems also that you have written code to solve your own problem?  I just want 
to be sure.

Original comment by malone.j...@gmail.com on 14 May 2012 at 3:43

  • Added labels: Type-Enhancement
  • Removed labels: Type-Defect

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant