This is because PixelDroid has [dependency verification](https://docs.gradle.org/current/userguide/dependency_verification.html) enabled.
Dependency verification is useful to protect against supply chain attacks.
Only dependencies which are in the `verification-metadata.xml` file are allowed to be used.
In the top toolbar, go to ``Edit Configurations... > Gradle `` and click on ``+`` in the top left corner to add a new run configuration. In the field ``Run``, write the command that triggered the dependency error, which in your case is probably ``assembleDebug`` (command executed when pressing the play button) and give it the arguments ``--write-verification-metadata sha256``.
However, this means that whenever the dependencies change (for example updates or new dependencies),
we have to update the `verification-metadata.xml` file. To avoid doing this manually, you can follow
the following steps:
In the top toolbar, go to ``Edit Configurations... > Gradle`` and click on ``+`` in the top left corner to add a new run configuration.
In the field ``Run``, write the command that triggered the dependency error,
which in your case is probably ``assembleDebug`` (command executed when pressing the play button) and give it the arguments ``--write-verification-metadata sha256``.
