-
Notifications
You must be signed in to change notification settings - Fork 3
Home
Welcome to the xabber-ios wiki! Here are some notes regarding current testing stage.
-
Xabber for iOS is a very incomplete product at the moment. It does not have proper support for such XMPP features as authorization requests. We DO support sending media and VoIP calls, but e2ee is currently not supported. The goal of this stage is to establish a reliable connection between client and server.
-
Xabber does support Message Archive (XEP-313), Message Carbons (XEP-0280), Push notifications (XEP-0357). We aim to achieve full sync between more mature clients such as Xabber for Web or Xabber for Android, that make emphasis on recent user conversations. Ideally working iOS client should have exactly same conversation list as other clients, and should act in sync with them, as much as it is possible with push notifications.
-
Xabber for iOS uses Background Update Notifications, that have an advantage over alert type notifications is that they do not deliver any readable content over Apple's services. The downside is that they are less reliable. Currently used notifications can also be turned off if a user swipes the app. This can be remedied only by using a more reliable VoIP background notifications, which we plan to do, eventually.
Instructions on joining beta testing.
- Incoming chat requests are not finished, so they work buggy
- App often crashes, this is normal at this stage, causes are known. Bugs will be fixed when we'll get back working onto relevant part of an app
- Many features are not yet implemented, have patience, we're doing the best we can. If you have no patience and have some extra funds, donate to our crowdfunding campaign. Maybe we'll be able to bring in more developers and speed up things.
For any other encountered issues, please use this issue tracker. It would be best if you provide a detailed instruction how to reproduce encountered issues. Videos of weird behaviour are cool, too.