All Collections
Help & Troubleshooting Guides
Basic Troubleshooting Guides
Provisioning Profile Doesn't Support Push Notifications
Provisioning Profile Doesn't Support Push Notifications

How to enable push notifications in your app identifier via Apple Connect

A
Written by Ashley
Updated over a week ago

This article runs through troubleshooting steps when you face issues after setting up push notifications. For a step-by-step guide on how to enable push notifications in your app identifier via Apple Connect, check our documentation here.


Understanding the "Push Notifications" Capability Issue

When deploying an app through FlutterFlow to the Apple App Store, developers may encounter a specific error related to the "Push Notifications" capability. This article aims to illuminate this issue, explaining its cause and guiding you through the process of enabling this capability within your Apple Developer account's key identifier.

Root of the Problem

The error message "Provisioning profile doesn't support the Push Notifications capability" is presented when an app that includes push notification functionality is submitted to the App Store without completing necessary configurations. This setup is essential because the push notifications feature requires explicit permission within your Apple Developer account to function properly.

Enabling "Push Notifications" Capability

To resolve this issue, follow these steps to enable the "Push Notifications" capability for your existing app:

  1. Visit Your Apple Developer Account: Log into your Apple Developer account and navigate to the "Identifiers" section under the "Certificates, Identifiers & Profiles" area.


  2. Select Your App's Identifier: Identify the App ID associated with the app you are deploying. This step is critical as the adjustments you're about to make are specific to the app's identifier.

  3. Enable the Capability: Within your app's identifier details, find the section for enabling capabilities. Check the option for "Push Notifications." Unlike some capabilities, there's no need to alter the primary App ID or create a new key if it's your first time enabling this capability for an App ID.


  4. Save Changes: Make sure to save the changes. Even if you see UI elements suggesting further edits, enabling this feature and saving changes is enough for the initial configuration.

  5. Deploy Through FlutterFlow: With the "Push Notifications" capability now enabled for your App ID, you can deploy your app through FlutterFlow without encountering the previous error.
    ​​​

Need more help? Contact us at support@flutterflow.io.

For additional insights on deploying apps with FlutterFlow and other app development topics, check out FlutterFlow's documentation and Community.

Did this answer your question?