Android P compatibility changes

[fractalwrench]

Goal

Test compatibility with Android P preview and make any necessary fixes.

Changeset

• Make StrictMode check insensitive
• Alter the test assertion on P devices for StrictMode. The exception message has changed so that we can't parse the violation code, meaning a full description isn't possible to obtain, although we can still detect that some issue occurred.

Tests

• Local unit tests

• Manual tests with dashboard

• Read the new features + changes to find any relevant changes https://android-developers.googleblog.com/2018/07/final-preview-update-official-android-p.html

• Mazerunner scenarios. It's worth noting that unhandled scenarios don't pass because P is more strict about killing the app after an exception, and the notifier would now deliver reports on the next app launch. As the scenarios fail due to incorrect assumptions about the report, I've left them as-is until we get to a point where mazerunner is capable of verifying multiple API levels at the same time.

Review

For the submitter, initial self-review:

• Commented on code changes inline explain the reasoning behind the approach
• Reviewed the test cases added for completeness and possible points for discussion
• A changelog entry was added for the goal of this pull request
• Check the scope of the changeset - is everything in the diff required for the pull request?
• This pull request is ready for:
  • Initial review of the intended approach, not yet feature complete
  • Structural review of the classes, functions, and properties modified
  • Final review

For the pull request reviewer(s), this changeset has been reviewed for:

• Consistency across platforms for structures or concepts added or modified
• Consistency between the changeset and the goal stated above
• Internal consistency with the rest of the library - is there any overlap between existing interfaces and any which have been added?
• Usage friction - is the proposed change in usage cumbersome or complicated?
• Performance and complexity - are there any cases of unexpected O(n^3) when iterating, recursing, flat mapping, etc?
• Concurrency concerns - if components are accessed asynchronously, what issues will arise
• Thoroughness of added tests and any missing edge cases
• Idiomatic use of the language

[coveralls]

Coverage decreased (-0.09%) to 74.927% when pulling 36df875 on android-p-compat into 397d771 on next.

[coveralls]

Coverage decreased (-0.09%) to 74.927% when pulling 36df875 on android-p-compat into 397d771 on next.

[coveralls]

Coverage decreased (-0.09%) to 74.927% when pulling 36df875 on android-p-compat into 397d771 on next.