search

Cloudkibo / Kibo_Client_iOS

0 stars 0 forks source link

Mobile Client can send message using push notifications #2

Closed sumairasaeed closed 8 years ago

sumairasaeed commented 8 years ago

We have socket.io logic written already in KiboChat. We just have to copy it in new application and make it working.

sumairasaeed commented 8 years ago

Worked on this. This is under construction. Coded socket listeners for chat.

sumairasaeed commented 8 years ago

I was unable to connect to socket of kibo engage. Discussed with sojharo and he said that server will block iOS and Android to connect to socket. We will have to put SSL certificates on KiboEngage. He has opened this issue here https://github.com/Cloudkibo/KiboEngage/issues/136

sumairasaeed commented 8 years ago

There was minor error in socket URL i was passing previously. I tried again and it successfully got connected to socket. kibo engage server didnot block iOS from connecting to socket.

sumairasaeed commented 8 years ago

Worked on this. This task has been done. Now mobile client can send message to agents. Here is screenshot showing test message received on web from mobile image

jekram commented 8 years ago

Thanks

sumairasaeed commented 8 years ago

We need to use push notifications instead of socket.io

sumairasaeed commented 8 years ago

Sir, I am removing this task from todays deck as you said we will discuss it again tomorrow. Because currently, as mentioned by @zarmeen kibo engage server is dependent of socket for receiving messages from web and mobile. Replacing socket with push notifications will need changes on server also. Will work on this task after discussion tomorrow IA

jekram commented 8 years ago

@sumairasaeed

We will discuss this tomorrow and I have sent the email also on it:

We have two piece to logic:

  1. Mobile Client to Server
  2. Web Client to Server

We changed #1 in KiboChat and I do not think it has anything to do with #2.

Let's not worry about #2 we will decide tomorrow. But we proceed with #1 in any case.

sumairasaeed commented 8 years ago

ok sir

On Tue, Oct 4, 2016 at 12:02 PM, Cloudkibo notifications@github.com wrote:

@sumairasaeed https://github.com/sumairasaeed

We will discuss this tomorrow and I have sent the email also on it:

We have two piece to logic:

  1. Mobile Client to Server
  2. Web Client to Server

We changed #1 https://github.com/Cloudkibo/Kibo_Client_iOS/issues/1 in KiboChat and I do not think it has anything to do with #2 https://github.com/Cloudkibo/Kibo_Client_iOS/issues/2.

Let's not worry about #2 https://github.com/Cloudkibo/Kibo_Client_iOS/issues/2 we will decide tomorrow. But we proceed with #1 https://github.com/Cloudkibo/Kibo_Client_iOS/issues/1 in any case.

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Cloudkibo/Kibo_Client_iOS/issues/2#issuecomment-251309732, or mute the thread https://github.com/notifications/unsubscribe-auth/AKbhp4rSi-zfBNTmFJ9C1ewGUdqJY0pqks5qwfoMgaJpZM4J0Oig .

sumairasaeed commented 8 years ago

Changing name of this issue. As we are now not using socket. we will use push notifications

jekram commented 8 years ago

What is the next step vs.changing the name of the task?

sumairasaeed commented 8 years ago

We will use server side endpoint created to send chat message.

On Sat, Oct 8, 2016 at 10:47 AM, Cloudkibo notifications@github.com wrote:

What is the next step vs.changing the name of the task?

— You are receiving this because you modified the open/close state. Reply to this email directly, view it on GitHub https://github.com/Cloudkibo/Kibo_Client_iOS/issues/2#issuecomment-252404917, or mute the thread https://github.com/notifications/unsubscribe-auth/AKbhpyW1Q3Fr4hXm1aVMSwLt1GIcvCLZks5qxy6IgaJpZM4J0Oig .

sumairasaeed commented 8 years ago

Completed work on this. Message is now sent to web using push notifications.

jekram commented 8 years ago

Are we publishing the code to test flight?