error after login

-- HikaShop version -- : 4.6.2
-- Joomla version -- : 4.2.4
-- PHP version -- : 8.0
-- Browser(s) name and version -- : Any (tried with brave/firefox/chromium sous Linux)
-- Error-message(debug-mod must be tuned on) -- : invalid token

Hello,
During checkout, I get an "invalid token" error message after the login process, when I click on the next step.
Now if I refresh the page after login and before I click on the next step, then there is no error message.
I tried different checkout schemes (cart + login / login alone / etc) it does not change anything.
Now the strange thing is that in order to write this post, I activated debug mode in Joomla with error reporting to "maximum" as instructed... and there was no error, not even the "invalid token". All worked as expected.
I then deactivated debug mode.... and the "invalid token" message came back when I went through checkout again (and I do clear the browser's cache and cookies between each try).
On the other hand, this is the error showing in everything.php during any checkout login process that fails:

2022-11-05T09:10:12+00:00	WARNING 91.161.42.18	assets	No asset found for core, falling back to root.1
2022-11-05T09:10:13+00:00	CRITICAL 85.187.143.1	error	Uncaught Throwable of type Joomla\CMS\Router\Exception\RouteNotFoundException thrown with message "Page not found". Stack trace: #0 [ROOT]/libraries/src/Application/SiteApplication.php(736): Joomla\CMS\Router\Router->parse(Object(Joomla\CMS\Uri\Uri), true)
#1 [ROOT]/libraries/src/Application/SiteApplication.php(224): Joomla\CMS\Application\SiteApplication->route()
#2 [ROOT]/libraries/src/Application/CMSApplication.php(294): Joomla\CMS\Application\SiteApplication->doExecute()
#3 [ROOT]/includes/app.php(61): Joomla\CMS\Application\CMSApplication->execute()
#4 [ROOT]/index.php(32): require_once('/home/mossieur/...')
#5 {main}

Hi Nicolas,
Thank you for your message. I will investigate with my host provider and let you know.
(I will also check if an extension -like Admin tool for example- is involved and need some fine tuning)

Hi,
I deactivated Admin Tools but that didn't fix the problem.
I contacted my host provider and am waiting for his answer.

You said :

nicolas wrote: An easy way to circumvent the problem would be to turn off the "show login" option of the HikaShop configuration and instead display the Joomla login module on the sidebar of the checkout page for guest users.

This is the answer from my hosting provider :

Reviewing the links you shared I can see there was much deliberation such as reinstalling a fresh copy of the core Joomla files and reimporting your database. This would help identify if there's a problem with the core Joomla files by replacing them with a fresh set. It's not said what was done by the hosting providers in this case so we don't have much information to work off of. It seems that most cases are still awaiting a resolution or weren't entirely successful.
I would recommend opening a thread there to discuss your issue with the module developers. We're more than happy to work with them and provide any information they may need about the server configuration. From my observation the error you shared is referencing core Joomla files that we cannot repair manually. Please try my first suggestions as this is the best way to initially troubleshoot, if not successful please check with the developer and let us know if they need specific information or need us to make a change.
Regards.
Eian C.
Support Specialist
A2 Hosting - Our Speed, Your Success!
www.a2hosting.com/support

OK, I found the checkout login problem which was linked to cache as seems to often be the case with "invalid token" error messages.
I went into the configuration of litespeed plugin and excluded hikashop from the list of cached component and there is no more problem with the checkout process now.
I still get the other error actually showing in everything.php during any login process (not just in hikashop checkout) but also general joomla login), , but it does not seem to affect the login process, although it seems triggered by it.
It seems to be related to joomla core itself as the technician from a2hosting mentioned.
As this is only a testing/staging website, I will look into this later while concentrating on setting up Hikashop for the moment.