Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SpaceClient.getMeetingInfo() is not returning #91

Open
gmoens-vuzix opened this issue Nov 2, 2021 · 3 comments
Open

SpaceClient.getMeetingInfo() is not returning #91

gmoens-vuzix opened this issue Nov 2, 2021 · 3 comments

Comments

@gmoens-vuzix
Copy link
Contributor

gmoens-vuzix commented Nov 2, 2021

Noticed this issue beginning with SDK 3.2. It is not consistent user to user, but for a given user the behavior is consistent.

When you call SpaceClient.getMeetingInfo(spaceId, handler), you provide a CompletionHandler to be called back when the results are available. But in some cases the CompletionHandler is never called back.

I have a space with two users in it. When I log in as one of those users, the space info loads successfully and the CompletionHandler is called back.

D/WebexApplication: attempting to get meeting info for space c5fe25c0-62ed-11ea-8891-ef9e6eaf861e D/WBX_TEAMS-ucf: tid[0x7c37f13548] ConversationService.cpp::2350 getRoomMeetingInformation:Attempting to fetch meeting info from server side for conversation c5fe25c0-62ed-11ea-8891-ef9e6eaf861e D/WBX_TEAMS-ucf: tid[0x7c37f13548] TelephonyAdapter.cpp::1258 logPrivateData:LOCUS_DTO: RestRequest: {"lookupType":"CONVERSATION_URL","sequence":{"entries":[],"rangeEnd":0,"rangeStart":0},"value":"https://conv-a.wbx2.com/conversation/api/v1/conversations/c5fe25c0-62ed-11ea-8891-ef9e6eaf861e"} for notificationId = , pid = 8072 D/WBX_TEAMS-ucf: tid[0x7b8c7384f0] TelephonyAdapter.cpp::1258 logPrivateData:LOCUS_DTO: RestResponse: {"conversationUrl":"https://conv-a.wbx2.com/conversation/api/v1/conversations/c5fe25c0-62ed-11ea-8891-ef9e6eaf861e","displayMeetingUrl":"private","isCallInEnabled":false,"isSparkPstnEnabled":false,"locusCallUrl":"private","locusUrl":"https://locus-a.wbx2.com/locus/api/v1/loci/da6438f2-3363-31ef-864e-2cbde89f1b67","maxParticipants":100,"meetingLink":"private","meetingNumber":"__removed__","numericCode":"__removed__","sipMeetingUri":"private","uri":"private"} for notificationId = , pid = 8072 D/WebexApplication: meeting info loaded successfully for space c5fe25c0-62ed-11ea-8891-ef9e6eaf861e

Then I log out and log back in with the other user in the space, the CompletionHandler is never called back and the log is different.

D/WebexApplication: attempting to get meeting info for space c5fe25c0-62ed-11ea-8891-ef9e6eaf861e D/WBX_TEAMS-ch: [FUNCTION_CALL] ZygoteInit.java::858 main:IOmniusServiceBridge.getMeetingInfo() D/WBX_TEAMS-ucf: tid[0x7b8c9344f0] HttpRequestManager.cpp::2600 _removeOutstandingRequest:requestId: 251a590e-87f4-427d-9006-7550b368e423, Outstanding HTTP requests: 0 D/WBX_TEAMS-ucf: tid[0x7c37f13548] ConversationService.cpp::2350 getRoomMeetingInformation:Attempting to fetch meeting info from server side for conversation c5fe25c0-62ed-11ea-8891-ef9e6eaf861e D/WBX_TEAMS-ucf: tid[0x7c37f13548] TelephonyService.cpp::12731 getSpaceMeetingInfo:will get space meeting from webex appapi D/WBX_TEAMS-ucf: tid[0x7c37f13548] WebexMeetingInfoManager.cpp::36 getSpaceMeetingInfo:use wbxappapi for conversation meetingInfo W/WBX_TEAMS-ucf: tid[0x7c37f13548] WebexMeetingInfoManager.cpp::145 getMeetingInfoFromWebexMeetingService:WebexMeetingService not loaded D/WBX_TEAMS-ch: [FUNCTION_RETURN] ZygoteInit.java::858 main:<-- 5ms IOmniusServiceBridge.getMeetingInfo(): void

Notice, it says "WebexMeetingService not loaded". Not sure if this part of the problem.

For the user that doesn't work, it consistently doesn't work. For the user where it works, it consistently works. Force stopping the app or uninstalling/reinstalling does not change the behavior.

I call getMeetingInfo() from a background thread. I tried changing to calling on the main UI thread, there is no difference. The CompletionHandler is never called back in either case.

@gmoens-vuzix
Copy link
Contributor Author

This issue appears to be fixed in SDK 3.2.1

@gmoens-vuzix
Copy link
Contributor Author

This bug has returned in SDK 3.3.0.

@gmoens-vuzix gmoens-vuzix reopened this Feb 28, 2022
@gmoens-vuzix
Copy link
Contributor Author

Still an issue in SDK 3.4.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant