Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
J
jami-client-android
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 145
    • Issues 145
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Requirements
    • Requirements
    • List
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • savoirfairelinux
  • jami-client-android
  • Issues
  • #264

Closed
Open
Opened May 13, 2016 by RingBot@RingBotOwner

Android: bug creating empty SIP account

Issue generated from Tuleap's migration script. Originally submitted by: Alexandre Lision (alision)

When trying to transform a SIP account in a IP2IP account (e.g: no hostname) to enable direct ip communications, I got some issues on the Android client.

- Account was not removable/exportable

- Only the Media tab was available in account's settings

Moreover, Since a IP2IP acocunt has no hostname and username, there are some graphical artefacts in the UI (in the account list, and in the Navigation menu)

Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: savoirfairelinux/ring-client-android#264