Electron 4/5/6 support, preferrably using N-API

sgarg · July 7, 2019, 10:02pm

If the Zoom SDK electron wrapper is updated to use the newer N-API instead of the legacy Node native addons API, then the version of Node/Electron used by Zoom to build the Electron wrapper will not have to match the version of Electron used by developers in their applications.

https://nodejs.org/api/n-api.html#n_api_n_api

Is there a near-term plan to do Zoom Electron Mac SDK release for a newer Electron version? Are you considering using N-API to eliminate this issue for future Electron releases?

carson.zoom · July 8, 2019, 6:15pm

Hi sgarg,

Thanks for using Zoom SDK and thank you for your suggestions. I will pass this info to our engineer and take it as an improvement request.

Thanks!

sgarg · July 8, 2019, 6:52pm

Thanks, please note that Zoom SDK currently only works with Electron 2.x which has been unsupported since a while now, including no security fixes. Electron team only supports last 3 versions (currently v5, v4, and v3, with v3 only getting security fixes).

https://electronjs.org/docs/tutorial/support

Using N-API will significantly simplify electron version dependency issues, but at least a recompile of current Zoom Electron SDK with a newer Electron should be done more urgently.

carson.zoom · July 17, 2019, 7:02pm

Hi sgarg,

Thanks for your reply. We have introduced a new version of Electron SDK that can work with any versions of Electron. Please have a try: https://github.com/zoom/zoom-sdk-electron

Thanks!

liubiantao · April 20, 2020, 7:01am

github.com

zoom/zoom-sdk-electron/blob/master/CHANGELOG.md

# CHANGELOG

## Note
### New SDK Initialization method: Using JWT token
Introducing new SDK initialization method -- JWT token, which is more secure, more convenient, and more versatile.

* How to compose JWT token for SDK initialization

You may generate your JWT token using the online tool https://jwt.io/. **It is highly recommended to generate your JWT token in your backend server.**

JWT is generated with three core parts: Header, Payload, and Signature. When combined, these parts are separated by a period to form a token: aaaaa.bbbbb.cccc.

Please follow this template to compose your payload for SDK initialization:

** Header
```
{
  "alg": "HS256",
  "typ": "JWT"
}

This file has been truncated. show original

But the changelog wrote only can work from 4 to 7.
Can 8 to 10 work with the new version of Electron SDK?

carson.zoom · April 21, 2020, 7:21am

Hi liubiantao,

Thanks for the reply. The current version of Electron SDK might not work with Electron 8 due to the new features introduced in Electron 8. I will forward this as a feature request to the engineering team and we will investigate the possibility of supporting it. If you need it as soon as possible, our Electron SDK is open sourced so you may configure it to support Electron 8.

Hope this helps. Thanks!

Topic		Replies	Views
Electron demo app run Electron	4	1122	August 19, 2021
Need help on getting started with the Electron SDK - How to get it to work with latest possible Electron/ Node.js versions and how to begin using it (authenticating, joining, etc.) Electron	1	1142	November 25, 2021
How to make sdk to compatible my owe electron version Electron	1	491	April 2, 2022
Can't Run Sample Electron App Electron	7	895	November 23, 2020
AuthWithJwtToken return ret 5 Electron	2	904	June 12, 2021

Electron 4/5/6 support, preferrably using N-API

Related Topics