I’m not a rover and havent used that feature. But if you believe its a bug maybe add it to polo issues, might gain a bit more traction there. But either way, here’s a little bump for ya.
You’ll need to turn DEV mode on and export the json file of the operation in question, so we can take a look, Post it back here.
The last rove I did worked fine for me but can you confirm that after you entered the BREAK command, you confirmed thet change in both the gridsquare location AND the park details?
Thanks for quick response. I can verify the park changed but I honestly didn’t pay attention to the grid square. The only thing I did notice was deselecting previously active park with the “-” symbol did not work, only selecting the new park below with the “+” sign replaced the park.
BTW, I am trying to export the database but am having some issues. I have a file that is sent directly to my email that is called “polo.sqlite” but I have no option to save or download.
OK - you need to have a different location (gridsquare) to trigger the “break” correctly. Check again next time.
polo.sqlite is the database from the device. Unless you have software to read this file and knowledge of how to interpret it, it’s only for use when you manually move the database from one device and over write another one. Or you are asked to forward it to someone here for further examination.
You can use the “Remove.. from this operation (red text) link to remove a park, then add a new one… If you add a new one, before you remove the old, the grid will not be reset. But just make sure you have a new grid each time.
the json file export is for the operation - not the device. After you enable DEV mode, go the operation settings and you will see a json export option.
But I think this is solved now - based on you not ensuring a change of grid/location