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.
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.
| What the phone needs | What the official pages say | |
|---|---|---|
| FCM (Android) | Android 7.0 or later with Google Play services and the Play Store app | Terms 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 membership | No country restriction on the APNs pages; Apple says enrolment may not be supported in some regions |
| Huawei Push Kit | HMS 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 |
| UnifiedPush | A distributor app the user installs, such as ntfy | Open standard for Android that you can self-host; does not run on iOS |
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.
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.
| What the terms say about countries | Sends through | |
|---|---|---|
| OneSignal | Sanctions 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 service | No export-control or country clause (effective 2 Nov 2026) | FCM and APNs; Expo says you can send to them directly instead |
| Pusher Beams | Pusher'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 SNS | AWS 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 Hubs | Syria 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 countries | APNs, FCM and WNS |
A phone without Google Play services cannot receive FCM. These are the documented options, and each comes with limits:
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.
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.
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.
When a user has disabled notifications for your app, FCM delivers its messages at lower priority.
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.
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.
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.
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.
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.
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.
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.
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.
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.
Login codes, payment confirmations and safety alerts need a second path. For one-time codes, see SMS verification for Syrian numbers.
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.
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.
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.