Open mcdurdin opened 1 year ago
For iOS, I have figured out how to capture the important aspects of user data - that helps drive some of the iOS unit tests about package installation & 'migration' from old versions of the app. (Among other things, this is used to facilitate migration testing from a pre-KMP app state to the current mode.) There's some manual "rigging" I set up somewhere in the unit testing area, if I recall, that I activate when I want to capture a snapshot of the Keyman app's installed state.
The other two parts, though... yeah, I don't really even know where to start.
In order to make it easier to track down root causes for issues, I'd like to try and find a way to capture more data during testing on simulators and emulators:
For iOS and Android to start with. We'd need to systematically store the data and include it when reporting issues.