Skip to content

Nightbell 3.9.0

Choose a tag to compare

@riveerxd riveerxd released this 04 Sep 18:16
· 105 commits to master since this release

Nightbell can keep a log of what it is doing, so a problem you cannot describe becomes a file you can send. Settings, About, Diagnostic log: switch it on, make the problem happen again, then read it and export it. It goes where you put it and nowhere else.

The log is written to be publishable. Addresses keep their scheme, host and port and lose the path and query to counts, so a link with a key in it cannot reach the file. Passwords, tokens, saved browser sessions, request headers, request bodies, page content and the names you gave your monitors are not in it at all: a monitor appears as the first eight characters of its id. Read it before you send it, in the app, which is why there is a viewer and not only an export button. Nothing is switched off in any build, because a setting that logs the real values is a setting that ships by accident.

Crashes are recorded whether or not the switch is on, to a file of their own, with the minute that preceded them. A crash cannot be reproduced on request.

A page monitor that overruns now says which part overran

"Page did not finish loading in 15s" was one sentence for every way of running out of time, including a page that had loaded perfectly well and then failed to produce the element you were watching, and that sentence sent a report looking in the wrong place. It names the stage it stopped at now, with the renderer's progress, what the document said about its own state, whether the load event ever arrived and how many requests were started.

Where a page reaches a usable document and never signals that it finished, it says so, and says that a longer timeout will not help, because that page is waiting on something that is never going to answer. The embedded browser had no way to report its progress, its console output or its failed sub-resources, so none of that was observable from a check. It is now.

The update notification opens the app that can install the update

Tapping "Nightbell update available", or the button inside it, opened a web page. Nightbell has been able to fetch and hand over the APK itself for several releases, and the dashboard has offered exactly that, so the notification was walking you out of the app to do by hand what the app already did for you. It opens Nightbell now, on the dashboard, with Install. A release with no APK behind it still opens its page, because that is the only route there is.

Nothing is downloaded until you press Install, and Android still asks before it replaces the app.