Yep. I included the parse.js library---it works for other functions just fine (Adding objects, etc.) but the push function doesn't work from Tiggzi.
Yep. I included the parse.js library---it works for other functions just fine (Adding objects, etc.) but the push function doesn't work from Tiggzi.
In the new builder, have you tried:
return "{'alert':'test'}"?
Yes. I think i've tried everything haha.
unfortunately when i configure it in the old editor--it doesn't transfer to the new editor.
Launch the app from the old builder, then using Chrome Dev. Tools see the exact request that's being sent. The compare it to the request that's being sent when you define the array in JavaScript in the new builder.
Here is the payload that worked: null /134
Oflex.messaging.messages.RemotingMessage
source operation body messageId timestamp clientId headers destination timeToLive testConnection 9https://api.parse.com/1/push post json 0 {X-Parse-Application-Id=f05Kc5hfvH5kFQr7jcgElQC9msrgdowczIhkCAPN&X-Parse-REST-API-Key=OINnIo6X6kVKQcE66S4rdO2g0GZmlgvbDXuzjaVO „U
IE39D3982-7E06-EE28-B86F-A20238F3D466 I9685C2DE-2409-D852-E1AE-558F6183BAC3
DSId I967FC8BC-461A-8AAB-D3D5-119305246AE7 DSEndpoint seam-amf 'restServiceEndpoint
This is the message from the HTML5 editor:
uri:https://api.parse.com/1/push
method:post
serviceDataType:json
contentType:json
securityContext:0
serviceSettings:0
headerParams:X-Parse-Application-Id=f05Kc5hfvH5kFQr7jcgElQC9msrgdowczIhkCAPN&X-Parse-REST-API-Key=OINnIo6X6kVKQcE66S4rdO2g0GZmlgvbDXuzjaVO
serviceParams:
Response Headersview source
I think you are looking at the request when testing from the builder. Run the app in the browser, and then see what the request is. Don't debug what's happening in the builder.
Nathan,
Were you able to get the Parse Push Notifications to work from your Tiggzi App?
If yes, then I would love to know what steps you took.
Thanks,
Eric