Guide · Notifications

Push notifications for users in Syria.

Whichever service you send from, an iPhone notification passes through Apple's APNs, and the default Android route passes through Google Play services. Here is what each layer needs, what the official pages say about Syria, and how to build so a late or lost message does not break your app.

Updated 18 November 2026Sources checked 16 November 2026Reviewed by Eng. Hasan Kassas

The short answer

On Android the default route is Firebase Cloud Messaging (FCM), and it reaches a phone only through Google Play services. Google's FCM client setup asks for Android 7.0 or later with the Google Play Store app installed, and the same page says your app does not have to be distributed through Google Play. The Firebase terms, and the Google APIs Terms that govern FCM, name no country. As of 16 November 2026 we found no Google page saying FCM is available in Syria, and none saying it is blocked.

On iPhone and iPad, every remote notification travels through Apple Push Notification service (APNs), even when you send it with FCM or another provider. Push needs a paid Apple Developer Program membership; free developer accounts cannot switch it on. Huawei Push Kit, Huawei's own service for devices with HMS Core, does not include Syria on its list of supported countries and regions.

Hosted services such as OneSignal, Expo, Pusher Beams, Amazon SNS and Azure Notification Hubs sit on top of FCM and APNs, so none of them removes either dependency. Whatever you choose, treat a push as a hint that something changed, and keep the real message in an in-app inbox that the app fetches when it opens.

As read on 16 November 2026

The layers that carry a notification to the phone

What the phone needsWhat the official pages say
FCM (Android)Android 7.0 or later with Google Play services and the Play Store appTerms name no country; no Google page says FCM is available or unavailable for Syria
APNs (iPhone, iPad)The device's own connection to APNs; the sender needs a paid Apple Developer Program membershipNo country restriction on the APNs pages; Apple says enrolment may not be supported in some regions
Huawei Push KitHMS Core 3.0.0 or later (Huawei devices, or other Android 4.4 to 13)Syria is not on the Supported Countries/Regions list, last updated 18 July 2023
UnifiedPushA distributor app the user installs, such as ntfyOpen standard for Android that you can self-host; does not run on iOS
Android

FCM depends on Google Play services

Google's FCM architecture page says the Android transport layer works only on approved Android devices with Google Play services. Those services belong to Google Mobile Services, which Google says is not part of the open-source Android project, is available only under a licence from Google, and varies by country. The per-country list is open to device-maker partners only, and we found no official figure for how many phones in Syria carry Google Play services.

Two practical points follow. First, Google states that you are not limited to the Play Store for distributing an app that uses FCM, which matters because Syria is not on Google Play's developer registration list (see the app store guide). Second, the app should check at runtime for a compatible version of Google Play services and switch to a fallback when it is missing, rather than registering for messages that will never come.

On the server, the FCM HTTP v1 API is authorised with a short-lived OAuth 2.0 token derived from a service account; the Firebase Admin SDK handles this for you. If the Firebase project sits on a paid Google Cloud billing account, the Google Cloud Terms also bar use that breaks export control laws (EAR, OFAC sanctions and ITAR), again without naming a country. Google's Workspace help says Google restricts some of its business services in Syria and does not say whether Firebase is one of them; our hosting guide covers what that means for the rest of your stack.

iPhone

On iOS, everything goes through APNs

Apple's capabilities table lists push notifications for members of the paid Apple Developer Program and the Enterprise Program, and not for free accounts. Apple also says enrolment may not be supported in certain regions, for example because of sanctions; the app store guide covers what that means for a team in Syria. None of the APNs pages we read mentions a country restriction.

Setup has three parts: turn on the Push Notifications capability in Xcode, enable push for the App ID in your developer account, and have the app register at every launch so it gets a device token to send to your server. For sending, an Account Holder or Admin creates an APNs authentication key. It downloads once as a .p8 file, works for development and production, never expires and can be revoked, so store it like a password. Your server signs a token with it and refreshes that token no more than once every 20 minutes and no less than once every 60.

If you send through FCM, Huawei or any hosted service, the message still reaches iOS through APNs, and Google notes that messages handed to another platform's layer may fall under that platform's terms rather than FCM's. Apple documents one alternative, Local Push Connectivity, but it runs only on networks you configure in advance, such as a particular Wi-Fi network, and needs a special entitlement from Apple. It does nothing for users on mobile data.

Read on 16 November 2026

Hosted push services and what their terms say

What the terms say about countriesSends through
OneSignalSanctions clause about restricted-party lists, plus a separate clause on Russia and Ukraine (Crimea); Syria is not named (updated 12 Jun 2024)FCM and APNs
Expo push serviceNo export-control or country clause (effective 2 Nov 2026)FCM and APNs; Expo says you can send to them directly instead
Pusher BeamsPusher's terms link leads to Bird's general terms: each party must follow US, UN, EU and UK sanctions and export laws; no country named (updated 21 Nov 2024)FCM, APNs and web push
Amazon SNSAWS Customer Agreement trade-compliance clause on export law and restricted-party lists; no country named (updated 29 Oct 2026)FCM, APNs, ADM, Baidu and WNS
Azure Notification HubsSyria is not on Azure's list of the 140 countries and regions where it is commercially available (checked 16 Nov 2026), and Microsoft's undated export FAQ says its cloud services may not be accessed from some countriesAPNs, FCM and WNS
No Google services

Android phones without Google Play services

A phone without Google Play services cannot receive FCM. These are the documented options, and each comes with limits:

  • Huawei Push Kit runs on Huawei devices with EMUI 3.0 or later, and on other Android 4.4 to 13 devices that have HMS Core installed. Huawei's product page claims more than 200 countries and regions, but its own country list leaves out Syria while listing Lebanon, Jordan, Iraq and Türkiye, and Huawei does not say whether a Huawei phone in Syria receives messages.
  • UnifiedPush is an open, decentralised standard in which the user picks the push service. It works on Android without Google services and can be self-hosted, but every user has to install a distributor app, and your server has to speak Web Push (RFC 8030, 8291 and 8292, per its Android spec AND_3.1.0).
  • ntfy is a push server you can host yourself. Its F-Droid build contains no Firebase and keeps a foreground service running for instant delivery, which the user sees as a permanent notification.
  • MQTT is an OASIS-standard publish and subscribe protocol (version 5.0, 7 March 2019) built for a small code footprint and low bandwidth, with persistent sessions for unreliable networks. It is only a transport: an app that holds its own MQTT connection is still subject to Doze and App Standby.
  • Any app that keeps its own connection meets Android's limits. Apps in the Rare and Restricted standby buckets lose background network access, and for apps targeting Android 15, dataSync foreground services may run only 6 hours in any 24 in the background. Android also defines a remoteMessaging foreground service type, but Google does not say which type a push socket should use.
  • Google accepts a battery optimisation exemption for chat, messaging and calling apps that cannot use FCM because they depend on another messaging service. Google Play policy forbids asking users for it directly unless the app's core function suffers, so do not reach for it by default.
  • None of these reach iPhones. The UnifiedPush FAQ says a distributor cannot run on iOS, and a self-hosted ntfy server has to pass iOS messages through an upstream server that is connected to APNs.
Delays

Why notifications arrive late, or not at all

01
Doze holds normal priority

On Android 6.0 and later, a phone left idle enters Doze: network access stops and background jobs wait for a maintenance window. Normal-priority FCM messages, the default, may wait until Doze ends.

02
High priority has to be earned

A high-priority message can wake a sleeping phone. If those messages do not produce a visible notification, FCM may lower them to normal, judging each app install on 7 days of behaviour.

03
Android 13 changed the rule

Since Android 13 the standby bucket no longer caps high-priority messages. Instead the system downgrades them when an app keeps sending high priority without showing anything.

04
Notifications switched off

When a user has disabled notifications for your app, FCM delivers its messages at lower priority.

05
Silent pushes on iOS are throttled

Apple treats background pushes as low priority with no delivery guarantee. It keeps only the newest when several arrive, drops it if the user force-quit the app, gives the app 30 seconds to run, and advises no more than two or three an hour.

06
A server call before display

Google warns that calling your server before showing a notification is risky on high-latency networks. Put the text in the message itself and use WorkManager for any extra sync.

Network

Ports, firewalls and VPNs

  • Android phones reach FCM on TCP ports 5228, 5229, 5230 and 443. The FCM protocol cannot pass through a proxy, and firewalls should keep idle connections on 5228 to 5230 open for at least 30 minutes.
  • Apple devices connect to APNs on TCP 5223 and fall back to 443. Your server sends to APNs over HTTP/2 with TLS 1.2 or later, on port 443 or 2197.
  • Huawei Push Kit needs ports 443 and 5223 open, caps message content at 4 KB, and caches messages for devices that are offline.
  • Google's FCM network page says that in some cases VPNs break the long-lived push connection, which shows up as missed or delayed messages and extra battery drain.
  • When a user reports that notifications stop on one network but not on another, these ports are the first thing to check.
Step by step

Notifications that survive Syrian networks

  1. Sort every message by urgency

    List each notification the app sends and mark it: the user must see it now, it can wait, or it only refreshes data. Only the first group gets high priority, and each of those must show a visible notification.

  2. Put the content in the payload

    Send the text, and the IDs the app needs to open the right screen, inside the message itself, so the phone can display it without asking your server first. If the text mixes Arabic and English, isolate the inserted part as our RTL guide shows.

  3. Give each type an expiry

    FCM keeps an undeliverable message for up to 28 days by default (the lifespan field takes 0 to 2,419,200 seconds on Android and web), and APNs for up to 30 days through the apns-expiration header. A ride offer is worthless after a few minutes, so give short-lived messages a short lifespan instead of letting them land a day late.

  4. Keep an in-app inbox

    Store every notification on your server and let the app fetch the list whenever it opens. APNs stores only one notification per app, so a phone that was off for a day can miss most of what you sent; the inbox closes that gap. Our guide to building for weak internet covers the sync side.

  5. Detect phones without Google Play services

    Check for a compatible Google Play services version at runtime. Where it is missing, lean on the inbox each time the app opens, and offer UnifiedPush to users willing to install a distributor.

  6. Guard the keys

    Keep the APNs .p8 key and the Firebase service account on the server only, never inside the app. The .p8 file downloads once; if it leaks, revoke it and create another.

  7. Test on real phones and networks

    Send to Android and iPhone on Syriatel and MTN, on mobile data and Wi-Fi, with the phone idle long enough to enter Doze, with the app force-quit, and after a day switched off. Record every send on your server and note, per platform, which ones the test phones actually showed.

  8. Keep critical flows off push alone

    Login codes, payment confirmations and safety alerts need a second path. For one-time codes, see SMS verification for Syrian numbers.

FAQ

Common questions

Google does not say either way. The Firebase terms and the Google APIs Terms that cover FCM name no country, and as of 16 November 2026 we found no Google page listing Syria as supported or blocked. FCM also needs Google Play services on the phone, so test with real devices on Syrian networks before you depend on it.

Sources

Where these facts come from

  1. Google Terms of Service for Firebase Services (FCM is governed by the Google APIs Terms)Google (Firebase) · modified 24 Sep 2026
  2. Google APIs Terms of ServiceGoogle for Developers · modified 9 Nov 2021
  3. Google Cloud Terms of Service (definition of Export Control Laws)Google Cloud · modified 12 Oct 2026
  4. FCM architectural overview (Android transport layer, platform terms)Firebase documentation · updated 12 Nov 2026
  5. Set up an FCM client app on Android (Android 7.0+, Play Store app, distribution)Firebase documentation · updated 12 Nov 2026
  6. Authorize FCM HTTP v1 send requestsFirebase documentation · updated 12 Nov 2026
  7. FCM network configuration (ports, proxies, VPNs)Firebase documentation · updated 12 Nov 2026
  8. Setting the lifespan of an FCM messageFirebase documentation · updated 12 Nov 2026
  9. FCM Android message priorityFirebase documentation · updated 12 Nov 2026
  10. Google Mobile Services (licensing, availability by country)Google (Android) · accessed 16 Nov 2026
  11. Google Workspace availability by country (restricted business services)Google Workspace Admin Help · updated 10 Nov 2026
  12. Supported capabilities (iOS): push notifications by membership typeApple Developer, Account Help · accessed 16 Nov 2026
  13. Apple Developer Program enrollment helpApple Developer · accessed 15 Nov 2026
  14. Registering your app with APNsApple Developer Documentation · accessed 16 Nov 2026
  15. Communicate with APNs using authentication tokensApple Developer, Account Help · accessed 16 Nov 2026
  16. Create a private keyApple Developer, Account Help · accessed 16 Nov 2026
  17. Establishing a token-based connection to APNsApple Developer Documentation · accessed 16 Nov 2026
  18. Sending notification requests to APNs (storage, priority)Apple Developer Documentation · accessed 16 Nov 2026
  19. Pushing background updates to your appApple Developer Documentation · accessed 16 Nov 2026
  20. If your Apple devices aren't getting Apple push notifications (ports)Apple Support · 22 Aug 2023
  21. Local Push ConnectivityApple Developer Documentation · accessed 16 Nov 2026
  22. Push Kit: Supported Countries/RegionsHUAWEI Developers · updated 18 Jul 2023
  23. Push Kit product page (200+ countries and regions)HUAWEI Developers · accessed 16 Nov 2026
  24. Push Kit: Service Introduction (supported devices, iOS SDK)HUAWEI Developers · updated 18 Jul 2023
  25. Push Kit: Restrictions (4 KB limit, ports)HUAWEI Developers · updated 21 Oct 2024
  26. OneSignal Terms of Service (sanctions clause)OneSignal · updated 12 Jun 2024
  27. Expo Terms of ServiceExpo · effective 2 Nov 2026
  28. Expo: send notifications with FCM and APNs directlyExpo documentation · accessed 16 Nov 2026
  29. Bird terms (target of Pusher's terms-of-service link), clause 7.4Bird (owner of Pusher) · updated 21 Nov 2024
  30. Pusher Beams product pagePusher · accessed 16 Nov 2026
  31. AWS Customer Agreement, section 11.6 (trade compliance)Amazon Web Services · updated 29 Oct 2026
  32. AWS Service Terms, section 11 (Amazon SNS fees)Amazon Web Services · updated 5 Nov 2026
  33. Amazon SNS mobile push (ADM, APNs, Baidu, FCM, WNS)AWS Documentation · accessed 16 Nov 2026
  34. Microsoft exporting FAQMicrosoft · undated, accessed 16 Nov 2026
  35. Azure free account FAQ (countries and regions where Azure is commercially available)Microsoft Azure · accessed 16 Nov 2026
  36. Azure Notification Hubs overviewMicrosoft Learn · accessed 16 Nov 2026
  37. UnifiedPush project siteUnifiedPush · accessed 16 Nov 2026
  38. UnifiedPush FAQ (distributor apps, Web Push servers, iOS)UnifiedPush · accessed 16 Nov 2026
  39. UnifiedPush Android specification AND_3.1.0UnifiedPush · accessed 16 Nov 2026
  40. ntfy: subscribe from your phone (F-Droid build, instant delivery)ntfy documentation · accessed 16 Nov 2026
  41. ntfy configuration: iOS instant notifications via an upstream serverntfy documentation · accessed 16 Nov 2026
  42. MQTT Version 5.0, OASIS StandardOASIS · 7 Mar 2019
  43. Optimize for Doze and App StandbyAndroid Developers · updated 22 Oct 2026
  44. Power management resource limits (standby buckets, Android 13 change)Android Developers · updated 19 May 2026
  45. Foreground service timeouts (Android 15)Android Developers · updated 28 Oct 2026
  46. Foreground service types (remoteMessaging)Android Developers · updated 28 Oct 2026

Checked 16 November 2026 against each provider's own pages. Terms, country lists and Android battery rules change, so read them again before launch. This guide reports what vendors publish and is not legal advice.

Adding notifications to a Syrian app?

Tell us what your app needs to tell its users. We will help you decide what goes by push, what waits in the inbox, and how to test both.