Fix flaky test

[guperrot]

Please have a look at our guidelines for contributions and consider the following before you submit the PR:

• Has CHANGELOG.md been updated?
• Are tests passing locally?
• Are the files formatted correctly?
• Did you add unit tests?
• Did you test your change with either the sample apps that are included in the repository or with a blank app that uses your change?
• Did you check UI tests on the sample app? They are not executed on CI.

Description

Trying to fix a flaky test.

[coveralls]

Coverage remained the same at 100.0% when pulling d6b9c77 on fix/flaky-test into 26718db on develop.

[guperrot]

reopened because the build never started

[guperrot]

[MatkovIvan]

@guperrot Could you please mention somewhere what exactly test is flaky?
Does it fix saveWrapperException?

[guperrot]

@guperrot Could you please mention somewhere what exactly test is flaky?
Does it fix saveWrapperException?

Yeah at first it was that, then disabling log sending in the android test uncovered some lines in the http logic.

If the test was fast enough to send logs and get an error, it would delete files as error is unrecoverable.
In most cases it was fast enough always to trigger the onPreExecute (but not go through completion) and was covering sending an http log without token and the onStart thing that way.