Jonathan Rainville

@jeluard I'm setting up my phone to use debug logs, but in the meantime, here's the answer for your question. > which provider do you use? You should hook with...

Just tried debugging and there is sadly nothing in the logs.

> Is the Set action supposed to create a transaction? Oops, just tested again, and while it worked when I tested last time, I might have overwritten the working version....

Ok, I just "fixed" the Dapp. Basically, the event handler was giving an error in Status that I didn't handle. The error is: ``` Error: The current provider doesn't support...

Possible. It is not the case in my example though, since, as you can see here https://github.com/jrainville/events-test/blob/master/app/js/index.js#L16, I only call the event registration once `EmbarkJS.onReady` is done on line 5....

That's my understanding of the problem yes. The Status-React providers are completely custom so they probably need WS support just like Web3js' Websocket provider (https://github.com/ethereum/web3.js/blob/2.x/packages/web3-providers/src/providers/WebsocketProvider.js) One way to do it...

Thanks for the reviews and test. Sadly for you, you'll have to do it again. I improved this PR significantly. I added the `mode` build param. That means that we...

I agree that `Mode` is a bad name. So, I think the consensus for now is to just rename the params to something better like suggested and then, if needed,...

Update done

@flexsurfer with the latest build, it should default to the status Gateway if none is provided thanks to this line https://github.com/status-im/status-go/pull/2795/files#diff-76ed074a9305c04054cdebb9e9aad2d818052b07091de1f20cad0bbac34ffb52R10 I'm not sure why it didn't work for you....