Overview

When targeting Android 14 with the Signed Call Android SDK, Google Play Console now mandates a declaration for using the Full-Screen Intent (FSI) permission. Unlike previous versions of Android, where this permission was automatically granted, you must explicitly declare the usage before submitting the app to the Play Store. The Google team then evaluates your declaration and determines whether to approve or reject the app build.

For more information, refer to Full-Screen Intent Limits.

FSI Permission Usage

The Signed Call Android SDK utilizes the FSI permission to display full-screen notifications for incoming VoIP calls when the app is not running in the foreground, ensuring a user experience comparable to other VoIP-capable apps.

Methods to Declare FSI Permission Usage

The following are the two ways to declare FSI Permission Usage:

• Method 1: Opt for Making and receiving calls category
• Method 2: Opt for Other category

Opt for Making and Receiving Calls Category

To declare FSI Permission Usage using the Making and receiving calls option:

1. Select the Making and receiving calls option in the About your app section.
2. When prompted, choose ‘Yes’ for Install behavior.
3. Save your changes and submit them for review.

📘

Best Practices

• If you are planning to release your app with the Signed Call SDK, CleverTap recommends creating a release in the internal test track with the build at least one week before the planned release date, and follow the steps listed in this section.
• If your application is rejected, you can appeal the decision.

Opt for Other Category

To declare FSI Permission Usage using the Other option:

1. Select Other option from the About your app section.
2. Save your changes and submit them for review. The Google team usually takes about 24 hours to review the changes.

📘

Best Practices

• If your app release is time-sensitive and you want to avoid potential rejections, opt for Option 2.
• After the release is live in production, you can change the Full-screen intent permission preferences anytime by navigating to App Content > Actioned Declarations > Full-screen intent.

App Rejection

If the Google team cannot verify that the FSI permission is used for the VoIP call feature, they may reject your build. In such cases, you will receive an app rejection email. The following image represents a Sample Rejection Email.

Address App Rejection

To address the app rejection, follow the steps listed in the rejection email:

1. Create a Recording
   Create a video demonstrating the exact process of receiving a call, highlighting the Signed Call functionality. Clearly indicate the part of the app where the VoIP call is initiated. This will help the Google team understand how the Full-screen Intent permission is utilized for the VoIP feature.
2. Submit the Recording
   Provide the video link along with a brief description of the flow shown in the video. Explain how revoking the Full-screen Intent permission could negatively impact your users. Submit this information in response to the rejection email.
3. Google Team Review
   The Google team will review your submission. If they approve your request, follow Step 2 included in the rejection email, to upload the build and send it for review.

SDK Behavior Demonstration

• Video Demonstrating SDK Behavior When Permission is Granted
• Video Demonstrating SDK Behavior When Permission is Not Granted