Open-source XMPP client for Android

I just tried upgrading the app on f-droid, but I noticed that the recent releases (2.0.2 and 2.1) introduced crashlytics resp. google play services, which are closed source libraries.

Could you provide a gradle build flavour that doesn't use these libraries so the app can be updated on F-Droid again?

If one side exits xabber ( exit xabber from menu, reboot phone, etc) without stop encryption, you cant get otr chat no more. To reproduce this problem both sides need to use newer xabber versions ( from 0.10.. ). If one side using 0.90 there no problem

Used versions 10.45, 10.62, beta 1.02

If there would be a way to send files via xmpp, and to see them in-chat, we could push whatsapp to the trash bin.

XEP-0096 - http://xmpp.org/extensions/xep-0096.html

since 1.0.24 (or 1.0.23,i don't know) there is a problem connecting to jabber server. password prompt shows up as usual, password is given, icon in taskbar doesn't change to "connected" (full lightbulb), status is "available", and no contacts are shown in list.

this doesn't happen in 0.9.30 - everything is fine there,so i assume the problem is on xabber side, not the account in question.

i use two accounts, the other one is gmail, and it works as usual (in beta).

i also cleaned cache and full application data - no change.

Unfortunately, prosody doesn't support XEP-0136 any more. It will be superseeded by XEP-0313. Using the same history on desktopclients and on smartphones like it was possible with XEP-0136 would be nice. http://xmpp.org/extensions/xep-0313.html

org.jivesoftware.smack.SmackException$NoResponseException: No response received within reply timeout. Timeout was 30000ms (~30s). While waiting for establishing TLS at org.jivesoftware.smack.SynchronizationPoint.checkForResponse(Unknown Source) at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWait(Unknown Source) at org.jivesoftware.smack.SynchronizationPoint.checkIfSuccessOrWaitOrThrow(Unknown Source) at org.jivesoftware.smack.AbstractXMPPConnection.connect(Unknown Source) at com.xabber.android.data.connection.ConnectionThread.connectAndLogin(Unknown Source) at com.xabber.android.data.connection.ConnectionThread$1.run(Unknown Source) at java.lang.Thread.run(Thread.java:761)

This happens with 1.0.42 and above, 1.0.39 works fine, all from F-Droid. I'll post a screenshot of the actual error message in a bit, but it comes from org.jivesoftware.smack.SmackException$ConnectionException

I have a few recent chas showing at the top when i run Xabber. I try to archive them, but every time i run xabber again, they show up. Only removing room bookmark or contact makes it disappear for good. Xabber is not allowed to run in background. Maybe it can't save state of chats because of that.

crashes when starting/opening conversation , no issues with 0.10.1x versions

could be "No permission to prevent power key"?

I/dalvikvm( 6702): Could not find method android.view.Window.setStatusBarColor, referenced from method com.xabber.android.ui.ChatViewer.updateActionBar W/dalvikvm( 6702): VFY: unable to resolve virtual method 11769: Landroid/view/Window;.setStatusBarColor (I)V D/dalvikvm( 6702): VFY: replacing opcode 0x6e at 0x0032 I/dalvikvm( 6702): Could not find method android.view.Window.getStatusBarColor, referenced from method com.xabber.android.ui.ChatViewer.onCreate W/dalvikvm( 6702): VFY: unable to resolve virtual method 11766: Landroid/view/Window;.getStatusBarColor ()I D/dalvikvm( 6702): VFY: replacing opcode 0x6e at 0x0065 I/dalvikvm( 6702): Could not find method android.view.Window.setStatusBarColor, referenced from method com.xabber.android.ui.ChatViewer.onPageSelected W/dalvikvm( 6702): VFY: unable to resolve virtual method 11769: Landroid/view/Window;.setStatusBarColor (I)V D/dalvikvm( 6702): VFY: replacing opcode 0x6e at 0x002f D/AndroidRuntime( 6702): Shutting down VM W/dalvikvm( 6702): threadid=1: thread exiting with uncaught exception (group=0x415a8ce0) E/AndroidRuntime( 6702): FATAL EXCEPTION: main E/AndroidRuntime( 6702): Process: com.xabber.androiddev, PID: 6702 E/AndroidRuntime( 6702): java.lang.RuntimeException: Unable to start activity ComponentInfo{com.xabber.androiddev/com.xabber.android.ui.ChatViewer}: java.lang.SecurityException: No permission to prevent power key: Neither user 10065 nor current process has android.permission.PREVENT_POWER_KEY. E/AndroidRuntime( 6702): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2212) E/AndroidRuntime( 6702): at android.app.ActivityThread.handleLaunchActivity(ActivityThread.java:2271) E/AndroidRuntime( 6702): at android.app.ActivityThread.access$800(ActivityThread.java:144) E/AndroidRuntime( 6702): at android.app.ActivityThread$H.handleMessage(ActivityThread.java:1205) E/AndroidRuntime( 6702): at android.os.Handler.dispatchMessage(Handler.java:102) E/AndroidRuntime( 6702): at android.os.Looper.loop(Looper.java:136) E/AndroidRuntime( 6702): at android.app.ActivityThread.main(ActivityThread.java:5146) E/AndroidRuntime( 6702): at java.lang.reflect.Method.invokeNative(Native Method) E/AndroidRuntime( 6702): at java.lang.reflect.Method.invoke(Method.java:515) E/AndroidRuntime( 6702): at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:732) E/AndroidRuntime( 6702): at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:566) E/AndroidRuntime( 6702): at dalvik.system.NativeStart.main(Native Method) E/AndroidRuntime( 6702): Caused by: java.lang.SecurityException: No permission to prevent power key: Neither user 10065 nor current process has android.permission.PREVENT_POWER_KEY. E/AndroidRuntime( 6702): at android.app.ContextImpl.enforce(ContextImpl.java:1749) E/AndroidRuntime( 6702): at android.app.ContextImpl.enforceCallingOrSelfPermission(ContextImpl.java:1778) E/AndroidRuntime( 6702): at android.content.ContextWrapper.enforceCallingOrSelfPermission(ContextWrapper.java:572) E/AndroidRuntime( 6702): at android.view.Window.setFlags(Window.java:749) E/AndroidRuntime( 6702): at android.view.Window.addFlags(Window.java:709) E/AndroidRuntime( 6702): at com.xabber.android.ui.ChatViewer.onCreate(ChatViewer.java:139) E/AndroidRuntime( 6702): at android.app.Activity.performCreate(Activity.java:5231) E/AndroidRuntime( 6702): at android.app.Instrumentation.callActivityOnCreate(Instrumentation.java:1087) E/AndroidRuntime( 6702): at android.app.ActivityThread.performLaunchActivity(ActivityThread.java:2169) E/AndroidRuntime( 6702): ... 11 more W/ActivityManager( 583): Force finishing activity com.xabber.androiddev/com.xabber.android.ui.ChatViewer I/WindowManager( 583): Screenshot max retries 4 of Token{41cda500 ActivityRecord{41dca188 u0 com.xabber.androiddev/com.xabber.android.ui.ChatViewer t33 f}} appWin=Window{41c8eec0 u0 Starting com.xabber.androiddev} drawState=4 W/WindowManager( 583): Screenshot failure taking screenshot for (1080x1920) to layer 21080 W/ActivityManager( 583): Activity pause timeout for ActivityRecord{41dca188 u0 com.xabber.androiddev/com.xabber.android.ui.ChatViewer t33 f} I/Timeline( 897): Timeline: Activity_idle id: android.os.BinderProxy@419d9eb0 time:13051528 I/Timeline( 583): Timeline: Activity_windows_visible id: ActivityRecord{41f10050 u0 com.cyanogenmod.trebuchet/org.cyanogenmod.trebuchet.CustomHomeLauncher t1} time:13051914 I/Process ( 6702): Sending signal. PID: 6702 SIG: 9 W/InputMethodManagerService( 583): Window already focused, ignoring focus gain of: com.android.internal.view.IInputMethodClient$Stub$Proxy@41e4bb08 attribute=null, token = android.os.BinderProxy@41e0d800 I/ActivityManager( 583): Process com.xabber.androiddev (pid 6702) has died. I/ActivityManager( 583): START u0 {act=com.android.systemui.recent.action.TOGGLE_RECENTS flg=0x10800000 cmp=com.android.systemui/.recent.RecentsActivity} from pid 707 W/InputMethodManagerService( 583): Starting input on non-focused client com.android.internal.view.IInputMethodClient$Stub$Proxy@41cb5788 (uid=10016 pid=897) I/Timeline( 707): Timeline: Activity_idle id: android.os.BinderProxy@42207398 time:13055547 I/Timeline( 583): Timeline: Activity_windows_visible id: ActivityRecord{41b97a10 u0 com.android.systemui/.recent.RecentsActivity t19} time:13055817 I/InputReader( 583): Reconfiguring input devices. changes=0x00000004 I/InputReader( 583): Device reconfigured: id=19, name='sec_touchscreen', size 1080x1920, orientation 1, mode 1, display id 0 I/ActivityManager( 583): Config changes=480 {0.85 238mcc20mnc en_US ldltr sw360dp w640dp h335dp 480dpi nrml long land finger -keyb/v/h -nav/h s.40 themeResource=null} I/InputReader( 583): Reconfiguring input devices. changes=0x00000004

Xabber doesn't seem to detect the XEP-0363 (HTTP File Upload) support of the XMPP server of feministwiki.org. It's marked as not supported under "Server info" and trying to send a file gives an error message saying the server doesn't support it.

Gajim on Windows successfully detects the support and is able to send files to other users just fine, so the server definitely supports it.

What might be causing Xabber to think it's not supported?

The problem with the last commit, is that when changing the theme, then clicking on a contact, Xabber crashes.

Actually adding the dark theme, made me discover an issue in the menu (probably related to https://github.com/redsolution/xabber-android/issues/372), is that the menu theme is light even if I use the dark theme.

Hello! I run my own ejabberd server, trying to connect to it with Xabber 2.6.6.645. I do suspect there is something wrong in ejabberd config, and I do understand that this question is rather more appropriate to ejabberd git. After I enabled debug logging:

"2022-10-31 14:37:54.848697+02:00 [error] <0.659.0>@ejabberd_acme:issue_request/7:246 Failed to request certificate for xxxxxxxx.org, pubsub.xxxxxxxx.org and 3 more hosts: Challenge failed for domain conference.xxxxxxxx.org: ACME server reported: DNS problem: NXDOMAIN looking up A for conference.xxxxxxxx.org - check that a DNS record exists for this domain; DNS problem: NXDOMAIN looking up AAAA for conference.xxxxxxxxx.org - check that a DNS record exists for this domain (error type: dns)"

Fixed DNS error, added A record for conference.mydomain.org Still I'm facing with the same error as before. What could be the reason for this? TLS\SSL error?

org.jivesoftware.smack.SmackException$ConnectionException: The following addresses failed: 'xxxxxxxx.org:5222' failed because: xxxxxxxx.org/45.x.x.19 exception: java.net.SocketTimeoutException: failed to connect to xxxxxxxxx.org/45.x.x.19 (port 5222) from /192.168.88.252 (port 51551) after 30000ms at com.xabber.xmpp.smack.XMPPTCPConnection.connectUsingConfiguration(Unknown Source:334) at com.xabber.xmpp.smack.XMPPTCPConnection.connectInternal(Unknown Source:5) at org.jivesoftware.smack.AbstractXMPPConnection.connect(Unknown Source:27) at com.xabber.android.data.connection.ConnectionThread.connectAndLogin(Unknown Source:207) at com.xabber.android.data.connection.ConnectionThread$1.run(Unknown Source:8) at java.lang.Thread.run(Thread.java:923)

Help me please. My project is not compiling. Writes: Could not find com.github.str4tocaster.smack:smack-android-extensions:ffb99cc. Required by: project :xabber > Could not find com.github.str4tocaster.smack:smack-experimental:ffb99cc. Required by: project :xabber > Could not find com.github.str4tocaster.smack:smack-tcp:ffb99cc. Required by: project :xabber > Could not find com.github.str4tocaster.smack:smack-resolver-dnsjava:ffb99cc. Required by: project :xabber

These libraries have been removed from the maven repository. Where can I download these libraries and build the project?

Thanks in advance

Hello,

I'm using Xabber for long, and recently I changed our self hosted xmpp server (ejabberd). I can connect my Xabber 2.6.6.645 to this xmpp server and chat with users, but I find no way to connect to MUC rooms. Either I'm lost and I forgot how to do, either I'm starting to understand that MUC support (XEP-0045) has been removed from this version?

Please advice me.

Steps to reproduce

1. In the mobile, enable both WiFi and Mobile data
2. Login to the XMPP
3. Disable WiFi

Issues here:

1. Xabber is displaying "Reconnecting", but not actually getting connected (even if Mobile Data is available)
2. Even if we activate WiFi again, most of the times it still shows "Reconnecting". Very rarely (say, 1-2% of the times), it reconnects.

Use cases:

1. You're connecting to the WiFi in home and step out.
2. You're connecting to the WiFi and suddenly there are some power outage or router gets restarted for some reasons

I have a doubt that it may be due to changing in IP. But, can't really guess the reason correctly. When we open Xabber, inside it will display indefinite "Authorizing". I also think, other desktop applications such as Pidgin don't have this issue (though not 100% sure about it).

Version: Xabber Beta 3.0.2 Beta (824) Mobile: Redmi, Android 9

Sorry, don't know the correct terminology...

The notification is not displaying in the lock screen. Always need to focus the application to view relevant notifications.

Version: Xabber Beta 3.0.2 Beta (824) Mobile: Redmi, Android 9