You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"I’m emailing as a number of people (including me) seem to having issues with the iRecord Butterflies app finding the locations. When you start the app it seems to find the location right away and after a couple of taps on the circle it quickly finds an accurate 8-figure grid reference for the record. However, after this the app will not budge from that first location no matter where you are on a survey route. If you have phone signal and the map loads you can of course navigate the app’s map to find the location, but if there is no signal the map won’t load and you have no way of knowing if the location is accurate or not. We have found a work around, and that is to have another app running in the background that uses real time locations (such as Google Maps or the Ordnance Survey app). To make this work though you have to leave the iRecord Butterflies app and open the other app to make that find your location, then you can go back to the iRecord Butterflies app and on the location screen it will find you accurately again. It is a bit of a faff, especially at this time of year when despite the poor season records are coming in thick and fast and people don’t have the time to switch between apps each time they record a butterfly. A few recorders are now saying they will abandon recording all the butterflies they see individually and will now turn to species lists for sites, which would be a terrible shame if they do as we will loose the beautifully detailed distribution maps that can usually be achieved using the iRecord records.
It only seems to be effecting those using an iPhone by the way. I have spoken to Android users and they don’t have an issue. We all have our location settings in the app set to always on as the app recommends, the apps and IOS are all fully updated too.
I’d really appreciate it if you could let me know if there is another work around, or possibly a roll back to a previous version of the app?"
The text was updated successfully, but these errors were encountered:
From a user:
"I’m emailing as a number of people (including me) seem to having issues with the iRecord Butterflies app finding the locations. When you start the app it seems to find the location right away and after a couple of taps on the circle it quickly finds an accurate 8-figure grid reference for the record. However, after this the app will not budge from that first location no matter where you are on a survey route. If you have phone signal and the map loads you can of course navigate the app’s map to find the location, but if there is no signal the map won’t load and you have no way of knowing if the location is accurate or not. We have found a work around, and that is to have another app running in the background that uses real time locations (such as Google Maps or the Ordnance Survey app). To make this work though you have to leave the iRecord Butterflies app and open the other app to make that find your location, then you can go back to the iRecord Butterflies app and on the location screen it will find you accurately again. It is a bit of a faff, especially at this time of year when despite the poor season records are coming in thick and fast and people don’t have the time to switch between apps each time they record a butterfly. A few recorders are now saying they will abandon recording all the butterflies they see individually and will now turn to species lists for sites, which would be a terrible shame if they do as we will loose the beautifully detailed distribution maps that can usually be achieved using the iRecord records.
It only seems to be effecting those using an iPhone by the way. I have spoken to Android users and they don’t have an issue. We all have our location settings in the app set to always on as the app recommends, the apps and IOS are all fully updated too.
I’d really appreciate it if you could let me know if there is another work around, or possibly a roll back to a previous version of the app?"
The text was updated successfully, but these errors were encountered: