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
  • #298

Closed
Open
Opened Oct 05, 2016 by RingBot@RingBotOwner

Android: crash when trying to call a ringID with all RING accounts dissabled

Issue generated from Tuleap's migration script. Originally submitted by: Stepan Salenikovich (ssalenik)

If all RING accounts are dissabled, entering a new RingID and trying to call it or calling an already used RingID will cause the application to crash. I don't have the logs, but with Adrien we saw it was a nullptr issue due to trying to make a call with a dissabled account. Seems like its an issue possibly on both the client and daemon side, as the client shouldn't try to make a call with a dissabled account and neither should the daemon.
 

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