You should be able 'fix' this behaviour by checking to see if the GPS has found a valid satellite fix. Post the location reported by the LocationSensor first to a variable or a label. When the label shows the location (and it is not No Address Available, then use a button to send the sms. You can also inhibit the sms by not allowing the message to be sent if the address is 'No address available" or whatever the exact wording is (yes, you need the exact wording). You can check for this as stated in the MIT LS documentation: :
Location information might not be immediately available when an app starts. You'll have to wait a short time for a location provider to be found and used, or wait for the OnLocationChanged event
The OnLocationChanged event could be the best block to place the code that will actually send the text. I would use an if..then else statement. Or you could, more awkwardly use a Clock object to poll the geocoordinate (not as nice coding).
Jim's suggestion might work too. I do not know. A problem with using Accuracy is that within a building, this value is usually going to be a large value even though what will be reported by the LS will be close enough for your app/s purposes
In my personal apps, I used to check if the latitude or longitude is 0. If the GPS does not have an initial fix, the LocationSensor defaulted to a 0 latitude; 0 longitude. If both are 0, then no fix and no address will be available. When that happens, I post a please wait for the satellite fix before proceeding. Practically, if either lat or long is exactly 0, there is no fix. I think MIT very recently modified the code to elicit the No Address when there is no satellite fix (0,0 coordinates); but do not know for sure..I'll have to look.
Try some blocks with a simple case...your app that checks a phone list is pretty complicated with several Clocks that could interfere with the OnLocationChanged event. I would get the simple sms working with the GPS on a simple version of your app, then port the blocks to your current project.
Also, be aware, there are several similar Projects in the MIT Gallery. You might visit it and see how other developers solved that issue (or avoided it).
Regards,
Steve