-
Notifications
You must be signed in to change notification settings - Fork 16
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.
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
Upload failed #2
Comments
.../mds/log |
Thanks for updating with the logging output. That helps significantly. It looks like the client is sending an erroneous value for the procedure being used, procedure_guid': u'0'. It should actually be sending the uuid or title. This might be a bug but which client version are you using-e.g. build from the current source on Github or other? |
I tried different clients, First I tried the one from http://sana.mit.edu/mobile/download/. I tried also the ones from https://code.google.com/p/moca/downloads/list: sana-release-1.1.1.apk, sana-release-1.1.2.apk ... all of them didn't work. Now I'm trying to compile from source. |
The sana-current.apk at the link you initially used needed to be updated. Should be corrected now. When building the client, the source available in the Github sana.mobile repo is what you will want to use. Clients built from the Googlecode repo definitely won't work. |
Quick follow up comment. We are moving the documentation. The latest versions, as well as any updates, will now be available at http://dev.sanamobile.org/. |
I buillt a client from sana.mobile repo, but I'm still getting the upload failed errorr! android logs: Received from MDS:{ |
//mds/log |
If you load the fixtures in the source, sana.mds/include/mds/fixtures/ directory. |
Thanks, I manage to upload successfully. But I have one last issue, what's the currently supported version of OpenMRS, is this http://sana.mit.edu/wiki/index.php?title=OpenMRS_Configuration outdated? Because I can't view the encounter queue in openmrs. |
The supported version is OpenMRS 1.9.7. |
Now I can view the encounter queue but I'm having a problem with the diagnosis and sending SMS notification. I filled in my clickatell information but still no sms notification is being delivered, can you help me to figure out what's going wrong here. Thanks. mds logs[{"line_number": 911, "level_number": 20, "delta": "0.000s", "timestamp": 1447479829.65, "level_name": "INFO", "function_name": "notification_submit", "message": "Notification submit received", "module": "json", "filename": "json.py"}, {"line_number": 914, "level_number": 20, "delta": "0.001s", "timestamp": 1447479829.65, "level_name": "INFO", "function_name": "notification_submit", "message": "Notification submit notificationText:DX: ; Plan: test, test", "module": "json", "filename": "json.py"}, {"line_number": 914, "level_number": 20, "delta": "0.001s", "timestamp": 1447479829.65, "level_name": "INFO", "function_name": "notification_submit", "message": "Notification submit phoneIdentifier:", "module": "json", "filename": "json.py"}, {"line_number": 914, "level_number": 20, "delta": "0.001s", "timestamp": 1447479829.65, "level_name": "INFO", "function_name": "notification_submit", "message": "Notification submit caseIdentifier:SPPQHhsBlcXJukqIyiNGuK", "module": "json", "filename": "json.py"}, {"line_number": 914, "level_number": 20, "delta": "0.002s", "timestamp": 1447479829.65, "level_name": "INFO", "function_name": "notification_submit", "message": "Notification submit patientIdentifier:635872", "module": "json", "filename": "json.py"}] Tomcat logsINFO - LoggingAdvice.invoke(117) |2015-11-14 00:42:47,480| In method EncounterService.saveEncounter. Arguments: Encounter=Encounter: [(no ID) Sat Nov 14 00:42:47 EST 2015 ADULTINITIAL Unknown Location 5 Skin num Obs: [] num Orders: 0 ], |
I was able to reproduce the issue but will need to do a bit more work to isolate the root cause. Seems to be an issue with null complex data getting returned for an observation. |
Hi Eric,
have you manage to solve the issue.
…On Sun, Nov 15, 2015 at 10:25 PM, Eric Winkler ***@***.***> wrote:
I was able to reproduce the issue but will need to do a bit more work to
isolate the root cause. Seems to be an issue with null complex data getting
returned for an observation.
—
Reply to this email directly or view it on GitHub
<#2 (comment)>.
|
I just finished setting up the mds, openmrs and sana. I followed the instructions in the INSTALL file but I can't get the sana android client to upload procedures, its saying upload failed all the time. I tried to check the tomcat and mds logs but I can't figure out how to fix this. Can somebody help me fix this.
Thanks.
The text was updated successfully, but these errors were encountered: