Unable to trace Android apps using Google Maps API

When capturing traces using GAPID on such an app, the app crashes as soon as the map is about to become visible. The issue is consistently reproducible using a basic map app (as generated by Android Studio, if need be I can always provide an APK).

My best guess would be that this is due to the actual map rendering occurring in a different process owned by the Google Play Services. The actual app crash is accompanied by a log like this, which would tend to confirm my suspicions:
```
03-30 15:56:35.911 9720 10718 F libc : Fatal signal 11 (SIGSEGV), code 1, fault addr 0x10 in tid 10718 (GLThread 182301)
03-30 15:56:35.982 3379 3379 E audit : type=1400 audit(1522418195.974:33937): avc: denied { search } for pid=10738 comm="crash_dump64" name="com.google.android.gms" dev="dm-1" ino=1376453 scontext=u:r:crash_dump:s0:c512,c768
```

I would perfectly understand if calls related to the map could not be traced, but avoiding the app crash would definitely be an improvement! Oh, and thanks for this wonderful tool :1st_place_medal:

## Current work-around

This might not suit all needs, but just making the map view invisible in the app prevents the crash.

## Environment

* host running GAPID: Ubuntu Linux 17.10
* gapid: 1.0.3
* phone running the app: Galaxy S8 / Android 8.0.0 / Google Play Services 12.2.21