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

Data not aligned after fire of new space event / new message. #128

Open
spardosj opened this issue May 9, 2022 · 7 comments
Open

Data not aligned after fire of new space event / new message. #128

spardosj opened this issue May 9, 2022 · 7 comments

Comments

@spardosj
Copy link

spardosj commented May 9, 2022

After the fire of the events receive "Decrypting" in title for space and text for message.
The SDK only working in update events with the correct data.

@jbenyovs
Copy link

jbenyovs commented May 9, 2022

@spardosj can you please confirm the following:

  • is the issue reproducible using the iOS KS app: https://github.com/webex/webex-ios-sdk-example ?
  • please provide a full, step by step description on how to reproduce the issue.
  • what version of the iOS SDK are you using if the issue is not reproducible with the KS app?
  • do you have screenshots showing the issue?
  • do you have the full client logs from when the issue is being reproduced?

@spardosj
Copy link
Author

spardosj commented May 9, 2022

image

Same issue in kitchen sink app, unable to fetch correctly the data from the "onevent" callback in SpaceClient and MessageClient, look the watch region in screenshot. In Kitchen sink all the event call a function for refresh the array used in the view, a new space fire two events in sdk: - new space - update space and when the new space fire the "update" this refresh the whole array with the "correct data", but is not correct at all. Using proxyman to watch the call of the sdk and I notice a web socket connection for the data refresh, recall the entire function after a websocket event ("new space"..) for refresh the data is not the best.

I think the best is to use the event for update the array and use less network in mobile cases.

SDK version : 3.4.0
IOS: 15.4.0
same issue in my app, like the screenshot.
tanks for the reply @jbenyovs !

@jbenyovs
Copy link

@spardosj thanks for the response. I am sorry, but based on your description I am still unsure what the actual issue is. You mention that "the data" from certain events is not correct, but you do not point out what exactly is wrong. Can you please formulate the issue using the below format:
- describe how to reproduce the issue step by step, like:

  1. login to the KS app with user A
  2. create a new space with user B, add user A
    etc.

- when you get to the part where you observe the issue, specify this:

  1. actual behaviour / payload
  2. expected behaviour / payload

At this point I would also recommend opening a Dev Support ticket with us - email to devsupport@webex.com - that way we might iron out the details easier. Thank you

@spardosj
Copy link
Author

spardosj commented May 10, 2022

image
@jbenyovs thanks for the response, in the screenshot the key "title" contain "Decrypting Conversation" but in webex app is "pippo161".
This issue is present only in "create" events.

@jbenyovs
Copy link

@spardosj thank for the reply, but we are still missing the reproduction part. Also, as recommended, could you maybe open a Dev Support ticket with us - email to devsupport@webex.com - that way we might iron out the details easier. Thank you

@spardosj
Copy link
Author

spardosj commented May 13, 2022

@spardosj thank for the reply, but we are still missing the reproduction part. Also, as recommended, could you maybe open a Dev Support ticket with us - email to devsupport@webex.com - that way we might iron out the details easier. Thank you

Reproduction steps:
1 - create a breakpoint into the spaces.onEvent function in create space case
2 - send a new case to the user via another user
3 - inspect the payload after the breakpoint is fired

In the payload you notice the key "title" will equal to "Decrypting Conversation"

Thank @jbenyovs

@jbenyovs
Copy link

@spardosj okay, thank you for the steps. I will open a ticket with engineering, for that would you mind opening a ticket with us as requested before - email to devsupport@webex.com ? The reason I keep asking for it, is that I can link the support ticket with the engineering ticket, but I can't do the same for the GitHub issue. So if you open a support ticket, we can keep you informed. Please if you send us a ticket, also send us the full application logs. Thank you

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

2 participants