Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • A AndroidAsync
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 333
    • Issues 333
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 19
    • Merge requests 19
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Koushik Dutta
  • AndroidAsync
  • Merge requests
  • !378

Handle cases where the transport becomes null during the socketIO heartbeat

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Administrator requested to merge github/fork/respoke/issue-295-null-object into master Aug 01, 2015
  • Overview 2
  • Commits 1
  • Pipelines 0
  • Changes 1

Created by: jznadams

This fixes issue https://github.com/koush/AndroidAsync/issues/295, A crash which I have been seeing in 5% of all sessions of my Android application using this library. During certain network conditions, the transport reference can become null during the "send" operation in the heartbeat. Simply checking for null afterwards prevents the crash.

Assignee
Assign to
Reviewers
Request review from
Time tracking
Source branch: github/fork/respoke/issue-295-null-object