CloudError: Endpoint (observeMySession)

[tlgtrn]

Node version: 20.5.0
Sails version (sails): 1.5.7
ORM hook version (sails-hook-orm): 4.0.0
Sockets hook version (sails-hook-sockets): 2.0.0
Organics hook version (sails-hook-organics): 2.0.0
Grunt hook version (sails-hook-grunt): 5.0

---

First install according to "get-started" and created "Web App"

Signed up with email address and when I try login I am facing this error.

"CloudError: Endpoint (observeMySession) responded with an error (or the request failed)."

Uncaught (in promise) CloudError: Endpoint (observeMySession) responded with an error (or the request failed).
exec http://localhost:1337/dependencies/cloud.js:649
_promise http://localhost:1337/dependencies/cloud.js:612
toPromise http://localhost:1337/dependencies/cloud.js:610
then http://localhost:1337/dependencies/cloud.js:592

cloud.js:649:33

[sailsbot]

@tlgtrn Thanks for posting! We'll take a look as soon as possible.

In the mean time, there are a few ways you can help speed things along:

• look for a workaround. (Even if it's just temporary, sharing your solution can save someone else a lot of time and effort.)
• tell us why this issue is important to you and your team. What are you trying to accomplish? (Submissions with a little bit of human context tend to be easier to understand and faster to resolve.)
• make sure you've provided clear instructions on how to reproduce the bug from a clean install.
• double-check that you've provided all of the requested version and dependency information. (Some of this info might seem irrelevant at first, like which database adapter you're using, but we ask that you include it anyway. Oftentimes an issue is caused by a confluence of unexpected factors, and it can save everybody a ton of time to know all the details up front.)
• read the code of conduct.
• if appropriate, ask your business to sponsor your issue. (Open source is our passion, and our core maintainers volunteer many of their nights and weekends working on Sails. But you only get so many nights and weekends in life, and stuff gets done a lot faster when you can work on it during normal daylight hours.)
• let us know if you are using a 3rd party plugin; whether that's a database adapter, a non-standard view engine, or any other dependency maintained by someone other than our core team. (Besides the name of the 3rd party package, it helps to include the exact version you're using. If you're unsure, check out this list of all the core packages we maintain.)

---

Please remember: never post in a public forum if you believe you've found a genuine security vulnerability. Instead, disclose it responsibly.

For help with questions about Sails, click here.

[usmanghani599]

I am also facing same issue. Any solution please?

[sreehari-nallapaneni]

Hi, As a temporary fix you can try the following.

step 1: Open your-project\assets\js\components\account-notification-banner.component.js
step 2: Replace mounted method with following

mounted: async function() {
  try{
    await Cloud.observeMySession();
    // Listen for updates to the user's session
    Cloud.on('session', (msg)=>{
      if(msg.notificationText) {
        this.notificationText = msg.notificationText;
      } else {
        this.notificationText = '';
      }
    });//œ
  }
  catch(e){
    console.log(`some error : `, e);
  }
}

Reason replacing mounted method is, in the mounted method await Cloud.observeMySession(); throws an error that is not handled, So we are handling that error with try/catch.

[rizikoblogger]

I am facing the same.

The temporary solution above works, but we keep without WebSocket capability because 'sails.sockets' is working nomore.

It looks like _csrf is not being sent into window.SAILS_LOCALS, so

I recommend you set false csrf attribute into config/security.js file - for a while.

I mean - FOR A WHILE - due to security issues around lack of CSRF control.

[mikermcneil]

@rizikoblogger @sreehari-nallapaneni @usmanghani599 @tlgtrn Patch otw (see also #7297)

[mikermcneil]

Published as v1.5.8