I have an Android app that's deployed on a bunch of tablets my company owns and manages. These tablets are single purpose devices - they run this app and nothing else. The app doesn't ever stop unless it crashes. In fact, we use AirWatch to lock the device into single task mode, so it's more or less impossible for the app to get killed.
From what I've read, this does not sit well with Fabric, which likes to send its non fatal errors and events only once the app is killed.
What can I do about this? Can I turn this behaviour off or somehow programmatically flush the list of events and non fatals to be sent to the server?
Mike from Fabric here. There isn't a way to manually flush or push the events to our servers currently. It's not on our immediate roadmap to add in, but will update my answer if there is a change.