As reported here:
https://github.com/jenkinsci/google-play-android-publisher-plugin/pull/25

When uploading bundles over a certain size, Google Play may reject the upload with a warning, resulting in this output from the plugin:

Upload failed:

• The installation of the app bundle may be too large and trigger user warning on some devices, and this needs to be explicitly acknowledged in the request.

When uploading a bundle, there is a ackBundleInstallationWarning flag which gives this vague description:

Must be set to true if the bundle installation may trigger a warning on user devices (for example, if installation size may be over a threshold, typically 100 MB).

The PR above solved this problem by adding a new checkbox in the job config, which would then set this flag when performing the upload. Which would work and seemed reasonable.

However, I don't see any reason to make users configure this:

• I was unable to find any documentation describing this "warning on user devices", so there's no way for us to provide meaningful documentation for users of this plugin about why this new checkbox exists.
• If Google Play causes this plugin to reject a user's bundle when uploading, they'll just reconfigure the job to enable the checkbox. But what's the point? Why not just have it enabled by default?
• I was able to upload small bundles, with this flag enabled — so there doesn't seem to be any reason not to alway set this flag.

I will enable the flag for all bundle uploads, mention it in the changelog, and README.
If someone can point to some useful documentation at some point, we can link to it.

If everybody's uploads start failing, or Google Play somehow starts showing weird warnings on users' devices, then I guess we'll hear about it pretty soon (and can then press Google for some useful documentation)… ¯\\\_(ツ)_/¯