I appreciate the convenience of the expo XDE logging pane, automatically aggregating device logs to this console. However this is obviously only available in a development phase.
My basic question is: what happens to logging probes in a published expo application?
Are logs retained on the device itself (i.e. take up space on the device), or are they discarded in the bit bucket?
If retained, how can I access them in a production environment? I have seen the “Manually access device logs” discussion in the expo docs, however this still seems more relevant to development than production.
The reason I ask is I typically utilize a highly configurable logging utility (that wraps console.log), filtering logs at run-time. In a production setting, this is typically configured to only emit error-level logs. However, for diagnostic purposes, these filters can be dynamically re-configured at run-time to emit more log levels (typically through a hidden easter egg).
Obviously this is only useful, if you have a mechanism to access the emitted logs.
I am curious as to if there are any thoughts on how aggregating production logs could operate today, or in a future expo enhancement?
Your help is greatly appreciated.