Lately this error is popping up every now and then. This is something I havent seen before, came this week or last week.
For some time It seems to be a very frequent demand for refreshing my session in create (“session ended/you are logged out”) I need to reload the create window many times per day (my guess 3-5 ).
Im usually logged in to two environments in create at the same time, could this be causing trouble?
We are aware of the error “Ampsession already has socket assigned” and is something our dev team is looking into.
However, 3-5 times a day is more frequent than expected. I have noticed that when I change Wi-Fi networks, I will usually get this error. Are you by any chance switching networks or working from a location with weak signal?
Do you know when this started to occur? And do you know if other developers in the same solution experience the same? And, have you tried working in that solution from different locations / network (just to verify that unstable network connection is not the issue)?
PS, to other developers: If you experience similar issues in your solutions - let me know.
I’m not sure, but I believe I’ve had this issue less frequently for several months. This past week the frequency has gone through the roof, for some reason. I just now noticed I’ve been switched to our guest network rather than the normal one, so maybe that’s why. I’ll try to switch network for a while and let you know if this changes anything.
I receive these messages every second day or something, and have noticed they sometimes occur when leaving a Teams meeting and going back to my desk and connecting to my monitor. I also have a colleague who said he received a lot of them when sitting on his home office and using a VPN
I cannot recall when I get this ampsession message but I still have issues being randomly disconnected/logged out from Create while I am working. This happens a few times per day, sometimes more.
The process of getting a new version of appfarm is not exactly user friendly.
Here is a walk through of what happened.
What you can´t see is that it was an update banner in the back (screenshot 2) that was impossible to dismiss. this only happened 30 seconds or so until the Oh snap message arrived.
Then I had to change solution since it was locked, then change back. After reloading a few times I was finally back where I was…
This has only been getting worse, and I experience it 10+ times a day (the “AmpSession already has a socket assigned” message), and it usually resets some of my progress, meaning I often need to go back through my work to check what changes has been undone by the message.