-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
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
problem with json push #1581
Comments
I have the similar issue, can't get the cloud code push notification to work. Using CURL works fine. but sending from cloud code getting: |
can you run the server with VERBOSE=1 and give us the logs attached to it? |
Ok, I realized the problem. The problem is, json message itself sending as an alert. When I send the json message below
LOG:
|
I'll have a look, @drew-gross isn't it a dashboard problem? The JSON should not be embedded no? |
The dashboard uses the JS SDK, just calls |
yeah I know, but the data is nested in the alert key. instead of set as the data object |
Is this not right? |
in that case: that should be:
that will prevent the double embedding:
to:
|
Sounds good |
This issue fixed with latest dashboard update. Thanks fellas! |
Check out this issue for an ideal bug report. The closer your issue report is to that one, the more likely we are to be able to help, and the more likely we will be to fix the issue quickly!
For implementation related questions or technical support, please refer to the Stack Overflow and Server Fault communities.
Make sure these boxes are checked before submitting your issue -- thanks for reporting issues back to Parse Server!
Environment Setup
Steps to reproduce
I can't send json messages via parse dashboard. I've checked http response and it seems
{result: true}
but can't push message anyway. (no problem with text messages)I didn't get any error with curl and json messages delivering smoothly.
@drew-gross told this might be a parse-server issue.
Thanks,
Logs/Trace
error: error while sending push code=101, message=Object not found.
The text was updated successfully, but these errors were encountered: