parse-community / parse-community/parse-server-push-adapter

Unable to send Push Message to IOS

Open
#194 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
96
Forks
108
PR merge metrics
No merged PRs in 30d

Description

Hi all, unfortunately I am not able to send push notifications via the dashboard. it shows the following error

verbose: Current clients %d verbose: Current subscriptions %d verbose: REQUEST for [POST] /parse/push: { "data": { "alert": "jujuuu" }, "where": {} } {"body":{"data":{"alert":"jujuuu"},"where":{}},"headers":{"accept":"*/*","accept-encoding":"gzip, deflate, br","accept-language":"de-DE,de;q=0.9","connection":"keep-alive","content-length":"208","content-type":"text/plain","host":"192.168.12.1:1339","origin":"http://192.168.12.1:4040","referer":"http://192.168.12.1:4040/","user-agent":"Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/15.0 Safari/605.1.15"},"method":"POST","url":"/parse/push"} verbose: RESPONSE from [POST] /parse/push: { "headers": { "X-Parse-Push-Status-Id": "j48Njcz937" }, "response": { "result": true } } {"result":{"headers":{"X-Parse-Push-Status-Id":"j48Njcz937"},"response":{"result":true}}} verbose: _PushStatus j48Njcz937: sending push to installations with %d batches verbose: Sending push to 1 (node:23221) UnhandledPromiseRejectionWarning: Error: ca md too weak at Object.createSecureContext (_tls_common.js:273:19) at Object.connect (_tls_wrap.js:1593:48) at Object.connect (internal/http2/core.js:3138:22) at /root/node_modules/@parse/node-apn/lib/client.js:122:44 at processTicksAndRejections (internal/process/task_queues.js:97:5) at async Promise.all (index 0) at async Promise.all (index 0) at async Promise.all (index 0) (node:23221) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict(see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the /parse/push flow and the @parse/node-apn/lib/client.js location shown in the stack trace; investigate the Node TLS "ca md too weak" error while sending the iOS push. Done means the dashboard push completes without the TLS error and the notification is delivered.

Written by the indexing model from the issue text.

Assessment

Tech stack
ios, javascript, node.js
Domain
backend, mobile-dev
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.