An outstanding issue has been the "Too many queries" for address look up that some users have suffered. This is due to the limited number of accesses to the API that are allowed per day by Google. I'm sourcing other providers at the moment (and hope to announce in the next few days) but until then I've implemented a logic fix.
You can download the latest version (1.0.30) of iFindStuff from this address:
https://www.dropbox.com/s/vtnxa5ssxvroga2/iFindStuff.zip?dl=1
What's new in version 1.0.30?
B49 - "Too many queries" against devices - I've decided to implement a simple trap to limit the number of accesses made to the Google Reverse GeoFence API that has caused the "Too Many Queries" issue. Simply put, if a device hasn't actually moved since the last update there seems no point working out a new address. Of course there will be some movement between updates as the GPS system isn't 100% rock solid. But, if a device hasn't moved more than a few metres since the last update we can probably assume it's stationary.
By default iFindStuff assumes 20 m (or 20ft) movement is acceptable for a stationary device. You can fine tune this against each device using the new "Distance a device can move and still be stationary" option. The entry depends on what units you're using. If you're set on imperial then enter a trigger value in feet, otherwise use metres.
On testing I've found that this actually reduces my access to the API by over 70% with no loss of functionality. That seems a reasonable compromise until I can convince Bing that unlimited access for a few hundred users isn't going to kill their servers
B61 - Send message action doesn't send message to Master Account Device - Fixed
B62 - Inconsistent field display on Device Configuration Screen - Fixed
B63 - Typo's on device screen - fixed
B64 - Trigger names inconsistent and difficult to determine which is which - mitigated by changing some descriptions
Thanks for your support as ever - and the iPhone/iPad app is coming on
Regards
Mike