Skip to content

Debugging Notifications

Faisal edited this page Nov 16, 2017 · 4 revisions

Debugging Notifications

Enabling Developer Mode

To facilitate testing, you can enable the debug menu by pressing the version text at the bottom of the drawer 5 times in quick succession. A new menu item, "Dev Settings", should appear. Exit dev mode by pressing "Exit Developer Mode" on the "Dev Settings" screen.

Testing Notifications

Since the production server produces releases every month, it's easier to test if you connect to our "mock server" that produces releases on a much more frequent basis.

You should subscribe to variant "c.956A>C", as the mock server creates a new version including just that variant with a cycling pathogenicity status.

It's much easier to test notifications if you enable the following options on the dev settings screen:

  • Mock Refresh Server: connects to a "mock server" that provides a subset of paths from brcaexchange.org (which is what is queried if this option is unchecked)
  • Quicker Refresh Interval: sets the "backoff" timer to 10-20 minutes rather than 12-24 hours. Note that background tasks will run opportunistically with a usual minimum period of 15 minutes on both Android and iOS.
  • Show Version in Notify Title: adds a "(vXXX) " prefix to received notifications, which helps to show the sequence of fetched versions at a glance.

Mock Server Details

The mock server mocks the paths /backend/data/release and /backend/data/. It appends a new entry to the "versions" list every 10 minutes, consisting of a changed pathogenicity for a single variant. More details available at https://github.com/falquaddoomi/brca-mobile-mockserver (ask if you'd like access).

Clone this wiki locally