When running on an api 23 emulator and targeting api 23, permissions are not granted about screenshot-tests-for-android

[boourns]

just fixing the error message in this case to not suggest WRITE_EXTERNAL_STORAGE is missing would help people not get stuck

[tdrhq]

hmm, I admit I haven't been testing this on M devices.

Since the installation happens with gradle and using Android's gradle set up, don't they already set up the permissions correctly for typical instrumentation tests?

[tdrhq]

@boourns what would the ideal message here be to make it more parseable?

[boourns]

This URL is an example of maybe the same bug that is being hit here. The workaround suggested (killing the app) I don't think would work with tests.

http://stackoverflow.com/questions/33062006/cant-write-to-external-storage-unless-app-is-restarted-after-granting-permissio

@josephmbeveridge could this gradle plugin be changed to install the apk using -g? Would that resolve the issue?

@tdrhq If you wanted to be clever, determine if the app has been built against 23 and is running on 23 to emit an error specifically about this issue, but alternately just mentioning this in a longer error message would be less misleading for people who hit this case. I myself spent a day banging my head against the wall trying to figure it out :)

[josephmbeveridge]

@boourns @tdrhq Yes, changing the plugin to install the apk using -g should fix the permissions issues on api 23 emulators.

[tdrhq]

@boourns Regarding installing with -g, the installation happens from the Android gradle plugin, so I'm surprised they don't already handle this. I imagine this is an issue with all kinds of instrumentation tests.

[tdrhq]

@boourns I'm closing this task since it should be part of the Android Gradle plugin, let me know if there's something actionable on my part. Thanks for the report!

[jimgoog]

To be clear: After PR #29 got merged, setting the compile target to API22 is not sufficient. Your emulator must also be using API level 22 or lower.

@tdrhq Do you know if this was ever fixed in later versions of the Android Gradle Plugin? If it was not fixed, can you file a bug on AndroidStudio and link to the bug from here?