This morning I got 5 “problems found” in orange each saying “Invalid context during scan”.
1.) Browser (standard android broswer v. 4.04-37
2.) Avast Mobile Security (AMS detected itself???)
3.) Settings (android settings)
4.) Home screen
5.) Google Search
What does this mean? I looked at the on-line manual for AMS and didn’t see anything that helped. There are options to uninstall, report FP, ignore, and resolve all. Everything seems to be working fine on the phone so I haven’t taken any action. If I do experience any problems before getting a response, I’ll have to restart the phone and see if that clears things up.
the latest virus definitions got corrupted. We already took them down and are working on releasing a fixed version, but it might take a bit more time to do so just hang on, please. Sorry for the inconvenience caused.
Just wanted to be sure that your advice is for folks with this problem to do nothing… and it will be straightened out when you push out the next batch of “definitions”?? Is that correct?
that is absolutely corrent and those definitions are already out so you can update them manually (AMS-Settings-Updates-Check for updates now) or you can wait for the app to pick them up automatically.
I just tried the manual update and I get this message: The downloaded virus definitions were invalid. Please try again later. I also have the “automatic updates” on. Any suggestions on how to the update?
it might take a little bit of time for the new definitions to arrive at the server near you. I think that if you wait for a few minutes and then try again, it’s gonna be fine. It might also help to try it a few times right now, sometimes the wireless connection currupts the file (it will stop loading in the middle of the file for example).
At what point does the “definitions were invalid” update message become an issue? I’ve read the Avast staff posts concerning corrupted definitions and wi-fi connections and to keep trying the download, but it seems like the “definitions were invalid” message comes up so quickly when manually checking for an update that there is something else going on.
My other identical phone that was NOT impacted by the bad definition file manually updated as it normally does. The phone that DID have the bad definitions today puts out the “definitions were invalid” message almost immediately like it’s not even connecting with the server to check.
Just curious because I’m wondering if a corrupted def. file is keeping it from updating properly.
I am still getting the “downloaded definitions were invalid message” instantly on my Android phone as Klinker reports. No problem with getting the update on a Nexus 7 though.
I’m still getting the “invalid” messages too. I switched from wifi to wireless just to check, and it took longer, but the same message appeared. I’m in Amsterdam.
Please be patient, now we are releasing the new version to the Play (in few minutes will be there). Please update the application, or, in case it does not help, reinstall it from Play. Apologies and thanks.
I attempted to use the Google Play app update to correct the problem, but it wouldn’t update…just kind of stuck there, don’t know why. Uninstalled, re installed, updated with new virus definitions and obviously everything seems fine with the new, clean install. Way easier re installing Avast on a phone than re installing Avast on my PC so no big deal.
