dhis2-users team mailing list archive

[Pamod Amarakoon <pamodm@xxxxxxxxx>]

The issue still persists on latest build. Any suggestion on how to fix this.

On Sat, Jul 9, 2016 at 1:16 PM, Pamod Amarakoon <pamodm@xxxxxxxxx> wrote:

> Dear All,
>
> We are developing an Android app for a specific tracker use case. It was
> initially developed targeting a DHIS 2.22 instance. The app used web API to
> communicate with the DHIS2 instance which mainly involved creating TEIs,
> enrolling them to a program, updating attributes, adding, updating and
> deleting events.
>
> The version was working fine without any major issue. We recently tested
> the App on a 2.23 instance.
>
> While testing we noted that we are getting "405-Method not allowed"
> response when trying to delete an event using mobile internet. We used
> following API which worked fine on mobile internet in 2.22
>
> http://xxx.xxx.xxx.xxx/api/events/tRYeBJR51yW
>
> But we don't get this error while performing the same delete event using
> WiFi on the Android mobile device.
>
> Even upgrading to the latest 2.23 didn't fix this error. Any idea on
> what's causing this error and how to fix this.
>
> Thank you
>
> --
> Regards,
> Pamod Amarakoon
>
> Confidentiality Notice: the information contained in this email and any
> attachments may be legally privileged and confidential. If you are not an
> intended recipient, you are hereby notified that any dissemination,
> distribution, or copying of this e-mail is strictly prohibited. If you have
> received this e-mail in error, please notify the sender and permanently
> delete the e-mail and any attachments immediately. You should not retain,
> copy or use this e-mail or any attachments for any purpose, nor disclose
> all or any part of the contents to any other person.
>
>
>
>


-- 
Regards,
Pamod Amarakoon

Confidentiality Notice: the information contained in this email and any
attachments may be legally privileged and confidential. If you are not an
intended recipient, you are hereby notified that any dissemination,
distribution, or copying of this e-mail is strictly prohibited. If you have
received this e-mail in error, please notify the sender and permanently
delete the e-mail and any attachments immediately. You should not retain,
copy or use this e-mail or any attachments for any purpose, nor disclose
all or any part of the contents to any other person.