*Details:* If you make a valid DELETE REST call, then HTTPClient's onload method is not called.
*Notes:*
* This issue is not reproducible on Android
* Even though the onload method is not being called, the DELETE request still goes through
* Other Http REST calls (e.g. POST) are triggering HTTPClient's onload method
*Steps to reproduce:*
Create a Titanium *and* Arrow project from Appc Studio
In the Titanium project, replace the app.js with the attached app.js
Next, select the Arrow project and run *Local Arrow Server*
In the console, copy the port number after http://127.0.0.1:
In the Titanium project's app.js, replace URL_PREFIX
(line 2) with your machine's ip address and Arrow project's port number e.g. http://172.16.3.129:62756
In the same app.js file, replace API_KEY
(line 8) with your Arrow project's apikey_development
; /conf/default.js
Next, install your Titanium project to an iOS device; make sure the device is on the same wifi network as your machine
Open the app and press 1. Create
; wait for *CREATED MONKEY LORD* alert
Next, press 2. DELETE
*Actual:* The onload method is never called i.e. *DATA DELETED* alert is never triggered in the onload method.
*Expected:* The onload method should be called if a valid DELETE Http REST called is made.
Not currently scheduling this for a release, but let me know if you feel otherwise.
Closing issue for now. I tested the requests using an open REST testing-service:
The onLoad is triggered and the response is 200 (not 204, because there is response). Please validate to make sure you see the same. I would suspect that something was wrong on the arrow-side.