Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

No installationId for ws_disconnect #6259

Closed
JeromeDeLeon opened this issue Dec 4, 2019 · 7 comments
Closed

No installationId for ws_disconnect #6259

JeromeDeLeon opened this issue Dec 4, 2019 · 7 comments
Labels
type:question Support or code-level question

Comments

@JeromeDeLeon
Copy link
Contributor

JeromeDeLeon commented Dec 4, 2019

Issue Description

Following the conversation from Parse Community. I decided to follow what @davimacedo said, but installationId was undefined.

Steps to reproduce

Parse.Cloud.onLiveQueryEvent(data => {
    console.log(data)
});

Expected Results

Contains installationId

Actual Outcome

installationId = undefined

Environment Setup

  • Server

    • parse-server version (Be specific! Don't say 'latest'.) : 3.9.0
    • Operating System: Ubuntu 18.04
    • Hardware: [FILL THIS OUT]
    • Localhost or remote server? (AWS, Heroku, Azure, Digital Ocean, etc): localhost
  • Database

    • MongoDB version: 4.2.1
    • Storage engine: default
    • Hardware: [FILL THIS OUT]
    • Localhost or remote server? (AWS, mLab, ObjectRocket, Digital Ocean, etc): localhost

Logs/Trace

// ws connect
{ event: 'ws_connect', clients: 0, subscriptions: 0 }

// connect
{
  client: Client {
    id: '545db257-c317-4cc3-8526-7ed6c6ae7aa8',
    parseWebSocket: ParseWebSocket {
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      ws: [WebSocket],
      clientId: '545db257-c317-4cc3-8526-7ed6c6ae7aa8'
    },
    hasMasterKey: false,
    sessionToken: 'r:fae9e151b5a0a3693a198b7fcd368f8a',
    roles: [],
    subscriptionInfos: Map {},
    pushConnect: [Function],
    pushSubscribe: [Function],
    pushUnsubscribe: [Function],
    pushCreate: [Function],
    pushEnter: [Function],
    pushUpdate: [Function],
    pushDelete: [Function],
    pushLeave: [Function]
  },
  event: 'connect',
  clients: 1,
  subscriptions: 0,
  sessionToken: 'r:fae9e151b5a0a3693a198b7fcd368f8a',
  useMasterKey: false,
  installationId: undefined
}

// subscribe
{
  client: Client {
    id: '545db257-c317-4cc3-8526-7ed6c6ae7aa8',
    parseWebSocket: ParseWebSocket {
      _events: [Object: null prototype],
      _eventsCount: 2,
      _maxListeners: undefined,
      ws: [WebSocket],
      clientId: '545db257-c317-4cc3-8526-7ed6c6ae7aa8'
    },
    hasMasterKey: false,
    sessionToken: 'r:fae9e151b5a0a3693a198b7fcd368f8a',
    roles: [],
    subscriptionInfos: Map { 1 => [Object] },
    pushConnect: [Function],
    pushSubscribe: [Function],
    pushUnsubscribe: [Function],
    pushCreate: [Function],
    pushEnter: [Function],
    pushUpdate: [Function],
    pushDelete: [Function],
    pushLeave: [Function]
  },
  event: 'subscribe',
  clients: 1,
  subscriptions: 1,
  sessionToken: 'r:fae9e151b5a0a3693a198b7fcd368f8a',
  useMasterKey: false,
  installationId: undefined
}

// disconnect
{ event: 'ws_disconnect', clients: 0, subscriptions: 0 }
@davimacedo
Copy link
Member

Can you please try to test against master? The installationId fix was not yet released.

@JeromeDeLeon
Copy link
Contributor Author

I haven't tried doing that nor have any idea on how to test the master branch sorry. If it was implemented then I'll just wait for it to release then.

@JeromeDeLeon
Copy link
Contributor Author

Can you reference the merge fix?

@davimacedo
Copy link
Member

I think this one should solve the issue: #6180

@JeromeDeLeon
Copy link
Contributor Author

JeromeDeLeon commented Dec 4, 2019

Do you have plan of when this will be release?

@dplewis
Copy link
Member

dplewis commented Dec 4, 2019

@JeromeDeLeon This is the fix here

If you want to try out the master branch

https://github.com/parse-community/parse-server#want-to-ride-the-bleeding-edge

We should do a release soon, probably this weekend.

@JeromeDeLeon
Copy link
Contributor Author

Thanks to both of you 😃

@mtrezza mtrezza added type:question Support or code-level question and removed 🔧 troubleshooting labels Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:question Support or code-level question
Projects
None yet
Development

No branches or pull requests

4 participants