Unable to login after last git updates about pialab-back HOT 6 CLOSED

Hello @daniel84, I can't reproduce your bug. Can you give me informations that appears in the symfony log under var/log/prod.log (or dev.log if you're in dev env) ?

from pialab-back.

Hello @PapsOu, you can find the dev.log from my dev env in the attached file.
It is the portion regarding the moment when I click on the Login button.
LoginError.txt

from pialab-back.

Could you give me more informations if you're in dev env ?

Open the profiler, search for the GET /profile item and go to Exception section. Please give me a screenshot or a text copy of the full stack.

Be sure to have you vendors sync with the composer.lock file (run a composer install). Also, please check in database that the pia_user, the one you try to log in with, have it's own user_profile entry.

from pialab-back.

To be sure I've deleted the vendor folder and the composer.lock file and rerun the composer install command.
I also controlled the pia_user and pia_profile tables and in pia_profile table I have the correct user_id for my user...
You can find the full stacktrace of the exception from the Symfony profiler of GET /profile item.
StackTrace.txt

from pialab-back.

Thanks for the stack trace.

The unserialize fails when trying to execute directly.

Do you have cleared the cache ? Please make sur the cache is fully cleared (if it is on a dev env, you can delete everything into var/cache/ folder : rm -rf var/cache/*. I know that JMSSerializer uses cache to store mapping metadatas, so the problem maybe due to an invalid cache state.

from pialab-back.

It was indeed a cache problem.
I deleted it and everything works now!
Thank you very much @PapsOu

from pialab-back.