Hi,
I've got a set of apps out on the app store that each support... everything. Right back as far as Epix.
The code is mature as in it has been running for a long time, successfully, without complaints or obvious errors.
It has a feature to store and reload profiles that is essentially a string concatenation (to serialise) and string splitting (to deserialise) operation.
For every single device I own, and in the simulator, on every single device I've tested, the serialise / deserialise process is flawless.
But...
I have a user report (along with supporting screenshots) that shows the following, incredibly weird, utterly unsupportable and inexplicable behaviour on Forerunner 230 which is a CIQ1 device, and a device that I do not own:
1. The first profile that is serialised works perfectly.
2. The second profile that is serialised works perfectly but it corrupts the first one.
It is literally not possible to have more than one profile stored as saving the second will always corrupt the penultimate profile.
THIS MAKES NO SENSE AT ALL. For one thing, my code does nothing to previously stored profiles... once a profile has been saved, it is simply a long string stored in application storage properties like any other setting.
From the screenshots, it looks as if the corruption is to eradicate the separator I use (a pipe character | ) on the stored, corrupted, profile.
Is there anything I could be hitting here that I had not previously considered? Is there a memory limit that Garmin might handle by randomly selecting characters to delete (!)? Is the pipe character a problem character or restricted character for any purpose? Or is this a bug that I should submit a bug report on?
And... just as much of a hail Mary pass... is there anyone with an FR230 who could verify the bug report?
Thanks,
Befuddled of Dublin
..
