Table of Contents

This release fixes various crashes and bugs, the most important one being crash reporting itself. I have used the opportunity to switch from Fabric based Crashlytics to Firebase based Crashlytics.

If you experienced a crash in 1.11.1, please enable crash reporting and try to reproduce the crash. I was able to fix some crashes with the limited data Google Play provides, but that data lacks crucial details like error messages and whole-process stacktraces.


  • Crash after granting storage permission
  • Crash when canceling loading early
  • Crash when importing config on device without ACTION_OPEN_DOCUMENT
  • Crash when stream is detected as failed
  • Crash when reading circular dependent config
  • Crash reporting not working

This crash was especially mysterious - if you have a complicated setup with remotes referencing other remotes nesting multiple levels, some nested remotes may no longer behave as expected, and I’d like to hear from you.

I have also added a new page that explains the bug reporting process.

Note: Only distributed on Google Play alpha, superseded by 1.11.3.


Please enable bug reporting in Settings > Logging: “Send anonymous crash reports” (Privacy Policy).

You can also also create a bug report from About > Report a bug which will prefill a new Github issue with technical details like your Android version and CPU architecture. You can then add more information about the issue itself and create a public bug report.

– x0b