Hello,

Mi system is:

Ubuntu 14.04
Graphical Environement is Unity
Firefox 44.0
jidesha 0.1.1

When I share screen with any program, not scale correctly and the other users see it wrong.
For example, if I share screen with libreoffice calc, the column "A" and part of "B" is not seen for the rest of users that is connected.
The problem also persists if I change the window size of that program or any other shared program. The scale is not correct.
This problem existed in previous versions of firefox, and this is tested from firefox user to firefox user.

Best regards

I compiled the chrome/chromium long time ago (before it had the thing for the calendar). And I think the screen capture is not working. Should I compile-update again the new extension? In case I should update the extension what is the criteria to update the extension, I see 0 releases, how can I know when is the good moment?

Thank you!

Hello,
According to https://developer.mozilla.org/en-US/Marketplace/Add-on_submission#Add-on_detail_page, the current file organization in Jidesha prevents add-on publication on Mozilla Marketplace.
Workaround is
copy chrome/manifest.json to /firefox/manifest.json
edit manifest.json with your own values into mandatory fields as per https://wiki.mozilla.org/Marketplace/Add-ons/Validation
encode manifest.json into UTF-8
copy chrome/*.png into firefox/
zip all files in firefox/ apart of make.sh and README.md

Thanks you to correct and big thanks for the whole software suite of jitsi-meet. It's amazing!

Hello,

I've used the instructions to create a private extension, added it to the chrome store, configured jitsi-meet to use the extension's ID but it keeps failing to download the extension from the Chrome Store and all it does is spit a "Permissions denied" popup.

Extension's page: https://chrome.google.com/webstore/detail/ojddellhmdkbkejiklmlaemehnbkfigb/publish-accepted?hl=en-US&gl=US

Error generated inside the console:
app.bundle.min.js:2 [react/features/base/tracks/functions.js] <>: Failed to create local tracks ["desktop"] r {name: "gum.chrome_extension_installation_error", message: "Failed to install the extension from https://chrom…/webstore/detail/ojddellhmdkbkejiklmlaemehnbkfigb", stack: "Error↵ at new r (https://app.boardhub.io/libs/l…er.onInstallResponse (extensions::webstore:72:22)"}

Any help would be much appreciated.

Thanks.

Desktop Sharing works the first time.
Then, use this functionality again, must restart chrome
Thanks for development

Here is what I did:

1. Revised the manifest.json, with

 "update_url": "https://meeting.jototech.cn/updates.xml",
  "externally_connectable": {
      "matches": [
          "*://meeting.jototech.cn/*"

2. Get the Exension ID: edhfhepkbohecicbjcgnceljemjhiglm

3. Revise the update.xml and upload, please check: https://meeting.jototech.cn/update.xml

<xml version='1.0' encoding='UTF-8'?>`<gupdate xmlns='http://www.google.com/update2/response' protocol='2.0'>
  <app appid='edhfhepkbohecicbjcgnceljemjhiglm'>
    <updatecheck codebase='https://meeting.jototech.cn/chrome.crx' version='2.0' />
  </app>
</gupdate>

4. Successfully drag and drop the extension:

5. Revise the configuration of /etc/jitsi/meet/joto-config.js, as following:

    desktopSharingChromeExtId: 'edhfhepkbohecicbjcgnceljemjhiglm',
   desktopSharingChromeDisabled: false,

6. Open link: https://meeting.jototech.cn/joto, but no screen sharing button

Any thing I did wrong???

Thank you for all of your work, and I want to know if I have two servers [ A.mydomain.com ] [ B.mydomain.com ],if I want 2 servers share the same extension, can I use below settings?
"externally_connectable": { "matches": [ "*://*.mydomain.com/*" ] },

I have published extension for "*://A.mydomain.com/*", But after I changed to "*://*.mydomain.com/*" , and update the extension with Hash ID no change , I got "oops! your screen sharing extension failed to install ."
But I can install the updated extension from google webstore , and it works well with screen sharing!

Hi,

I'm not sure how else to describe this other than the subject.

Both Jitsi Meet and the extension work just fine in Chrome when sharing either an Application Window or Chrome Tab. However, when testing sharing the full desktop, it's sort of like mirrors facing one another... the sharing is shared, which is shared, which is shared..

See attached screenshot:

This is Chrome 55 on macOS 10.11 (El Capitan). This is with only the host connected. My assumption is that with another person in the conference and them given focus, this may not happen. Still to be tested, it's a new set up.

Also, not checked on FF yet.

When sharing from firefox with last jidesha extension, the image is very pixelated (and test is unreadable) — a bit alike what skype does when sharing screen on linux.

We tried with the same user on the same condition under chrome, and everything went smoothly (i.e, a bit pixelated, but getting better in one second on static images).

Any idea on what may cause the problem and how to solve it ?

Finally, I got your plugin working and I must tell you that I really appreciate your work as part of an open source project. Now, after testing both, the Firefox and the Chrome plugin, I would like to ask you some questions:

1. Why is there no option to define the URL of the Chrome extension file on the Jitsi Meet server? When using Firefox I can set a link to my XPI file, but with Chrome's CRX I can not. Even if the CRX would have been installed instantly after downloading it, it should be possible to inform the user to right click and save it to a certain location of the current PC.
2. In Chrome you are able to share the whole screen, but with the Firefox Addon only Windows can be streamed to the other person. Is this due to the Firefox API or could you also implement a feature to share the whole screen with the Firefox Plugin?

Thank you so much for your work
I'm looking forward to your reply

I cloned the repo, changed the externally connectable URL, created an extension and pasted the extension ID on my config.js file.

But when some of my users try to use the extension the get a message saying "Permission Denied, failed to install extension".

This is happening on Windows 10 with Google Chrome 59.0.3071.115.

I am hosting rocket.chat on my own server but not Jitsi, and rocket.chat is using Jitsi for the video chat.
So in my case, if I am using Jitsi's server for the video chat through rocket.chat, do i still need to install Jidesha in order for my users to use screen share ? I do get the error message: failed to install desktop extension.

If so, is there a tutorial or instruction in terms of how to get Jidesha up running? there is nothing in Github.

When creating an Event in Google Calendar there is a known bug where it doesn't work / works only erratically. Fundamentally this problem is caused by trying to interact with the Calendar page with JS instead of using the native Template system. I propose moving to the native URL var based Template instead to fix this (I have it working in a private fork). Would you be open to a Pull Request for this?

Implications / how I have it working currently:

• create a new config.js to store the constants used in the JS and share across popup.js and meet-calendar.js
• in popup.html load config.js, RandomUtil.js and RoomnameGenerator.js
• in popup.html use (e.g.) https://www.google.com/calendar/render?action=TEMPLATE&autoCreateMeeting=true&details={MEET_DESCRIPTION}&location={MEET_LOCATION}&dates={DATETIME}%2F{DATETIME} as the URL
• in popup.js build vars and replace placeholders
  Unfortunately since I don't think Outlook has an equivalent we still need the extid system, but only for OWA. So either popup.js switches depending on URL or '&extid=' + chrome.runtime.id get's injected in popup.html instead.

Hi,
I cloned the repository, modified the chrome/manifest.json file then packed and installed the extension in Chrome.
After that i modified /etc/jitsi/meet/my.domain-config.js and added the
desktopSharingChromeExtId: 'myextensionid',
line and restarted everything with
systemctl restart jicofo && systemctl restart jitsi-videobridge && systemctl restart prosody && systemctl restart nginx
I started Chrome, connected to my domain, reloaded the page with ctrl+f5 (tried also ctrl-r, ctrl-shift-r).
I tried setting
desktopSharing: 'webrtc'
and
desktopSharing: 'ext'
But both give the same results:
When i click on the "Share Desktop" icon, i get the "Failed to install desktop extension" message.
What is the issue?

I tried this on Google Chrome 49.0.2623.87-1 (the "stable" package), on Debian Testing 64 bit.

Tutorial for doing an inline install with the Chrome extension via the Chrome webstore.
This is different to the manual install in which your users use the crx file to set the extension. This inline install is preferable because you do not need to provide a user with the extension. When they click the "Screen Share" icon in the conference interface, it will automatically install the extension (inline install).

1. Go to https://github.com/jitsi/jidesha and download the files.

2. Your download will be a zip file, unzip: "jidesha-master"

3. Open the calendar folder and edit the manifest.json file

4. The lines you need to edit include:
   "name", "description", "icons (your png icons 16x16, 48x48 and 128,128), "web_accessible_resources" and

    "externally_connectable": {
          "matches": [
            "*://yourdomain.com/*"
          ]
      },
   

Updated on advice from damencho:

5. Remember to replace the png files with your png files AND name them as you have them in your mainfest.json file.
6. Now run the make.sh file (just click it)
7. It will create a new folder "target", inside this another folder "content"
8. The content folder now has all your edits and is ready for the to be added to the Chrome Extension via the Chrome Webstore.
9. Zip the "contents" folder.

• Now we set up the Chrome Webstore to distribute our extension

10. Now go to the developer dashboard for Chrome.
    https://chrome.google.com/webstore/developer/dashboard

11. Create your developer account. If you don't have a developer account its a one-time fee of $5.00
    Your manifest will automatically populate the info into the Extension page eg, "name", "version", "description", "pngs" etc. but you also do edits as well right there in the panel.

12. Lower on the developer dashboard page for your extension, is the "websites" drop down list. This is a list of all the sites you have verified thus far with your Google account. IF you don't see the domain that you want to have your Jitsi-Meet at, on that list then you have to add this site and verify it.

• We continue as if you did not have this site added and verified.

13. At the "websites" drop down list there is below this - "add new site".
    You will then be taken to a Google process for you to add a website as verified. This involves you uploading a file to your domain and then clicking the link.

14. Once your website has been verified it will then show on your developer dashboard page in the websites drop down list. IF its not there, just refresh the page. If you see it on the list, select it.

15. Lower down the page is "Inline Install" and a checkbox for it. Select the checkbox.
    This is the "allow process" so that when users click the Screen Share icon in Chrome, it will automatically install the extension (after they give it permission to install).

• Almost done.

16. Follow the addition process for your Chrome extension to the end and you will then see the publishing is in progress. You have to wait a bit for this, don't rush it, its doing its thing.

17. After it shows as "Published" on your dashboard, click the "more info" link attached to your extension on your developer dashboard. You will then have the Item ID for your extension.

Copy this ID. We need this ID so that the Screen Sharing icon in your conference will direct to this extension in the webstore. If you don't have this ID, how can it get the extension?

18. Now on your server files for your Jitsi-Meet go to and edit:
    /etc/jitsi/meet/www.mydomain.com-config.js

19. Look for the following on this file:

    // The ID of the jidesha extension for Chrome.
    desktopSharingChromeExtId: 'Item ID',
    
    // Whether desktop sharing should be disabled on Chrome.
    desktopSharingChromeDisabled: false,
    

Enter you Item ID into - desktopSharingChromeExtId: 'Item ID',
BE SURE TO ENTER THE ID INSIDE THE ''

These are the only 2 lines in this file which need to be edited.
Save the file and then go to your Jitsi-Meet site.
Your Chrome browser users will be able to install the extension from inside the conference without doing it manually (drag and drop) or having to go to the webstore.

When clicking the "Create Outlook 365 Calendar" it doesn't work and is redirected to the Microsoft Live site. It seems the URL in the extension provided doesn't work any longer.

I already create and install my extension on chrome. But when I looked at the installed chrome extension, there's no information about the id, how do I know my Id to put into jitsi meet? I use the latest chrome btw Version 58.0.3029.110 (64-bit) windows.
Thank you

I do as for the Chrome, but it does not work. (No button to share the screen)
Can I somehow teach him how to work in Opera?
PS : In Chrome and Firefox, everything works fine.

I tried to upload the extension on mozilla addon store and I've got the following message:

Starting with Firefox 53, new extensions on this site can only be WebExtensions.

Best regards,

YC

Hi
I installed the jitsi server on an ubuntu and it works fine , screeen sharing is working on firefox with the same site.

I tried to compile the calendar crx extension with my site and it does not work for me.

Instead the original extension jitsi meetings works fine with the https://meet.jit.si/ site.

so I guess it is an error in configuration of my server.

when I add the generated ID to the server :

// The ID of the jidesha extension for Chrome.
desktopSharingChromeExtId: omikhipjhdfmdnemgfifenclnmaphebc,
// Whether desktop sharing should be disabled on Chrome.
desktopSharingChromeDisabled: false,
// The media sources to use when using screen sharing with the Chrome
// extension.
desktopSharingChromeSources: ['screen', 'window', 'tab'],
// Required version of Chrome extension
desktopSharingChromeMinExtVersion: '0.1',

and I restart the jicofo service, I got a blank screen
What I'm missing ?

Thank you
Paolo

If I understood correctly the current inline installation process that Jidesha uses will be deprecated by September 2018.

https://blog.chromium.org/2018/06/improving-extension-transparency-for.html

Would this be a blocking issue for Jidesha?

Hey everybody,

I am having a problem about desktop sharing on my server. When I use firefox add-on, I can't share screen and can't see shared screens (other users have same problem too.). I create my own add-on from this repo but firefox saying this add-on is not secure and wont install it. I disabled signature dependincy at about:config. Now, is there any other way to create my add-on? Should I change my servers jitsi config file (if answer is yes, what should I do on my server?)? Or can u upgrade https://addons.mozilla.org/en-US/firefox/addon/jidesha1/?src=userprofile#id=666492 for people can use their own ID and EXT_ID for their servers? Thanks :)

nextcloud's calendar is widely used. It would be great if also an open source calendar would get some auto fill in capabilities for Jitsi meetings as the place to meet.

Alternatively, the feature may be integrated into the nextcloud calendar app nextcloud/calendar#3480 (comment)

When i add crx file to Chrome i get error: "This extension may have been corrupted".
In Chrome ver 62 no error

I dont see anything at description area on google calendar

I successfully installed jidesha for desktop sharing and scheduling a jitsi event using google calendar.
Desktop sharing is working fine but sometimes the event in the google calendar does not have the "location" information. It is not very consistent; sometimes the event does have the location, but not always.

Did anyone experience this? Is it a known bug?

-Minkyu

Hi Guys,

I'm just curious is this jidesha 0.1.6 differs from 0.2.6.9 which you have on chrome web store ?
I just want to make sure I'm using the most recent version.

Thanks !
David

Description

I have a very small request to update the text that is automatically inserted by the Jitsi Meetings Chrome extension to reflect the current dial-in numbers.

As we’re located in Canada, having the Canadian number available is useful, however it doesn’t appear in the extension text when creating a calendar invite.

Current behavior

Dial-in numbers inserted by the Chrome extension are not the most recent

Expected Behavior

Chrome extension will insert the most recent dial-in numbers

Possible Solution

Update the numbers

Steps to reproduce

Create a calendar invite with the Jitsi Meetings Google Chrome extension

Environment details

Windows 10 Pro 1909
Chrome Version 81.0.4044.129 (Official Build) (64-bit)
Jitsi Meetings extension Version 0.2.8.14

I can see here: https://meet.jit.si/config.js that there is not extension id for firefox?

Does it mean that firefox doesn't need extension anymore? Thanks for clarifying the doubts.

This addon is not compatible with the new electrolysis multiprocess framework for firefox. Here's a screenshot from the add-ons menu. Sorry I have no further information about this.

Hi
I Just wanted to ask if there's a demand to pull in one jidesha plugin in the
firefox addon store and chrome addon web store, where you can manually point to
your own jitsi-meet installation instead of building your own plugin to do this.

E.g.: Add a configurable input field exposed in the browser plugin settings.

This way, you need only one build for everyone.

I like to use the same room for all my meetings. Is it possible to add an option to use a specific room with the chrome calendar extension rather than a random one?

Sometimes, screen sharing shows unlimited nesting/loopings when sharing entire screen. any idea to fix this. thanks a lot

Hello,
I've explicitly followed all the steps on customizing my chrome plugin.
After I clear the cache and try to use my customized plugin, it still points to jitsi.net.
Am I missing something or is the current release not working?

Thanks!

Any step by step docs to get this going?

Hi,
I deploy my chrome extension based on jidesha, I set externally_connectable in manifest.json with my domain and I'v got this

the extension can't be downloaded and get this message in console
Failed to obtain the stream to switch to NavigatorUserMediaError {constraintName: "", message: "", name: "InvalidStateError"}

my virtual host is not https

thanks

OS: Fedora 26
Chrome: Version 61.0.3163.100 (Official Build) (64-bit)
Jidesha: Jitsi Meetings - 0.2.6.12
Graphics: NVIDIA proprietary - 384.90

Problem: Almost all application windows display as black when attempting to screen share. Some show partial content, but never all. The mouse is always captured when hovering over the window that is meant to be captured (so video is working, etc)

I believe this to be a regression in either the browser's abilities, Jidesha itself, or the nvidia driver I'm using. I am 100% certain that I've used this in the past few months when it worked completely fine, I just can't give an exact timeframe.

I'll attempt to do some more troubleshooting and leave what information I find here.