Taplytics Release 1.11.6

1. Change base method used for finding views.

   For a while, Taplytics relied on findViewById in base viewgroups to find that needed to be modified. This became unreliable over time as the applications changed (IDs can change!), so a long while ago we added a fallback which would check the resource identifier instead (essentially the string name of the view).

   This proved successful, but then there existed the small probability that a new ID would be generated for a view that would match up with the previously generated ID.

   The probability of that happening was extremely small, but it got picked up in a test we ran.

   So from here on out, we are now going with the identifier first, and ID second. This DOES mean that if you change the name (identifier) of your view to something new, Taplytics will most likely not be able to modify it using the old experiment, and it will need to be set up again.

2. Fragments will now too rely on the identifier of the fragment container instead of the ID for similar reasons to the ones stated above.

3. Fixed an issue in which Android studio would output many warnings surrounding proguard and inner classes.