Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • J jami-client-gnome
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 88
    • Issues 88
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • savoirfairelinux
  • jami-client-gnome
  • Issues
  • #654

Closed
Open
Created Jul 27, 2017 by RingBot@RingBotOwner

Sending message always failed. (Android version success)

Issue generated from Tuleap's migration script. Originally submitted by: Karl Vito Lam (karlvlam)

A detailed description of the bug. Use following fields for description field:

Sending message always failed. (Android version success)

* Environment:
Ubuntu 16.04
ring version: 20170720.1.f450dea~dfsg

* Reproduce steps:
send message, wait for a long time... Failure...

* Expected result:
message send success

* Actual result:
What is the actual result on running the above steps i.e. the bug behavior.

Assignee
Assign to
Time tracking