This may not be a real solution, but I had the same problem a few days before. After a few days of searching the Internet, I updated my application on the Play Store with some minor changes (nothing that really helps solve this error, I think).
The error just disappeared. Perhaps this is just a bug on Google Play. Therefore, if you are planning an upgrade, just do it and I think it will be resolved.
source share