I’m using a Samsung Galaxy Tab. OS is updated to the latest version. However, I’m unable to install the app from the Google play store. It downloads correctly, but then I get the error in the screenshot.
Unfortunately, this is beyond the scope of our application. This error message comes from the Play Store, not from us. Your device specifications look fine, so that should not be an issue!
Perhaps it was just temporary. What happens if you try it again now? Perhaps even on a different internet connection?
You mention that you have cleared the cache. What steps did you take to do this?
And did you click the link in that error message and follow their instructions?
That is what sounds really strange. However I’m sure I’ve updated it in the past, after removing the beta. And I’m also sure there isn’t any “Navigraph” installed at the minute.
I shall dig deeper - perhaps there are some spurious packages which haven’t been removed correctly.
That is weird indeed! We do not manually add files anywhere, the app itself is self-contained. If uninstalled, there should not be any unusual traces left on your device!
The closest error I have seen is when installing a new application version without changing its internal “build version”, which the Play Store uses to determine the app version. In that case, you get a similar (but not identical) error when installing it. Such a scenario is impossible for you to get in since the Play Store enforces correct versioning on their side before a release is possible.
There seem to be many resources on debugging this error out there online, including detailed steps on how to use ADB to do this on a system level. I wish you the best of luck in tracking this down! In case you need it, the bundle identifier of our app is com.navigraph.chartsrn.
ok… here’s an update from me. Had to go in debug mode but the actual error was
“Can’t install because provider name com.navigraph.chartsrn.blobs (in package com.navigraph.chartsrn) is already used by com.chartsrn”
Not sure what this com.chartsrn was, perhaps some spurious package left over by the beta? no idea. Anyway, I’ve removed it via terminal, and now it works