Fixing Text Wrap Problems in Power Apps: A Troubleshooting Guide

Table of Contents

This article is designed to assist you in resolving common problems encountered when utilizing the wrap feature within Microsoft Power Apps. The wrap functionality allows you to package your canvas apps as native mobile applications for distribution. Understanding potential issues and their solutions is crucial for a smooth app deployment process. Let’s explore some of the most frequently reported challenges and their corresponding troubleshooting steps.

Issue 1 - Wrap Build is Failing¶

Encountering a failed wrap build can be a frustrating roadblock. Several factors can contribute to this issue. To effectively diagnose and rectify the problem, a systematic approach is recommended. Let’s examine the essential steps to take when your wrap build process fails.

Step 1: Verify that your images are in PNG format¶

One of the most common culprits for wrap build failures is incorrect image format. The wrap feature in Power Apps specifically requires images to be in PNG (Portable Network Graphics) format. Using images in any other format, such as JPEG or GIF, will invariably lead to build failure. This is due to the specific processing and optimization steps involved in creating the mobile app packages.

To resolve this, meticulously check all images incorporated into your Power App. Ensure that each image file is indeed in PNG format. If you find images in other formats, you must convert them to PNG. Utilize readily available image converter tools or software to save your images as .png files. Alternatively, ensure that your original image source files are in PNG format before incorporating them into your Power App.

Important Note: Simply renaming an image file extension from .jpeg or another format to .png will not magically transform the image into PNG format. This action only changes the file extension, not the underlying image data. You must use a proper image conversion process to ensure the image data itself is converted to the PNG format.

Step 2: Verify that your App Center is correctly configured¶

Proper configuration of your App Center connection is paramount for successful wrap builds. Your App Center link must be established as an app within an organization, rather than a standalone app. This organizational structure is essential for managing the build and distribution processes effectively.

When setting up your App Center within the wrap wizard, ensure you are creating a new organization if one doesn’t already exist for your app projects. The wrap wizard interface provides clear steps for creating a new organization during the configuration process. This organizational context is crucial for App Center to correctly handle the build and deployment pipeline for your wrapped mobile app. Refer to the Power Apps documentation for detailed guidance on creating and configuring App Center organizations for wrap projects.

Step 3: Verify that your key vault configuration is correct¶

Azure Key Vault plays a critical role in securing and managing the certificates and secrets required for code signing your wrapped mobile applications. Incorrect key vault configuration is another common cause of wrap build failures. Therefore, meticulous verification of your key vault setup is essential.

Firstly, confirm that an Azure service principal has been created and that the service principal role is correctly assigned. This service principal grants Power Apps wrap the necessary permissions to access your key vault securely. Refer to the Power Apps documentation for detailed steps on creating a service principal and assigning the appropriate roles for wrap functionality.

Secondly, meticulously verify that your key vault contains all the necessary certificates, secrets, and tags specific to your target platforms, whether iOS, Android, or both. The requirements differ slightly depending on the platform:

• iOS: Requires two tags, one certificate, and one secret within the key vault. These are essential for the iOS code signing process and provisioning profile management.
• Android: Requires one tag and one certificate in the key vault. These elements are needed for generating the Android keystore and signing the application package.

Double-check that all these components are present, correctly configured, and associated with the appropriate tags within your Azure Key Vault. Refer to the Power Apps documentation for detailed guidance on setting up your Azure key vault for wrap functionality, including certificate and secret management.

Step 4: Try again if you have all the proper configurations¶

After diligently verifying and rectifying all the configurations mentioned in the previous steps, it’s time to retry the wrap build process. It’s often the case that addressing one or more of these configuration issues will resolve the build failure.

If, however, your wrap build continues to fail even after confirming that all configurations are properly set, it indicates a potentially different underlying issue. In such scenarios, it’s advisable to consult the “Other issues in wrap for Power Apps” section of this article. This section provides guidance on reporting more complex or persistent issues and gathering necessary information for support troubleshooting.

Issue 2 - Wrap button is disabled for my app¶

If you notice that the “Wrap” button is unexpectedly disabled for your Power App, it’s usually related to user permissions. The wrap functionality in Power Apps is restricted to users with edit permissions for the specific app they intend to wrap. This permission requirement is in place to ensure that only authorized app makers can create wrapped versions of applications.

To resolve this, verify your permission level for the app in question. Ensure that you possess edit permissions to the Power App you are attempting to wrap. If you only have view or run permissions, the wrap button will remain disabled. Request edit permissions from the app owner or administrator if needed. Once you have the necessary edit permissions, the wrap button should become enabled, allowing you to proceed with the wrapping process.

Issue 3 - Can’t save my project or trigger a wrap build¶

Encountering difficulties in saving your wrap project configurations or triggering a build can stem from a couple of common scenarios. Let’s explore the troubleshooting steps for these situations.

To address issues with saving or building, consider the following actions:

• Update to the latest wrap solution version: Ensure that you are utilizing the most recent version of the wrap solution within your Power Apps environment. Outdated solutions might contain bugs or compatibility issues that could hinder saving or building. Check for available updates and install the latest version.
• Ensure no UI validation errors: Before attempting to save or initiate a build, carefully review the wrap project interface for any UI validation errors. These errors are typically indicated by visual cues, such as red markings or error messages within the wrap wizard. Address any reported validation errors. Common validation errors might include missing required fields, incorrect data formats, or conflicting configurations. Resolving these UI validation errors is crucial for enabling the Save and Build submission processes.

By updating your wrap solution and resolving any UI validation errors, you should be able to successfully save your wrap project and trigger the build process.

Issue 4 - Can’t install a wrapped mobile app on a device¶

Successfully building a wrapped mobile app is only the first step. You might encounter challenges when attempting to install the wrapped app on a mobile device. Installation failures are often related to code signing and device compatibility.

To troubleshoot installation issues, consider the following:

• Verify application signing: Ensure that you have properly signed the outputted application package. Code signing is a critical security measure that verifies the app’s authenticity and integrity. Unsigned applications may be blocked by mobile operating systems for security reasons. You can sign your application package using either of the following methods:

  • Key Vault Configuration: Configure an Azure Key Vault and provide its details during the build trigger time within the wrap wizard. This automates the signing process using certificates and secrets stored in your key vault.
  • Manual Signing: Alternatively, you can perform manual code signing after the build process is complete, using platform-specific code signing tools and procedures.

  Refer to the Power Apps documentation for detailed guides on both automated and manual code signing for iOS and Android platforms.

• Verify device minimum requirements: Confirm that your target mobile device meets the minimum software and device requirements specified for wrapped Power Apps. Wrapped apps may have dependencies on specific operating system versions or hardware capabilities. Ensure your device meets these prerequisites. Consult the Power Apps documentation for the detailed list of software and device requirements for wrapped applications.

By ensuring proper application signing and verifying device compatibility, you should be able to successfully install your wrapped mobile app on target devices.

Issue 5 - Can’t sign in to a wrapped mobile app or can’t see data¶

After successfully installing your wrapped mobile app, you might encounter issues with user sign-in or data access within the app. Sign-in problems and data visibility issues often point to configuration problems with Microsoft Entra ID (formerly Azure Active Directory) and API permissions.

If you experience sign-in or data access problems, meticulously verify the following aspects of your Microsoft Entra ID and app configurations:

• Microsoft Entra app configuration: Confirm that your Microsoft Entra app registration is correctly configured. The app registration in Entra ID is essential for authenticating users and authorizing access to resources. Ensure all necessary settings, such as redirect URIs and authentication protocols, are properly configured in your Entra app registration.
• API Permissions: Verify that all required API permissions for your app have been added correctly to your Microsoft Entra app registration. Wrapped Power Apps often need to access various Microsoft services or external APIs. Granting the necessary API permissions ensures that the app can securely access these resources on behalf of the user. Refer to the Power Apps documentation for guidance on viewing and configuring API permissions within your Entra app registration.
• Add-AdminAllowedThirdPartyApps script: Ensure that the Add-AdminAllowedThirdPartyApps PowerShell script has been executed successfully within your Power Apps environment. This script is sometimes required to allow registered apps, like your wrapped app, to function correctly within the Power Apps ecosystem. Check the execution logs or status of this script to confirm successful completion.
• Microsoft Entra app type: Verify that your Microsoft Entra app registration is configured as Multitenant. Under the Authentication tab of your Entra app registration, the supported account type should be set to “Accounts in any organizational directory (Any Microsoft Entra directory - Multitenant)”. Multitenant configuration allows users from different organizations to sign in to your wrapped application.
• Redirect URIs: Confirm that the proper redirect URIs have been created and configured for both iOS and Android platforms within your Microsoft Entra app registration. Redirect URIs are crucial for the authentication flow, especially after successful user sign-in. For Android, specifically ensure that the hash for the redirect URI is provided correctly. Refer to the Azure Active Directory documentation for detailed instructions on configuring platform settings and redirect URIs for mobile applications.

By carefully reviewing and correcting these Microsoft Entra ID and app configuration settings, you should be able to resolve sign-in and data access issues in your wrapped mobile application.

Issue 6 - Azure key vault errors in wrap for Power Apps¶

Azure Key Vault errors during the wrap process can be identified by specific error codes displayed within the Power Apps wrap wizard portal. These error codes provide valuable clues about the nature of the configuration problem.

The following table outlines common Azure Key Vault error codes encountered in Power Apps wrap and provides guidance on their resolution. Utilize the search functionality within the Power Apps wrap wizard to locate the specific error code you are encountering and follow the corresponding troubleshooting steps.

Error Code	Description
1000118	Default subscription not found or missing access permissions.
1000119	Key vault does not exist or is missing access privileges.
1000120	No organization ID tags found on key vault.
1000121	Android keystore is not valid. Missing tag and/or certificate.
1000122	iOS certificate is not valid.
1000123	iOS profile is not valid.
1000128	Missing access key used while accessing Azure Blob storage location.

Let’s delve into the troubleshooting steps for some of these specific error codes.

Error code 1000118¶

Error code: 1000118
Description: Default subscription not found, or missing access permissions

This error indicates that Power Apps wrap cannot locate your default Azure subscription or lacks the necessary access permissions to it. To resolve this:

1. Default Subscription: Ensure your Azure Key Vault resides within your tenant’s Default subscription. Key Vaults should ideally be created within the default subscription for seamless integration with Power Apps wrap.

2. PowerShell Commands: Execute the following PowerShell commands as an administrator. These commands register a service principal that grants Power Apps wrap access to your Key Vault.

   Connect-AzureAD -TenantId <your tenant ID>
   

   New-AzureADServicePrincipal -AppId 4e1f8dc5-5a42-45ce-a096-700fa485ba20 -DisplayName "Wrap KeyVault Access App"
   

   Replace <your tenant ID> with your actual Azure tenant ID.

3. Azure Portal Access Control (IAM): In the Azure portal, navigate to your default subscription. On the Access Control (IAM) page, grant a Reader role assignment to the Service Principal representing your app (e.g., Wrap KeyVault Access App). This Reader role provides the necessary permissions for Power Apps wrap to read Key Vault configurations. Ensure this role assignment is applied at both the Subscription’s IAM and Key Vault’s IAM levels.

   Follow these steps within the Azure portal:

   1. Go to the Access control (IAM) tab and select Add role assignment under the Add menu.
   2. Choose the Job function roles tab and ensure the Reader role is selected. Then, navigate to the Members tab.
   3. Search for Wrap KeyVault Access App on the Members tab.
   4. Select Wrap KeyVault Access App and click Review + assign to assign the Reader role.

Error code 1000119¶

Error code: 1000119
Description: Key Vault does not exist, or Key Vault is missing access privileges

This error message indicates that either the specified Azure Key Vault cannot be found, or Power Apps wrap lacks the necessary access privileges to it. Troubleshooting steps are similar to error code 1000118, with an additional check:

1. Default Subscription: As with error 1000118, verify that your Azure Key Vault is located within your tenant’s Default subscription.
2. Vault Access Policy: When creating your Key Vault, ensure that the Vault access policy option is selected. Access policies control how services and users can interact with the Key Vault.

3. PowerShell Commands: Execute the same PowerShell commands as in error 1000118 to register the service principal:

   Connect-AzureAD -TenantId <your tenant ID>
   

   New-AzureADServicePrincipal -AppId 4e1f8dc5-5a42-45ce-a096-700fa485ba20 -DisplayName "Wrap KeyVault Access App"
   

   Replace <your tenant ID> with your Azure tenant ID.

4. Azure Portal Access Control (IAM): Follow the same steps as in error 1000118 to grant the Reader role to the Wrap KeyVault Access App service principal at both the Subscription and Key Vault IAM levels.

5. Add Access Policies to Key Vault: In addition to IAM roles, explicitly add access policies to your Azure Key Vault to grant Power Apps wrap specific permissions to access secrets, certificates, and keys within the vault. Access policies are configured directly within the Key Vault settings in the Azure portal.

Error code 1000120¶

Error code: 1000120
Description: No organization ID tags found on key vault

This error indicates that the required organization-id tag is missing from your Azure Key Vault. This tag is used to associate the Key Vault with your Power Apps environment. To rectify this:

1. Power Platform Admin Center: Go to the Power Platform admin center. Navigate to Environments and select the specific environment where your wrap project resides.
2. Copy Organization ID: Locate and copy the Organization ID of your selected Power Apps environment.
3. Azure Portal Key Vault Tags: In the Azure portal, access your Key Vault. Navigate to Tags. Create a new tag with the following details:
   • Name: organization-id
   • Value: Paste the Organization ID you copied from the Power Platform admin center.

Error code 1000121¶

Error code: 1000121
Description: Android keystore is not valid. Missing Tag and/or Certificate

This error signifies that your Android keystore configuration within the Azure Key Vault is incomplete or invalid. It typically means either the Android certificate or the associated tag is missing. To resolve this:

1. Import Android Certificate: Ensure you have imported your Android Certificate into your Azure Key Vault. This certificate is essential for signing Android application packages.
2. Add Certificate Tag: Create a new Tag for your Android Certificate within the Key Vault. Configure the tag as follows:
   • Tag name: The tag name should be based on the bundle ID you used in your wrap project. For instance, if your wrapped app’s bundle ID is com.testApp.wrap, the tag name should be com.testApp.wrap.keystore.
   • Tag value: The tag value must match the name you assigned to your Certificate when you uploaded it to the Key Vault. For example, if you named your Certificate AndroidWrapCertificate, the tag value should also be AndroidWrapCertificate.

Error code 1000122¶

Error code: 1000122
Description: iOS certificate is not valid

This error indicates an issue with your iOS certificate configuration in Azure Key Vault. Similar to error 1000121, it typically points to a missing or incorrectly configured iOS certificate or tag. To resolve this:

1. Import iOS Certificate: Verify that you have imported your iOS Certificate into your Azure Key Vault. This certificate is crucial for signing iOS application packages.
2. Add Certificate Tag: Create a new Tag for your iOS Certificate within the Key Vault, with these settings:
   • Tag name: The tag name should be derived from your wrap project’s bundle ID. For example, if your bundle ID is com.testApp.wrap, the tag name should be com.testApp.wrap.cert.
   • Tag value: The tag value must correspond to the name you provided for your Certificate when you uploaded it to the Key Vault. If you named your Certificate iOSCertificate1, the tag value should also be iOSCertificate1.

Error code 1000123¶

Error code: 1000123
Description: iOS profile is not valid

This error signifies that your iOS provisioning profile configuration in Azure Key Vault is invalid. It generally means the provisioning profile secret or its associated tag is missing or incorrectly configured. To resolve this:

1. Import Provisioning Profile as Secret: Ensure you have imported your iOS Provisioning Profile into your Azure Key Vault, specifically as a Secret. Provisioning profiles are handled as secrets within Key Vault.
2. Add Profile Tag: Create a new Tag for your Provisioning Profile Secret within the Key Vault. Configure the tag as follows:
   • Tag name: The tag name should be based on your wrap project’s bundle ID. For example, if your bundle ID is com.testApp.wrap, the tag name should be com.testApp.wrap.profile.
   • Tag value: The tag value must match the name you assigned to your Secret when you uploaded the provisioning profile to the Key Vault. If you named your Secret iOSProvisioningProfileSecret, the tag value should also be iOSProvisioningProfileSecret.

Error code 1000128¶

Error code: 1000128
Description: Missing access key used while accessing azure blob storage location

This error indicates that Power Apps wrap is unable to access your Azure Blob storage location due to a missing access key. To resolve this, you need to add your access key to the Azure Blob storage account in your Azure Key Vault. Refer to the Power Apps documentation for detailed instructions on configuring Azure Blob storage and access keys for wrap functionality.

Issue 7 - Wrap app sign-in fails¶

If users are experiencing sign-in failures within your wrapped application, consider these troubleshooting steps:

1. User Access Verification: Confirm that the user attempting to sign in has been granted access to the application. Ensure the app is properly shared with the intended users or user groups. Refer to the Power Apps documentation for guidance on sharing canvas apps within your organization.
2. Conditional Access Policies Review: If the user has access permissions, review the app’s Conditional Access policies within the Microsoft Entra admin center. Conditional Access policies can enforce specific requirements for user sign-in based on various factors. Ensure that no Conditional Access policies are inadvertently blocking user sign-ins. You will need a role that allows you to view both sign-in logs and Conditional Access policies to perform this review.
3. Troubleshooting Sign-in Errors: To investigate sign-in errors in detail, copy the correlation ID displayed on the mobile screen showing the failed sign-in attempt. Then, utilize this correlation ID and follow the guide provided in the Microsoft Entra documentation on troubleshooting sign-in errors. This guide will help you analyze sign-in logs and pinpoint the root cause of the sign-in failures.

Other issues in wrap for Power Apps¶

For any other issues not covered in this guide, or if your problem persists after following these troubleshooting steps, further investigation and support may be required.

Next steps¶

To report persistent or unaddressed issues, you will need to submit a support request. When submitting your request, it is highly beneficial to provide the following information to facilitate efficient troubleshooting:

• Repro Video or Screenshots: Include a video recording or screenshots that clearly demonstrate the issue you are experiencing. Visual evidence is invaluable for understanding the problem.
• Session ID: Provide a session ID from your Power Apps session. The session ID helps Microsoft support engineers trace and analyze your specific session logs. You can obtain the session ID in two ways:
  • Sign-in Screen: On the app sign-in screen, locate the gear icon in the lower right corner, select it, and then choose Session Details.
  • App Interface: After opening the app, tap and hold on the screen, and then select Session Details from the context menu.

By providing this information with your support request, you will enable the support team to diagnose and resolve your issue more effectively.

---

If you found this troubleshooting guide helpful, or if you have encountered other wrap issues and their solutions, please share your experiences in the comments below! Your insights can be valuable to other Power Apps makers.