Hi,
That's normal, the 5.0.2 was released just a few days after the 5.0.1. We had not activated the update notifications for the 5.0.1 at the time.
Regarding the error, it's hard to say anything like that. Please reproduce the issue after activating the "debug" setting of the Joomla configuration. That way, you'll get the full error message.
There are only two places where a method getArgument is called in HikaShop:
1. In the file administrator/components/com_hikashop/pluginCompatJ4.php there is this code:
$class = get_class($arguments[0]);
if(substr($class, 0, 7) == 'Joomla\\') {
....
if(!empty($result)) {
$results = $arguments[0]->getArgument('result', []);
....
}
....
}
So for this call to getArgument to generate this error, it would mean that
is a string. However, if that was the case,
get_class($arguments[0]);
would return an error first and it would definitely not go inside the
if(substr($class, 0, 7) == 'Joomla\\') {
and thus the line with getArgument would be called.
So that means that the error can't be from there.
2. In plugins/quickicon/hikashop/hikashop.php there is this code:
if(!is_null($context) && !is_string($context)) {
$resultArray = $context->getArgument('result', []);
....
}
For this error to happen there, $context needs to be a string. However, in the line
if(!is_null($context) && !is_string($context)) {
HikaShop checks that $context is not a string. So again, it shouldn't be possible that this code generates the error.
What this all means is that with that short error message, I don't see what could be the problem. The full error message (with the debug activated) would probably help. However, what's likely is that one of these two files have permissions which prevented the Joomla installer from updating them when HikaShop was updated. So one thing you could check if you're able to reproduce the issue is these pieces of code I provided above and make sure you have the same as me. Chances are that the version of one of these files is not the 5.0.2 (you can see the version number at the beginning of the file) because of this permission issue I talked about. So manually copying the files from the install package via FTP would solve the problem.