New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Server/Ticket76/Fix the "crash_report_ack" response from server #77

Open

bdfhjk opened this issue Apr 3, 2016 · 1 comment

Assignees

Labels

assigned mission critical

Milestone

Alpha version 0.2

Collaborator

bdfhjk commented Apr 3, 2016

The scope is to fix the server, that it will communicate correctly with the client communication.

The only thing that's not working correctly is a JSON response to a new crash report.

Please update the JSON response on the server to be consistent with documentation:

http://docs.dpcs.apiary.io/#reference/crashes/crash-report-collection/send-a-new-report

bdfhjk assigned hubertta

bdfhjk added assigned mission critical labels

bdfhjk added this to the Alpha version 0.2 milestone

Contributor

patrikos94 commented Apr 4, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment