I have several Array objects that my application manages across different frames, and I'm having an issue where either they're not saving to files properly or not loading from files properly while testing on my device. What's odd is that out of four different arrays being managed, only one is having this issue.
What happened was my Array was saving and loading fine on PC, then when testing on iOS devices it wasn't saving/loading at all and was just coming up blank when it was supposed to be loaded from its file. I implemented a debug menu so I could manually enter values into the Array to see if it worked that way, and when I built the updated application to my device, the problem vanished, even though I didn't change anything; it was suddenly saving and loading 100% properly.
But then, a couple builds later, it suddenly started up again, not saving. I used the debug menu I implemented - and it worked... And from then on, in the same build, it was working fine...
Is this a bug with the exporter itself? I can't release this version of the app with an Array that might just not save at all or else I'll have unhappy customers. Has anyone else encountered something like this?