connection timeout about rpc HOT 10 CLOSED

having the same issue

https://maxie.is-serious.business/47b296.png

const DiscordRPC = require('discord-rpc');
const ClientId = '388095943624359946';
DiscordRPC.register(ClientId);

const rpc = new DiscordRPC.Client({ transport: 'ipc' });

async function setActivity() {
  if (!rpc || !mainWindow) 
    return;

    rpc.setActivity({
      details: `Rich Presence for the UnderCards Client`,
      state: 'Searching',
      startTimestamp,
      largeImageKey: 'cards_logo',
      largeImageText: 'UnderCards',
      smallImageKey: 'maxie',
      smallImageText: 'Beta Testing stuff',
      instance: false,
    });
  }
  
  rpc.on('ready', () => {
    setActivity();
  
    // activity can only be set every 15 seconds
    setInterval(() => {
      setActivity();
    }, 15e3);
  });

  
rpc.login(ClientId).catch(console.error);

from rpc.

it looks like this issue actually comes from windows named pipes and elevated permissions, technically an implementation bug on discord's side, i'll close this

from rpc.

So there's no fix @devsnek ? :(

from rpc.

@mew351 make your app match the elevation of the discord process

from rpc.

We experienced this too, live on a convention floor showing our game. It happened all day on Windows on day 1 and appeared to start happening on day 2 on linux as well.

I'm going to be looking into it more this week but it appears to stretch beyond just Windows (but it definitely shows up almost 100% of the time in Windows).

We had to remove discord integration entirely for the time being, which is a major bummer! Hopefully I can come up with a better solution and report back.

from rpc.

@framerate please keep me informed, and make sure you're on the latest version (and also whats your game 😄)

from rpc.

@devsnek http://doomtroopergame.com :)

I'll definitely keep you updated if I find anything. My game is 100% javascript so this is a key library for me here :)

from rpc.

For me, I was getting my problem until I removed a date from my code:

client.setActivity({ largeImageKey: 'logo', largeImageText: 'large image text', details: 'subscribe and like', state: 'or i die', startTimestamp: new Date(), buttons: [ { label: 'Hello!', url: 'https://github.com/thedigs', }, ], });

I removed the startTimestamp: new Date(), and the problem disappeared!

from rpc.

DIGS Answer Solved for me.

For me, I was getting my problem until I removed a date from my code:

client.setActivity({ largeImageKey: 'logo', largeImageText: 'large image text', details: 'subscribe and like', state: 'or i die', startTimestamp: new Date(), buttons: [ { label: 'Hello!', url: 'https://github.com/thedigs', }, ], });

I removed the startTimestamp: new Date(), and the problem disappeared!

from rpc.

same problem, I can't try TheDIGS solution cause I haven't startTimestamp in my code

from rpc.