-
-
Notifications
You must be signed in to change notification settings - Fork 4.8k
Occasional "Missing push configuration" error #2439
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
Comments
It seems to somewhat be related to the fact that I can't get some of my subclassed
Does a before/after save request not contain its object's object's sub properties? |
Is your |
yes, its a pointer. So you mean I should first fetch the post from the DB and then get it's story? |
@royherma Yes, it would seem that you'll have to query the story separately. The good news is that you should have the ID of the object in the pointer, so should be very easy to get the proper story object using that ID. |
yeah, that won't be a problem - its more of a speed/usage thing, i.e would have been way faster if i can directly access the pointer object's properties (which are being sent from the client end). Thanks joey 👍 |
I've been able to set up parse server push notifications on my Ubuntu backend, however I seem to be running into an issue which results in the "Missing push configuration" error. I've definitely been able to send and receive push notifications at certain times, but at other times I am running into that error. I'm not changing the parse environment file, but rather only conducting changes the
main.js
cloud code file, which does seem to affect it oddly enough. I get the error both in theparse-dashboard
when trying to send to all users, and in the xcode console when running a more targeted push function using a custom cloud code method. It is here below btw:It is being called in on the client as so:
The bottom line is that I am unable to understand the relation of the error message and the
main.js
(seems to me that they should not affect one another, at least when I am using the parse dashboard to send a push and not the cloud code). Anybody run into this issue, or has an idea what exactly is happening here?Thanks!
The text was updated successfully, but these errors were encountered: