sunny-lau / dirty-room Goto Github PK

if user did not enable notification or user turned-off spaces user pref for notification. we the utilize the socket-event

• This issue is executed by a bot.
• Bot expects to click this button within 4 seconds and in some cases not able to - that is the failure reported.
• Selenium Headless Chrome
• Issue experienced in multi-region. Appeared twice today. Saturday/Sunday a couple of times as well.

One of the spaces impacted https://spaces.zang.io/spaces/5ed507939c9b2ab0c054fbc3
Time: 17:58 IST July 6th - 8:28 a.m EST.

What is the config or machine type of the VM -
n1-standard-4 (4 vCPUs, 15 GB memory)

"Based on my logs checking and my testing. I found some static files delay is very long. For example the failure testing you claimed at 11:40 this morning, I found a request to fontawesome-webfont.af7ae505.woff2 take near 4 second. And I got another delay to another static file take more than 5 seconds. But I never get very long delay on rest api."

┆Attachments: font-awesome.min.css | font-awesome-4.7.0.zip

• data: DEFINITION UNCLEAR is it substitute for 'video.screensharedata' response, should return an array of objects with screenshare frames? Always returns an empty array

• userA has space enabled

• userB also has space enabled

• userA is in a video call and calls DM of userB

• userA 'hangs up' the call to DM userB

• userA is shown as removed from their initial ongoing call and is still shown 'are you sure you want to leave this conference'

https://drive.google.com/file/d/1M4mv4R1Qy8XxN5_k9feRoxJ4a0PpXkBK/view

┆Attachments: loganstaging.esna.com-1596560220674.log

• sender.type:DEFINITION UNCLEAR - always returns 'spaceserver' which is set as a constant (TypeSpaceServer) in backend's 'meeting history' api

Problem description (be as specific as possible), include step by step procedure used to reproduce the issue:
User sends some chat and attaches some files, user send more chat and now the scroll bar can go down to the bottom and disappears. User's unable to scroll down to bottom and unable to see new chat messages.

Notes:
- This issue also happens with quick chat

• This issue happens with : chrome, firefox, safari, edge
• This issue does not happens on system: spaces.avayacloud.com
  - Refresh page does not fix the issue

Setup:
UserA - Any user

Steps:

1. UserA sends some messages
2. UserA shares some files
3. UserA sends some more messages

Expected :
All messages are fully displayed. UserA can scroll down to bottom to see new messages

Actual:
Scrolling bar disappear at the bottom. User is not able to scroll down to see latest messages

Workaround: N/A

SV comment for blocking status: yes

Is the issue reproducible: 100%

┆Attachments: loganstaging2.esna.com-1594887508553.log | Screenshot_3.png | Video_2020-07-16_151810.mp4 | loganstaging2.esna.com-1594897619628.log | Screenshot_1.png | Video_2020-07-16_180629.mp4 | image.png | loganstaging.esna.com-1594950703583.log | Screenshot_2.png | Video_2020-07-17_085123.mp4 | loganstaging.esna.com-1594978784768.log | Screenshot_1.png | Video_2020-07-17_163857.mp4 | Screenshot_1.png | Screenshot_2.png | spaces-candidate.avayacloud.com-1595403937413.log | Video_2020-07-22_144510.mp4 | Screenshot_1.png | Screenshot_2.png | spaces-candidate.avayacloud.com-1595823014485.log | Video_2020-07-27_110955.mp4

for electron app:
call :

window.electron.send(
window.electron.constants.APP_MESSAGE_TYPE.RESTORE_APP
);

for browser:
call window.focus();

• this recording file took a very long time to try to generate

• after 10 minutes it stops and displays as shown in the image

• happened couple times

┆Attachments: image.png | loganstaging.esna.com-1597951889578.log

Setup:
UserA - Tho Pham - admin of space https://loganstaging-candidate.esna.com/spaces/5ef486cd430c396df69ce93e
UserB - Test04 - Registered guest

Steps:

1. UserA, userB is in same space
2. UserA starts meeting. While userA connecting to meeting, userB clicks Leave on top to leave space
3. UserA hangs up call
   4. UserB relaunch space --> UserB see userA in roster list but userA does not see userB in roster list. UserA, userB can chat to each other

Workaround: N/A

SV comment for blocking status: This is a not blocked issue

Is the issue reproducible: 100%

┆Attachments: UserA-Tho Pham-Admin-.png | UserB-Test04-Registered guest-.png | UserA-Tho Pham-Admin-loganstaging-candidate.esna.com-1593084019090.log | UserB-Test04-Registered guest-loganstaging-candidate.esna.com-1593084073655.log | UserA-Tho Pham-Admin-Video_2020-06-25_181918.mp4 | UserB-Test04-Registered guest-Video_2020-06-25_181925.mp4

2020-08-18T18:11:56.787Z - error: [socket-server/backend][SEND_PRESENCE_EVENT] ReferenceError: src is not defined "ReferenceError: src is not defined\n at /app/src/socket-server/socket.backend.js:838:42\n at getSocketUserInfo (/app/src/socket-server/socket.backend.js:49:3)\n at _callee5$ (/app/src/socket-server/socket.backend.js:829:5)\n at tryCatch (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:62:40)\n at Generator.invoke [as _invoke] (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:296:22)\n at Generator.prototype.(anonymous function) [as next] (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:114:21)\n at step (/app/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)\n at /app/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14\n at new Promise ()\n at new F (/app/node_modules/core-js/library/modules/_export.js:36:28)\n at /app/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12\n at onSocketSendPresenceEvent (/app/build/server.js:44406:18)\n at Namespace._callee4$ (/app/src/socket-server/index.js:212:13)\n at tryCatch (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:62:40)\n at Generator.invoke [as _invoke] (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:296:22)\n at Generator.prototype.(anonymous function) [as next] (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:114:21)\n at step (/app/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30)\n at /app/node_modules/babel-runtime/helpers/asyncToGenerator.js:35:14\n at new Promise ()\n at new F (/app/node_modules/core-js/library/modules/_export.js:36:28)\n at Socket. (/app/node_modules/babel-runtime/helpers/asyncToGenerator.js:14:12)\n at Socket. (/app/src/socket-server/index.js:211:5)" {"socketid":"/chat#_47sWiOx27o9NLNsJgcL","sessionId":"400d4a10-8d33-477d-b91e-c5d62502c523","connector":"58d29da13b3132a1e27bf4aa","connector_email":"[email protected]","connector_displayname":"Mehmet Balasaygun","connector_picture_url":"https://accounts.zang.io/norevimages/noimage.jpg","connectorType":"user","transportType":"websocket","expires":1597843871000,"connector_permissions":

Method's likely deprecated. It did not show up in 'webSockets messages' of developer tools, when another user joined a room protected with password. It's either deprecated or substituted by CHANNEL_SUBSCRIBED payload?

It does not emit when a user joins my room. It is also not used in backend, e.g. in method onCodePaired() at app.socket.js:11

If the user clicks a link to a Space (for instance in an email or in an appointment), or pastes a link in a browser tab:

• if the user never downloaded and used desktop app before: (P)

  • navigation continues in the browser (P)

• If he installed desktop app and logged in at least once, he should be redirected to a landing page with the following options:

  • Continue in browser (P)

  • Open Desktop application (P)

  • If the user selects “Continue in this browser”

    • user is redirected to the space associated with the link (P)

  • if the user selects “Open Desktop application”

    • The browser pops-up the window asking the user to open desktop app (P)

  • an option is presented to offer the possibility of remembering the option selected

    • If the option is set to true, the landing page is not shown again. (P)

• In the user menu, an option called “Join space with:” with options "Ask", "Browser" and "Desktop app" will be shown

  • If "Ask" is selected, the user is always redirected to the landing page (P)
  • if "Browser" option is selected, user will always be redirected to the space. (P)
  • if "Desktop app" option is selected, user will always be redirected to the application. (P)

Use this Electron App builds to test that deep links are working as expected on staging:

• macOS: https://drive.google.com/file/d/1NSkExmodGrqy-vBECib0IQDIFELHkwBG/view?usp=sharing
• Windows: https://drive.google.com/file/d/14eI3QoAdCL9i71TORfBcdQWpp8Ky9T6U/view?usp=sharing

• Making it blocking because Reproduced 4 times by @Vincent Yeung - asking other QC members to try it as well

• one guest was sent invitation by email, another was sent a link to that room

• guest joins and admin is not in the call

• after 1-2 minutes, the guest suddenly is kicked out of call but still shows that call is ongoing (from meeting card)

┆Attachments: loganstaging.esna.com-1597946749719.log

The issue can be found with anyone who wants to join a Spaces meeting via ‘Join by phone’ option from Android native Calendar app.

The below is how the issue can be reproduced.
a. People in Avaya invites a participant to Space meeting via outlook add-in(Avaya Meeting Scheduler Add-in)

b. The Participant opens the invitation ﹍from Calendar app on Android device﹍ and tries to join a Space meeting via ‘Join by Phone’ option.
c. There are 2 links for each dial-in number, one with just dial-in number and the other with dial-in number + Space ID.
d. The participant wants to use the link with dial-in number + Space ID but the second link does not work because ‘ ’ is added between country code and local code.

According to the user report, Equinox Conferencing had the same issue but it was resolved.

IT service team suggested to use Outlook on the phone to get to the meeting invites. But it was not accepted.

﹍Can we have removed from the link?﹍

┆Attachments: Step 2.jpg | step 3.jpg | Step_1.jpg

User has to try multiple times to get his login acknowledged by Spaces when he joins his Spaces. User only gets the recording that the meeting ID is invalid.

When the user clicks on a Spaces link:

• If the user is already logged in, and it is configured to be able to download Desktop app, the following landing page should be shown.

• If the user is not logged in or it is not configured to download Desktop app , navigation continues in the browser

For Supported Browsers
A landing page is shown when a user is logged in, is an active user of the Electron App and opens a link to a space or invite to join/meet.
For the user to be considered an active user of the Electron App should have it installed and use it in the last 2 weeks. The user's last activity timestamp on Electron App is being updated every 30 min. This is managed as a setting so this depends on backend (esna/Logan#840).
The landing page will prompt the user to open the link on the Desktop App or continue in browser, with an option to remember the decision made.
If the user don't choose to remember his decision, the next time that he opens a link to a space/invite the landing page will be shown again
If the user choose to remember his decision (decision stored on a cookie called preferDesktop) and also choose to:

• continue in browser, the landing page will not be shown again
• open the Desktop App, next time the landing page will be shown but will also automatically prompt to open the App

The preferred behaviour for the landing page could be changed from the User Preferences page were the user can choose within:

• Ask every time
• Web browser (same as if user choose to remember that he wants to continue in browser)
• Desktop app (same as if user choose to remember that he wants to open the Desktop App)

The preference applies to the user's current browser since it is being stored on a cookie and so we also consider some use cases like users with different PCs that for many reasons on one have the Electron App installed and on others not.
For the not active users of the Electron App or Guests, the flow remains the same as it currently is.
For not-supported Browsers
For the case of browsers that doesn't support webRTC (like Safari) a landing page will be shown for those users that are enrolled to the Electron App no matter what path they are trying to reach.
The landing page offers the users to download the app for the current platform (macOS or PC) or suggests to use spaces on one of the supported browsers -Chrome (Recommended), Firefox, Edge (Chromium)-.
If the app is already installed by the user then the landing page will automatically prompt to open the Desktop App.
If the app is not installed and the user downloads it from the landing page and installs it then he has an option to launch the app.
For the users not enrolled on Electron App or Guests, the flow remains the same as it currently is.
There are no changes for IE.

Use this Electron App builds to test that deep links are working as expected on staging:

• macOS: https://drive.google.com/file/d/1NSkExmodGrqy-vBECib0IQDIFELHkwBG/view?usp=sharing
• Windows: https://drive.google.com/file/d/14eI3QoAdCL9i71TORfBcdQWpp8Ky9T6U/view?usp=sharing

┆Attachments: image.png

• User A doesn't have DM space with user b on the sidebar topic list (you can hide the DM with user B, if it's existing)
• User B call User A
• User B should be able to see incoming call dialog and call should be established correctly after accept it.

User is changing the language to 'Czech' from English and it is not correctly showing on the Avaya Space dashboard or anywhere. I have attached a screenshot regarding the same. @

┆Attachments: Language_Error.jpg | Screen Shot 2020-08-24 at 2.10.26 PM.png

Description: The created space should be launched automatically when client creates that space

Setup:
Client: [email protected]
System: https://logantesting2.esna.com/spaces/dashboard

Steps:

1. Client creates a space

Expected:

1. The created space should be opened automatically

Actual:

1. The space isn't opened

Reproducible: 100%

Workaround: client must open space manually

┆Attachments: Video_2020-08-17_113126.wmv | Console.log | Network.har | Console.log | Network.har | Network.har | Console.log | Video_2020-08-25_094530.wmv

• User enrolled on Electron App Download feature
• On Safari open a URL to an space
• Expected Result: deep link landing page is shown
• Actual Result: shows a page saying that there was an error opening the space

Use this Electron App builds to test that deep links are working as expected on staging:

• macOS: https://drive.google.com/file/d/1NSkExmodGrqy-vBECib0IQDIFELHkwBG/view?usp=sharing
• Windows: https://drive.google.com/file/d/14eI3QoAdCL9i71TORfBcdQWpp8Ky9T6U/view?usp=sharing

┆Attachments: Safari landing page.mov | Screen Shot 2020-08-27 at 19.47.59.png | Console.txt

• need to also test this with a space with many messages with uploaded messages
• also test with newly sent messages with pdf/images attached the scroll should go to bottom.

Description for test:

• Receive multiple messages in chat
• You will see that new messages are arrived, but scroll to bottom happened only after more than 400ms

┆Attachments: meeting card.PNG | new message scroll.mp4 | attachment scroll.mp4

All the users left the meeting and call ended but meeting card still shows as "Live Meeting Active".

Note: this happens in all kind of spaces: "My Meeting Room", "Normal Space" and "DMs"

┆Attachments: image.png | image.png | loganstaging.esna.com-1597954104754.log | image.png | loganstaging.esna.com-1597954213234.log

nothing changed in terms of feature we just need to retest space-calling

This issue only happened once.

category:
app.event.channel.subscription.required Message content: ["MESSAGE_SENT",{"topicId":"5f088f453cb00fbe3e70abb9","sender":{"_id":"5e9f84e14aa9b9e0b3d9b3e7","username":"[email protected]","displayname":"Doug Brown","type":"user"},"category":"app.event.channel.subscription.required","loopbackMetadata":"cdc8b8c0-f85e-49e3-a8d5-c3e4da0ec282"}]

user is Doug Brown, issue happened to him on 7/14/2020 2:00-2:37

Some of the rich text features are documented here:
https://spaces.avayacloud.com/developers/docs/guides/rich-input

However the web client will accept and render many more html tags if they are sent to it.

Mobile clients had many issues raised for unsupported tags such as address, abbr, bdo, cite, marked, etc. We need an official reference for which tags are supported and which are not.

As a related issue, perhaps the web client should strip or escape any tags coming from other clients that are not officially supported.

https://drive.google.com/file/d/1XQQoSOUH3o7ZUKy12MD6wKsiYQq0Sn3p/view
https://drive.google.com/file/d/1AgMS4BvzjcHbfeOncwXehvEss3PFPQaM/view

• called another DM user

• in call, one user decides to share screen but is unable to

• clicking does not allow to choose which screen to share

• another time it happened on 'my meeting room' call

• not reproducible all the time, please view logs and video

┆Attachments: loganstaging.esna.com-1597952664314.log | loganstaging.esna.com-1597953201006.log

Jaydeep, if we can remove the limitations of the safari as a toggled feature (like what we are doing with large-meeting feature) and we can run a test and see if JSCSDK is already working and try to figure out the limitations.

Steps to reproduce or test this issue

• Use Avaya OCC hub device - (https://www.avaya.com/en/documents/fs-occ-hub-dv15409en.pdf)
• Connect microphone, camera and monitor devices to OCC hub device, have another USB 3.0 connection from OCC hub to PC/Laptop.
• This way mic/camera/display devices were not directly connected to PC/Laptop but through single USB 3.0 connection from OCC hub to PC/Laptop.
• If device drivers are not installed correctly, emulated mic device name for PC/Laptop causes exception in spaces app which in turn causes microphone device not detected properly and call results in collaboration only call.

Note that in interoperability section of Avaya OCC hub device, they mentioned that it supports Avaya IX Meetings Conferencing and not Avaya Spaces.

Got an issue with Spaces meeting room, buttons not visible, User informed: "Spaces refuses to see any of my video or audio tools. Maybe a Chrome problem but it only happens with Spaces. I was setting up to do a live video demo for the PCC when it happened on Tuesday. Zoom to Avaya IX Workplace works but not Spaces. Spaces product management believes I am in the unrecognized browser mod."

┆Attachments: Ronnie.jpg | spaces.avayacloud.com (2).har | spaces.avayacloud.com-1595008235403 (1).log

BACKEND LOG CAPTURES:

2020-08-18T20:31:20.652Z - info: [socket-server/backend][validateReceivers] {"receivers":["{"username":"[email protected]","phone_numbers":[],"_id":"5977883f3b3132a1e27cd68a","picture_url":"https:\/\/storage.googleapis.com\/onesna\/pictures\/pfpic_zjane_5dbc83b4-85dc-43f0-a9c5-0e95e045c8b2","type":"user","displayname":"Jane Zhang"}"],"sender":{"username":"[email protected]","picture_url":"https://storage.googleapis.com/onesna/pictures/pfpic_ftx_8f40d136-3a82-4163-b5bd-526b27e674af","type":"user","_id":"5dd421b6bcacd1e2f64e19a2","displayname":"GG (FT)"}}

16:31:20.679 EDT(node:1) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'toString' of undefined at _callee14$ (/app/src/socket-server/socket.backend.js:1384:69) at tryCatch (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:62:40) at Generator.invoke [as _invoke] (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:296:22) at Generator.prototype.(anonymous function) [as next] (/app/node_modules/babel-runtime/node_modules/regenerator-runtime/runtime.js:114:21) at step (/app/node_modules/babel-runtime/helpers/asyncToGenerator.js:17:30) at /app/node_modules/babel-runtime/helpers/asyncToGenerator.js:28:13 at <anonymous> at process._tickDomainCallback (internal/process/next_tick.js:228:7)

• User enrolled on Electron App Download feature
• User downloads the Electron App, installs, open and log in it.
• Make a request to user settings endpoint on backend (users/me/settings) and validate that there is a setting called lastElectronActivity with the timestamp when the user has logged in to the app.
• Open a link to a space on a supported browser and a landing page that prompts the user to open the Desktop App or continue on browser is shown.
• Close the Electron App and open it again (user already logged in).
• Make another request to user settings API and validate that the lastElectronActivity is updated.
• Open a link to a space on a supported browser and a landing page that prompts the user to open the Desktop App or continue on browser is shown.
• Leave the Electron App open for 13 days or more (that is for users that never shutdowns or restart his computers) then check that the timestamp of lastElectronActivity is updated.
• Open a link to an space on a supported browser and a landing page that prompts the user to open the Desktop App or continue on browser is shown
• Close the Electron App and don't use it during 2 weeks or more.
• Open a link to a space on a supported browser and it will navigate to the space in that browser without showing the landing page.

Use this Electron App builds to test that deep links are working as expected on staging:

• macOS: https://drive.google.com/file/d/1NSkExmodGrqy-vBECib0IQDIFELHkwBG/view?usp=sharing
• Windows: https://drive.google.com/file/d/14eI3QoAdCL9i71TORfBcdQWpp8Ky9T6U/view?usp=sharing

adding the following protocol
Socket event type is:
'SEND_MEDIA_SESSION_EVENTS'
payload=
{
"category": "request.app.to.join.meeting",
"content": {
"startupOptions": {
"withCollab":true,
"withAudio": true,
"withVideo": true,
}
},
"topicId": "5b5f64aa505badbfb6ac4f11"
}

this message is broadcased to the sender's personal inbox, the service-worker will receive this and will try to find an active tab to load the app and join the space. if connectionOptions contains only "collab" it will start the session in collab only.

We started the effort to allow a user to delegate collab-only or media connection to his/her other devices. For simplicity if user has a tab open and active we will automatically start the session, if user’s tab is closed or no tab at all, the user will see a desktop notification to click on to accept the request.
Again this is a draft we are working and there is room to improve

[Kieu]System spaces.avayacloud.com- Crash app if user click on link of Avaya spaces developer Documentation
Problem description (be a specific as possible), include step-by-step procedure used to reproduce the issue:
Notes:

•    This issue happens on System spaces.avayacloud.com
  

•    Link: https://spaces.avayacloud.com/developers/docs/guides/filesystem
  

Setup:

•    Direct Space: https://spaces.avayacloud.com/spaces/dashboard
  

•    User A - Admin - Windows 10 - IP:10.128.224.50 - Chrome - Signed in with Google account [email protected]
  

Steps to Reproduce:

1. User A in spaces
   

2. User A copy link https://spaces.avayacloud.com/developers/docs/guides/filesystem and send it in chat Spaces
   

3. User A clicks on link
   

4. Observe
   

Expected Result:
1, 2: User A sends link successfully
3: Web will redirect to new page
Actual result:
1, 2. As expected
3. crash app
Workaround: no

SV comment for blocking status: This is a blocked issue

Is the issue reproducible: 100%

Note:

• This issue also happen on production system
• We had similar item before ✓ [Anton] System loganstaging.esna.com - DM call - Caller is dropped from meeting right after callee clicks Yes to join DM call but the flow is backward

Setup:
UserA - Tho Pham - Admin of group space1 https://spaces.avayacloud.com/spaces/5f321109959ad779de290d23?pwd=d3ae2328ca421ac4947a971dd91c0796
UserB - Test04 - Member
UserC - Ruby - Ano guest

Steps:

1. UserA, userB, userC are in space1 meeting
2. UserC clicks userA's entry in roster list to open userA's DM
3. UserC starts DM meeting with userA
4. UserC sends some chat messages to userA
5. UserA clicks Join button to join DM call with userC --> Right after userA clicks Yes to join DM call with userC, userA is dropped from DM call

SV comment for blocking status: This is a blocked issue

Is the issue reproducible: 100%

@Ray Gerami please help to check what sprint is fit for this item

┆Attachments: UserA - Tho Pham - spaces-candidate.avayacloud.com-1597408236987.log | UserB - Ruby - spaces-candidate.avayacloud.com-1597408253135.log | Video_2020-08-14_193001.mp4

Problem description (be as specific as possible), include step by step procedure used to reproduce the issue:
In a space with 2 users and no one starts meeting but new meeting card is auto added with ACTIVE status. Refresh the page does not help to clear this ACTIVE status.

Note:

• This issue happens on other with other tma accounts

Setup:

• Space https://loganstaging.esna.com/spaces/5f3e47d6579a4c137bb7d705

Steps:

1. UserA starts meeting
2. UserA ends meeting
   3. Wait for a minute --> New meeting is auto started with ACTIVE status

SV comment for blocking status: This is a blocked issue

Is the issue reproducible: 100%

┆Attachments: Video_2020-08-20_172612.mp4 | loganstaging.esna.com-1597919309493.log | Screenshot_1.png | ray-loganstaging.esna.com-1597924691489.log

Lukas's comments:

receivers:

• _id: unique identifier of the receiver
• authorizedBy: NOT FOUND IN BACKEND @ MessageConstants.js:803
• authorizedResources: NOT FOUND IN BACKEND @ MessageConstants.js:803
• displayname: the display name of the receiver
• picture_url: URL linking to the profile picture of the receiver
• scopeNOT FOUND IN BACKEND @ MessageConstants.js:803
• type: type of the receiver, can be either 'user' or 'anonymous'
• username: the username of the receiver

Payload ('media.session.invalid') INFERED FROM BACKEND, COULD BE WRONG
Payload for dialin user ('app.event.presence.party.online') COULD NOT TEST IT
Payload for dialin user ('app.event.presence.party.leaves') COULD NOT TEST IT

I checked current structure of roster and found some things you should fix for better perfomance:

1. We use AutoSizer component for react-virtualized List component, would be better if AutoSizer would be removed. AutoSizer receives children as function, so each time it will be rerendered.
2. Current data flow for MembersContainer is bad. The best way would be to update attendeesSelector to return only sorted attendees IDs. For now it returns big object with all attendee properties. So you can pass attendeeId to ContactItemContainer and receive all props from redux state inside.
3. UserPicture component produces a lot of cascading update (I found it in profiler). I am not sure how to fix this, but this issue can produce lags for large meetings.

initial PR fix:
https://github.com/esna/spaces-front/pull/3366

Site Tested: https://loganstaging.esna.com

Description: The new Direct Space Calling feature is not available through quick chat window (Please refer to attached vIdeo).

Note: Both users have the new direct space calling feature enabled and it works as expected through direct messages tab but the new feature is not available through quick chat.

┆Attachments: Direct_Space_Calling_ Jul 31, 2020 2_37 PM.mp4 | loganstaging.esna.com-07_31_2020.log

At times the Chrome Consumes 100% of the CPU and the Screen Sharing freezes or it turns in a black Screen. Attached the Screenshot for it.

CPU - i5 with 32GB RAM

┆Attachments: Print_Screen-1593186455661.png | Performance-testing.docx | image001.jpg | spaces.avayacloud.com-1598437187616.log

adding the following protocol
Socket event type is:
'SEND_MEDIA_SESSION_EVENTS'
payload=
{
"category": "request.app.to.connect",
"content": {
"connectionOptions": ["collab"] // possible values "collab", "audio","video"
},
"topicId": "5b5f64aa505badbfb6ac4f11"
}

this message is broadcased to the sender's personal inbox, the service-worker will receive this and will try to find an active tab to load the app and join the space. if connectionOptions contains only "collab" it will start the session in collab only.

We started the effort to allow a user to delegate collab-only or media connection to his/her other devices. For simplicity if user has a tab open and active we will automatically start the session, if user’s tab is closed or no tab at all, the user will see a desktop notification to click on to accept the request.
Again this is a draft we are working and there is room to improve

• need to port all supported languages into app/sw/_locale

Problem description (be as specific as possible), include step by step procedure used to reproduce the issue:
Users can't join meeting when click "Join Meeting" in Group space, Personal space and DM

Notes:
- This issue don't happen on production system

Setup:
UserA - Kiet Truong ([email protected]) - admin of https://loganstaging.esna.com/spaces/5f3b3115b0d7ac8f4b1d84a3
UserB - Tho has a very long first name that no one has Pham ([email protected]) - admin of https://loganstaging.esna.com/spaces/5f3b3115b0d7ac8f4b1d84a3

Steps:

1. UserA and UserB are in the same group space, personal space or DM
2. UserB starts video meeting
3. UserA click "Join Meeting" --> UserA can't join meeting
   SV comment for blocking status: This is a blocked issue

Is the issue reproducible: 100%

┆Attachments: Kiet Truong - Admin - loganstaging.esna.com-1597894467250.log | Kiet Truong - Admin.png | Tho Pham - Admin - oganstaging.esna.com-1597896397516.log | Tho Pham - Admin.png | Video_2020-08-20_104206.mp4

• happened suddenly, was working for most of the day

https://drive.google.com/file/d/1nsb63w3QrnzMWJJUamiPnUs-znuCrI-G/view

┆Attachments: loganstaging.esna.com-1597954056999.log | image.png | Kiet Truong - Admin.png

pwa is removed from manifest.json

====================
Thanks, Vineet I know what you mean now, it's PWA

I'm thinking to shut down that PWA since we're developing ElectronApp.

@Geramikhosh, Alireza (Ray) [email protected],

@aslam, Umair (Umair) [email protected] I think this is a miss, PWA is probably a burden to us if we cannot make it perfect. Since we're working on ElectronApp and no bandwidth to perfect PWA, can we disable it? Let me know

Regards,

Zack

Zack Cao | Director, Software Engineering | Avaya Cloud |
30 West Beaver Creek Rd | Suite 101 Richmond Hill, ON L4B 3K1 Canada |
[email protected] [email protected] | avaya.com http://www.avaya.com |
1(905)707-4630

From: Kotagiri, Vineet K (Vineet) [email protected]

Sent: Friday, August 7, 2020 11:50 AM

To: Cao, Yongzhong (Zack) [email protected]; Vlasenko, Sergey (Sergey) CTR [email protected]

Cc: Xie, Jing (Jerry) [email protected]

Subject: Re: SR #1-16285322262 IX Spaces: 404 Space Not Found error when clicking on Spaces Desktop shortcut

Sergey - Thank you!

Zack

I am referring to the Chrome web App that is available to install when you go login to the Spaces portal/dashboard via a + symbol in the top right of the address bar.
Clicking on it asks you to install the Spaces App which then moves that browser session to a new window, which almost feels like a standalone client.
It also creates a desktop shortcut using which you can launch the Spaces portal directly without going to the browser.
The problem is when you launch from the shortcut you see the error and have to click on Go Home to get to Dashboard.

Sent from my mobile

From: Cao, Yongzhong (Zack) [email protected]

Sent: Friday, August 7, 2020 5:40:00 AM

To: Vlasenko, Sergey (Sergey) CTR [email protected]; Kotagiri, Vineet K (Vineet) [email protected]

Cc: Xie, Jing (Jerry) [email protected]

Subject: Re: SR #1-16285322262 IX Spaces: 404 Space Not Found error when clicking on Spaces Desktop shortcut

Thanks, Sergey

Hi, Vineet

I'm not sure I fully get the context, Spaces has not released Desktop app yet, I'm wondering whether it's related to IX Workplace desktop. Jerry, do you have idea on what Vineet is trying to report?

Zack Cao | Director, Software Engineering | Avaya Cloud |
30 West Beaver Creek Rd | Suite 101 Richmond Hill, ON L4B 3K1 Canada |
[email protected] [email protected] | avaya.com http://www.avaya.com |
1(905)707-4630

From: Vlasenko, Sergey (Sergey) CTR [email protected]

Sent: Friday, August 7, 2020 6:58 AM

To: Kotagiri, Vineet K (Vineet) [email protected]; Cao, Yongzhong (Zack) [email protected]

Cc: Xie, Jing (Jerry) [email protected]

Subject: RE: SR #1-16285322262 IX Spaces: 404 Space Not Found error when clicking on Spaces Desktop shortcut

Hi Vineet,

I would believe this is about Spaces desktop app – that is handled by
@cao, Yongzhong (Zack) [email protected]’s team.

Thanks
Sergey

Vacation Alert: Aug 17th 2020 – Aug 26th 2020

From: Kotagiri, Vineet K (Vineet) [email protected]

Sent: Friday, August 7, 2020 5:13 AM

To: Vlasenko, Sergey (Sergey) CTR [email protected]

Cc: Xie, Jing (Jerry) [email protected]

Subject: FW: SR #1-16285322262 IX Spaces: 404 Space Not Found error when clicking on Spaces Desktop shortcut

Hi Sergey

Hope you are doing well!
Is this something you would typically work on?
Please see below.

Thanks!

From: Kotagiri, Vineet K (Vineet)

Sent: Thursday, August 6, 2020 6:18 PM

To: Akshat, Mehta (Mehta) CTR [email protected]; Calulo, Peter-Glenn P (Peter-Glenn) [email protected]

Subject: SR #1-16285322262 IX Spaces: 404 Space Not Found error when clicking on Spaces Desktop shortcut

Hi Akshat

Just wanted to reach out to you on a similar issue you have been w, rking on as part of SR #1-16266680492.
Do you have any further updates on this from R&D ? I see you have a PEA open but not one has take ownership yet ?
I have been looking into this issue for a while now as I happened to notice this issue a couple weeks back when I initially installed it.
Based on the investigation I have done so far, workaround options by modifying the target path in the shortcut may not work as I have tried various options.

Initially I thought the problem was related to the
manifest.json file from which the app reads and it can be found at:
C:\Users<userID>\AppData\Local\Google\Chrome\User Data\Default\Extensions\cmaiilchpongihlpdpgpnddagebmhkfl<TimestampofAppInstall>
The file includes a web_url path which currently points to
https://spaces.avayacloud.com/index.html https://spaces.avayacloud.com/index.html
When you navigate to that link, you will see the exact same 404 error, which confirms the problem is with the path.
So I tried modifying the URL to use https://spaces.avayacloud.com/spaces/dashboard https://spaces.avayacloud.com/spaces/dashboard
, but it did not make a difference.

I also tried additional options of using shortcut command line switches to ignore the json file and use a manual URL path (as below), but that also did not help:
"C:\Program Files (x86)\Google\Chrome\Application\chrome_proxy.exe" --profile-directory=Default --app-id=cmaiilchpongihlpdpgpnddagebmhkfl --app-launch-url-for-shortcuts-menu-item=https://spaces.avayacloud.com/spaces/dashboard

Upon further checking, it looks like the App ignores or does not really use the manifest file as I can completely remove the manifest file from directory and it does not matter.
Given that this is a WebApp shortcut, it looks like it tries to pull the manifest file directly from the cloud when you click on it and does not actually retrieve it from that directory and the only thing it retrieves from that directory
is the desktop Spaces icon (image).
I believe it retrieves it from https://spaces.avayacloud.com/manifest.json https://spaces.avayacloud.com/manifest.json
And if you look it shows the "start_url": "/index.html" and herein lies the problem and not sure this is something that can be modified locally.
My guess it this may need to be updated in the cloud, maybe as
"start_url": "/spaces/dashboard"

I will keep looking for other alternatives to try and find a workaround, but I just wanted to reach out to you and provide my findings.
If you happen to have further updates on this, then please share.

Thanks!

Desktop app - build 1.1.14 contains:

✓ On Windows (or probably Mac), click the X cross button on the top left (right) does NOT kill the process, it instead minimize it in the tray

✓ Update macOS installer background

Link to download macOS and Windows binaries:
https://drive.google.com/drive/folders/1Sy4A-JwoIT-Cyc6u-a5I5ma10GY0tZyP?usp=sharing