mesibo/messenger-app-android

I/MesiboJNI: E(0705-191400-027)(7010): *** BUG *** Create client unix socket failed

Closed this issue · 16 comments

kvnramirez commented

With Mesibo STATUS_ONLINE, getting:
I/MesiboJNI: E(0705-191400-027)(7010): *** BUG *** Create client unix socket failed

This happends when I call the method: mesibo.sendMessage(messageParams, msgid, message);

Mesibo needs better documentation, also check: mesibo/samples#21

I'm having Issues with android 4.4.2 using mesibo android sdk.

mesibo commented

Is this issue also in 4.4.2?

kvnramirez commented

On android 4.4.2 and above. As I see, the only way to dissapear that error is starting mesibo always on MainApplication, if you start Mesibo on other Activity, somethimes throws that error.

karan1213 commented

I am receiving this error too, How did you manage to fix this.

mesibo commented

Initialize Mesibo from Application and not from activity/fragmenet

karan1213 commented

But when we authenticate the user to our own server first and then I login user to Mesibo in the background, I had to trigger 'Mesibo Init' method from Login Activity. Although the Actual method is being executed inside the Application class.

I am invoking it like this getApplication().startMesibo(String accessToken)
This throws above error and Audio/Video call doesn't get through.

I tried going back to home and restarting app, it still throws the same error untill I kill the app and restrat app. After then it works fine.

mesibo commented

Karan, you can initialize Mesibo from App and start whenever you like later.

For example,
https://github.com/mesibo/messenger-app-android/blob/master/app/src/main/java/org/mesibo/messenger/SampleAPI.java#L569

As you can see, init function is called from MainApplication which initializes Mesibo and start() much later when the token is obtained.

Let us know if you still face issues after this change.

karan1213 commented

Yes, I'm initializing in Application only.

BTW what does Restart Intent do?

Intent restartIntent = new Intent(MainApplication.getRestartIntent());
        Mesibo.runInBackground(MainApplication.getAppContext(), null, restartIntent);

Is this being used to restart Application?

karan1213 commented

I noticed that this error occurs in the sample app too. The Audio/Video call doesn't go through some time until I kill the app and restart it after then Call works fine and the exception disappears too.

mesibo commented
  1. Are you seeing this also in your logs "Unix server sock failed:"
  2. Can you try the Google Play store version too and let us know if you can reproduce.

I am anyway raising this with the development team.

karan1213 commented
  1. Logs show two kinds of exceptions
*** BUG *** openssl session management not implemented

 *** BUG *** Create client unix socket failed: /data/user/0/<packagename>/Mesibo/usock
  1. Yes, the issue exists in Play store version as well. I have tried this on Nokia 8.1 (Android 9.0) device.
mesibo commented

Please update to the latest version and see if "Create client unix socket failed:" is resolved. Disregard openssl log for now.

karan1213 commented

Yeah updated SDK to implementation 'com.mesibo.api:mesibo:1.0.80'
And working fine now. Thanks!

maddenbrain commented

Have this logs on version 'com.mesibo.api:mesibo:1.0.90'.

mesibo commented

It is not possible as that is fixed a long back and that text was entirely removed. You MUST be using an old API.

maddenbrain commented

But I have these logs.
Maybe I'm using mesibo in a wrong way?
How can I contact your support? Any live chat?

Edit:
I also using 'com.mesibo.api:ui:1.1.32', and connection managed via MesiboMessagingFragment.
May be mesibo UI library depends on old mesibo lib?

mesibo commented

Certainly! You can reach us here http://mesibo.com/ticket