Merge pull request #11546 from OfficeDev/supkasar-patch-13

docs: Update package.nls.json

packages/fx-core/resource/package.nls.json

@@ -782,20 +782,20 @@
   "error.m365.M365TenantIdNotMatchError": "Authentication failed. You are currently signed in to Microsoft 365 tenant '%s', which is different from the one specified in the .env file (TEAMS_APP_TENANT_ID='%s'). To resolve this issue and switch to your current signed-in tenant, please remove the values of '%s' from the .env file and try again.",
   "error.arm.CompileBicepError": "Unable to compile Bicep files located in path '%s' to JSON ARM templates. The error message returned was: %s. Check the Bicep files for any syntax or configuration errors and try again.",
   "error.arm.DownloadBicepCliError": "Unable to download Bicep cli from '%s'. The error message was: %s. Fix the error and try again. Or remove the bicepCliVersion config in the config file teamsapp.yml and Teams Toolkit will use bicep CLI in PATH",
-  "error.arm.DeployArmError.Notification": "The ARM templates for deployment name: '%s' could not be deployed in resource group '%s'. Refer to the [Output panel](command:fx-extension.showOutputChannel) for more details.",
-  "error.arm.DeployArmError": "The ARM templates for deployment name: '%s' could not be deployed in resource group '%s' for reason: %s",
-  "error.arm.GetArmDeploymentError": "The ARM templates for deployment name: '%s' could not be deployed in resource group '%s' for reason: %s. \nUnable to get detailed error message due to: %s. \nRefer to the resource group %s in portal for deployment error.",
-  "error.arm.ConvertArmOutputError": "Unable to convert ARM deployment result to action output, there is a duplicated key '%s' in ARM deployment result.",
-  "error.deploy.DeployEmptyFolderError": "Unable to locate any files in the distribution folder: '%s'. Please ensure that the folder is not empty and that all necessary files have been included.",
-  "error.deploy.CheckDeploymentStatusTimeoutError": "Unable to check deployment status because the process timed out. Check your internet connection and try again. If the issue persists, please review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred.",
-  "error.deploy.ZipFileError": "Failed to zip the artifact folder. The folder size exceeds the maximum limit of 2GB. Please reduce the size of the folder and try again.",
-  "error.deploy.ZipFileTargetInUse": "Failed to clear the distribution zip file in %s. The file may be currently in use. Please close any applications using the file and try again.",
+  "error.arm.DeployArmError.Notification": "The ARM templates for deployment name: '%s' couldn't be deployed in resource group '%s'. Refer to the [Output panel](command:fx-extension.showOutputChannel) for more details.",
+  "error.arm.DeployArmError": "The ARM templates for deployment name: '%s' couldn't be deployed in resource group '%s' for reason: %s",
+  "error.arm.GetArmDeploymentError": "The ARM templates for deployment name: '%s' couldn't be deployed in resource group '%s' for reason: %s. \nUnable to get detailed error message due to: %s. \nRefer to the resource group %s in portal for deployment error.",
+  "error.arm.ConvertArmOutputError": "Unable to convert ARM deployment result into action output. There is a duplicated key '%s' in ARM deployment result.",
+  "error.deploy.DeployEmptyFolderError": "Unable to locate any files in the distribution folder: '%s'. Make sure the folder includes all necessary files.",
+  "error.deploy.CheckDeploymentStatusTimeoutError": "Unable to check deployment status because the process timed out. Check your internet connection and try again. If the issue persists, review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred.",
+  "error.deploy.ZipFileError": "Unable to zip the artifact folder as its size exceeds the maximum limit of 2GB. Reduce the folder size and try again.",
+  "error.deploy.ZipFileTargetInUse": "Unable to clear the distribution zip file in %s as it may be currently in use. Close any apps using the file and try again.",
   "error.deploy.GetPublishingCredentialsError.Notification": "Unable to obtain publishing credentials of app '%s' in resource group '%s'. Refer to the [Output panel](command:fx-extension.showOutputChannel) for more details.",
-  "error.deploy.GetPublishingCredentialsError": "Unable to obtain publishing credentials of app '%s' in resource group '%s' for reason:\n %s.\n Suggestions:\n 1. Verify that the app name and resource group name are spelled correctly and are valid. \n 2. Verify that your Azure account has the necessary permissions to access the API. You may need to elevate your role or request additional permissions from an administrator. \n 3. If the error message includes a specific reason, such as an authentication failure or a network issue, investigate that issue specifically to resolve the error and try again. \n 4. You can test the API in this page: '%s'",
+  "error.deploy.GetPublishingCredentialsError": "Unable to obtain publishing credentials of app '%s' in resource group '%s' for reason:\n %s.\n Suggestions:\n 1. Make sure the app name and resource group name are spelled correctly and are valid. \n 2. Make sure your Azure account has necessary permissions to access the API. You may need to elevate your role or request additional permissions from an administrator. \n 3. If the error message includes a specific reason, such as an authentication failure or a network issue, investigate that issue specifically to resolve the error and try again. \n 4. You can test the API in this page: '%s'",
   "error.deploy.DeployZipPackageError.Notification": "Unable to deploy zip package to endpoint: '%s'. Refer to the [Output panel](command:fx-extension.showOutputChannel) for more details and try again.",
-  "error.deploy.DeployZipPackageError": "Unable to deploy zip package to endpoint '%s' in Azure due to error: %s. \nSuggestions:\n 1. Verify that your Azure account has the necessary permissions to access the API. \n 2. Verify that the endpoint is properly configured in Azure and that the required resources have been provisioned. \n 3. Ensure that the zip package is valid and free of errors. \n 4. If the error message specifies the reason, such as an authentication failure or a network issue, fix the error and try again. \n 5. If the error still persists, you can attempt to deploy the package manually following the guidelines in this link: '%s'",
-  "error.deploy.CheckDeploymentStatusError": "Unable to check deployment status for location: '%s' due to error: %s. If the issue persists, please review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred.",
-  "error.deploy.DeployRemoteStartError": "The package has been successfully deployed to Azure for location: '%s', but the application is not able to start due to error: %s.\n If the reason is not clearly specified, here are some suggestions to troubleshoot:\n 1. Check the application logs: Look for any error messages or stack traces in the application logs to identify the root cause of the problem.\n 2. Check the Azure configuration: Ensure that the Azure configuration is correct, including connection strings and application settings.\n 3. Check the application code: Review the code to see if there are any syntax or logic errors that could be causing the issue.\n 4. Check the dependencies: Verify that all dependencies required by the application are correctly installed and updated.\n 5. Restart the application: Try restarting the application in Azure to see if that resolves the issue.\n 6. Check the resource allocation: Make sure that the resource allocation for the Azure instance is appropriate for the application and its workload.\n 7. Seek help from Azure support: If the issue persists, reach out to Azure support for further assistance.",
+  "error.deploy.DeployZipPackageError": "Unable to deploy zip package to endpoint '%s' in Azure due to error: %s. \nSuggestions:\n 1. Make sure your Azure account has necessary permissions to access the API. \n 2. Make sure the endpoint is properly configured in Azure and the required resources have been provisioned. \n 3. Make sure the zip package is valid and free of errors. \n 4. If the error message specifies the reason, such as an authentication failure or a network issue, fix the error and try again. \n 5. If the error still persists, deploy the package manually following the guidelines in this link: '%s'",
+  "error.deploy.CheckDeploymentStatusError": "Unable to check deployment status for location: '%s' due to error: %s. If the issue persists, review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred.",
+  "error.deploy.DeployRemoteStartError": "The package deployed to Azure for location: '%s', but the app is not able to start due to error: %s.\n If the reason is not clearly specified, here are some suggestions to troubleshoot:\n 1. Check the app logs: Look for any error messages or stack traces in the app logs to identify the root cause of the problem.\n 2. Check the Azure configuration: Make sure the Azure configuration is correct, including connection strings and application settings.\n 3. Check the application code: Review the code to see if there are any syntax or logic errors that could be causing the issue.\n 4. Check the dependencies: Make sure all dependencies required by the app are correctly installed and updated.\n 5. Restart the application: Try restarting the application in Azure to see if that resolves the issue.\n 6. Check the resource allocation: Make sure the resource allocation for the Azure instance is appropriate for the app and its workload.\n 7. Get help from Azure support: If the issue persists, reach out to Azure support for further assistance.",
   "error.script.ScriptTimeoutError": "Script execution timeout. Adjust 'timeout' parameter in yaml or improve your script's efficiency.",
   "error.script.ScriptExecutionError": "Unable to execute script action.",
   "error.deploy.AzureStorageClearBlobsError.Notification": "Unable to clear blob files in Azure Storage Account '%s'. Refer to the [Output panel](command:fx-extension.showOutputChannel) for more details.",

packages/fx-core/tests/common/error/deployError.test.ts

@@ -20,10 +20,10 @@ describe("DeployEmptyFolderError", () => {
     expect(error).to.be.instanceOf(UserError);
     expect(error.source).to.equal("azureDeploy");
     expect(error.message).to.equal(
-      `Unable to locate any files in the distribution folder: '${folderPath}'. Please ensure that the folder is not empty and that all necessary files have been included.`
+      `Unable to locate any files in the distribution folder: '${folderPath}'. Make sure the folder includes all necessary files.`
     );
     expect(error.displayMessage).to.equal(
-      `Unable to locate any files in the distribution folder: '${folderPath}'. Please ensure that the folder is not empty and that all necessary files have been included.`
+      `Unable to locate any files in the distribution folder: '${folderPath}'. Make sure the folder includes all necessary files.`
     );
   });
 });
@@ -34,10 +34,10 @@ describe("CheckDeploymentStatusTimeoutError", () => {
     expect(error).to.be.instanceOf(UserError);
     expect(error.source).to.equal("azureDeploy");
     expect(error.message).to.equal(
-      "Unable to check deployment status because the process timed out. Check your internet connection and try again. If the issue persists, please review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred."
+      "Unable to check deployment status because the process timed out. Check your internet connection and try again. If the issue persists, review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred."
     );
     expect(error.displayMessage).to.equal(
-      "Unable to check deployment status because the process timed out. Check your internet connection and try again. If the issue persists, please review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred."
+      "Unable to check deployment status because the process timed out. Check your internet connection and try again. If the issue persists, review the deployment logs (Deployment -> Deployment center -> Logs) in Azure portal to identify any issues that may have occurred."
     );
   });
 });
@@ -101,7 +101,7 @@ describe("CacheFileInUse", () => {
     expect(error).to.be.instanceOf(UserError);
     expect(error.source).to.equal("azureDeploy");
     expect(error.message).to.equal(
-      `Failed to clear the distribution zip file in ${path}. The file may be currently in use. Please close any applications using the file and try again.`
+      `Unable to clear the distribution zip file in ${path} as it may be currently in use. Close any apps using the file and try again.`
     );
   });
 });