fix: route native APNs tokens directly via apn package in push-send-q…

[ManAnRuck]

…ueued

iOS >= 1.5.5 stores raw APNs device tokens (64-char hex) in the DB. Firebase Admin SDK rejects these as invalid FCM registration tokens.

Detect token format at send time:

• 64-char hex → sendPushViaApns() using the apn package (already installed)
• all others → sendPushViaFcm() via Firebase Admin SDK (unchanged)

APNs provider uses existing credentials: APPLE_APN_KEY, APPLE_APN_KEY_ID, APPLE_TEAMID (already in push-notifications-secrets) and APN_TOPIC (already in push-notifications-config).

Pullrequest

Issues

• None

Checklist

• None

Repositories Affected

• bundestag.io
• bundestag.io-admin
• client
• democracy-app.de
• democracy-app.de-api
• democracy-deutschland.de
• docu
• elasticsearch
• None

How2Test

• None

Todo

• None

[Copilot]

Pull request overview

This PR updates the push-send-queued cron job to detect raw APNs device tokens (64-char hex) at send time and route them through APNs (via the apn package) instead of Firebase Admin SDK, which rejects those tokens.

Changes:

• Add APNs provider initialization from APPLE_APN_KEY, APPLE_APN_KEY_ID, and APPLE_TEAMID.
• Split push sending into sendPushViaApns() and sendPushViaFcm(), selecting based on token format.
• Shut down the APNs provider before process exit.

Comments suppressed due to low confidence (2)

services/cron-jobs/push-send-queued/src/index.ts:50

• notification.topic falls back to an empty string when APN_TOPIC is unset. APNs requires a valid topic (bundle id); sending with '' will cause pushes to fail. Consider validating process.env.APN_TOPIC (and throwing a clear config error) before attempting to send via APNs, rather than defaulting to an empty string.

  notification.topic = process.env.APN_TOPIC ?? '';
  notification.payload = { data: { type, action: type, category, title, message, procedureId: procedureIds[0] } };

services/cron-jobs/push-send-queued/src/index.ts:140

• apnsProvider?.shutdown() only runs after await start() completes successfully. If start() throws/rejects, the APNs provider can keep sockets open and prevent the process from terminating cleanly. Wrap the main body in a try/finally so shutdown() is always executed before exiting.

(async () => {
  await mongoConnect();
  console.log("outstanding push's", await PushNotificationModel.countDocuments({ sent: false }));
  await start();
  apnsProvider?.shutdown();
  process.exit(0);