build(deps): bump leakcanary-android-no-op from 1.5.1 to 1.6.3

[dependabot-preview]

Bumps leakcanary-android-no-op from 1.5.1 to 1.6.3.

Release notes

Sourced from leakcanary-android-no-op's releases.

v1.6.3

See Change Log

v1.6.2

See Change Log

v1.6.1

See Change Log

1.6

This release was short lived due to #1058

v1.5.4

No release notes provided.

v1.5.3

No release notes provided.

v1.5.2

No release notes provided.

Changelog

Sourced from leakcanary-android-no-op's changelog.

So, what's changed since 1.6.3?

Everything. The LeakCanary codebase went from ~6000 lines of Java to ~16000 lines of Kotlin, excluding comments & blanks.

!!! question "Isn't Kotlin supposed to drastically reduce the amount of boilerplate code?" Absolutely! And it did. But then, we wrote more code. LeakCanary used to depend on HAHA, a repackaging of perflib, the heap dump parser used by Android Studio. Unfortunately perflib was slow and used too much memory, so LeakCanary now includes its own heap dump parser: Shark. The extra code comes from Shark, but also from having a lot more automated tests, and an improved UI layer.

One major difference: when the app is in foreground, LeakCanary 2 will not trigger on every retained instance. Instead it will wait until the app goes in background or to reach a threashold of 5 retained instances in foreground. The analysis will then find all the leaks at once, and group identical leaks in the results UI. Please read the Fundamentals section to learn more!

Random facts

• You can customize the Leaks launcher icon and label: learn more here.
• If you long press on your main activity launcher icon, you should see a LeakCanary dynamic shortcut. You can then long press that to drop it on your home screen, and the launcher shows that it's the leaks launcher for your app.
• Out of the box, LeakCanary tracks all fragments flavors: AOSP, Support Library and Android X.
• From within the leak screen, you can share a leak to stack overflow. You can also share a heap dump, or import and analyze a heap dump from another device.
• You can run LeakCanary from your computer command line, on any debuggable app even if that app doesn't have LeakCanary: learn more here.
• The new documentation is fully searchable and includes the API documentation. Try the search bar ⤴.
• A large 160Mb heap dump uses 2Gb memory when opening it in Android Studio, but only 40Mb with Shark.

Changes since 2.0 Beta 5

• Shark CLI supports multiple connected devices #1642
• Fixed missing sources from Maven Central #1643
• Updated notification icon to avoid confusion with Twitter DM notifications, and added icons to bottom navigation bar #1648
• Automatic leak detection for support library fragments #1611

Many thanks to @AndreasBoehm, @jrodbx, @pyricau for the contributions, bug reports and feature requests.

For more details, see the 2.0 Milestone and the full diff.

Version 2.0 Beta 5 (2019-11-25)

• Major bugfix: native gc roots were accidentally ignored in Beta 4, as a result some leaks were not found #1634
• Fixed Lint warning (leak_canary_about_message string triggered multiple substitutions warning) #1630

Many thanks to @DanEdgarTarget, @msfjarvis, @PaulWoitaschek, @pyricau, @ZacSweers for the contributions, bug reports and feature requests.

For more details, see the 2.0-beta-5 Milestone and the full diff.

... (truncated)

Commits

• 31007b4 Prepare 1.6.3 release
• 64b6e5a Fix GC Root bugs that missed leaks (#1168)
• bd3de26 Keep "no leak" heap dumps (#1166)
• ba868a1 Remove unused field (#1167)
• f044c1d Fixed IndexOutOfBoundsException for leak traces of size 1 (#1164)
• a7ae33c Disable DisplayLeakActivity when not using DisplayLeakService (#1162)
• cefc33d LeakCanary.isInAnalyzerProcess correctly returns true in the analyzer proce...
• 85adede Updating repo order because AS is hangry for dependencies (#1160)
• 4702cf0 Merge pull request #1155 from KMaragh/master
• 58f776f Updated spacing in leak message. Some words were mashed together.
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Automerge options (never/patch/minor, and dev/runtime dependencies)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)