[Bug] Unable to push the Code App to PowerApps/CRM

[agregoirehsdyn]

Hello,

I have created a Code App using this guide https://learn.microsoft.com/en-us/power-apps/developer/code-apps/overview but once I try to push the app to my Dynamics 365 environment, I get this error: There was an error in pushing the app: bolt.authentication.http.AuthenticatedClientException: Encountered internal server error.

Full logs

PS C:\EmptyCodeApp\EmptyCodeApp> pac code push --solutionName "XXXXX"
_Connected as aXXXXX.XXXXXt@XXXXX.com
Connected to... XXXX-XXXX XXXX EU XXXX-Dev

Listing all Solutions from the current Dataverse organization...
Saving app ...
bolt.system.VerbExecutionException: CodePushCreateNewAndSaveAppErrorMessage
à bolt.module.code.PushVerb.d__15.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à bolt.module.code.PushVerb.d__11.MoveNext() Failed to push the app. Retrying...
bolt.system.VerbExecutionException: CodePushCreateNewAndSaveAppErrorMessage
à bolt.module.code.PushVerb.d__15.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à bolt.module.code.PushVerb.d__11.MoveNext() Failed to push the app. Retrying...
bolt.system.VerbExecutionException: CodePushCreateNewAndSaveAppErrorMessage
à bolt.module.code.PushVerb.d__15.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à bolt.module.code.PushVerb.d__11.MoveNext() Failed to push the app. Retrying...
bolt.system.VerbExecutionException: CodePushCreateNewAndSaveAppErrorMessage
à bolt.module.code.PushVerb.d__15.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à bolt.module.code.PushVerb.d__11.MoveNext() Failed to push the app. Retrying...
Microsoft PowerPlatform CLI
Version: 2.1.1+gefbf518 (.NET Framework 4.8.9221.0)
Online documentation: https://aka.ms/PowerPlatformCLI
Feedback, Suggestions, Issues: https://github.com/microsoft/powerplatform-build-tools/discussions

Error: There was an error in pushing the app: bolt.authentication.http.AuthenticatedClientException: Encountered internal server error. The correlation Id is '67960a30-0757-4da8-9859-f1d8a293538a'.
à bolt.authentication.http.AuthenticatedHttpClient.d__16.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
à bolt.authentication.http.AuthenticatedHttpClient.d__18`1.MoveNext()
--- Fin de la trace de la pile à partir de l'emplacement précédent au niveau duquel l'exception a été levée ---
à System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
à System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
à bolt.module.code.PushVerb.d__15.MoveNext()_

Misc informations

I have tried with --environment or --solution parameter
I have tried pac auth clear
I have tried on a PC without any proxy
I have enabled the CodeApp option on the environment
I have tried with CLI 2.1.1 and 1.44.2
I have tried with npm 11.7.0
I have System Administrator privileges on the targeted environment

I have contacted the Microsoft Support and it told me to create a ticket here.

Steps:

1. On PowerShell 7.5.4 with CLI 2.1.1
2. Targeting a "production" type environment, but we use it as a dev
3. pac code push
4. Error: There was an error in pushing the app: bolt.authentication.http.AuthenticatedClientException: Encountered internal server error. The correlation Id is '67960a30-0757-4da8-9859-f1d8a293538a'.

[agregoirehsdyn]

After testing multiple things, it might be linked to the environment type "Production".
Can anyone try to do a pac code push to a Production environment?

[chumleesockson]

After testing multiple things, it might be linked to the environment type "Production". Can anyone try to do a pac code push to a Production environment?

I've not tried that before. Can you push it to a dev environment and deploy it to the production environment?

[madhumach]

When you run the push command, were you using the same environmentId profile as on the power.config.json?

[agregoirehsdyn]

After testing multiple things, it might be linked to the environment type "Production". Can anyone try to do a pac code push to a Production environment?

I've not tried that before. Can you push it to a dev environment and deploy it to the production environment?

Yes I can, but it's really not convenient

[agregoirehsdyn]

When you run the push command, were you using the same environmentId profile as on the power.config.json?

Yes, it is the right Id.
When it's not, I get an explicit message

[madhumach]

@agregoirehsdyn could you share the power.config.json file values for further debugging?

[agregoirehsdyn]

@madhumach
Here it is, I just changed the environmentId

{
"appId": "",
"appDisplayName": "Empty Code App",
"description": null,
"environmentId": "XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX",
"buildPath": "./dist",
"buildEntryPoint": "index.html",
"logoPath": "Default",
"localAppUrl": "http://localhost:3000/",
"region": "prod",
"connectionReferences": {},
"databaseReferences": {}
}

[ansjain215]

@agregoirehsdyn We’ve identified this as a product bug in the Code Apps publishing pipeline and we expect the fix to be deployed by next week.

Impact clarification:
This issue only affects environments where the “Enable IP address based Storage Shared Access Signature (SAS) rule” setting is turned on. When enabled, this setting applies additional IP-based restrictions to SAS tokens used during app operations, which is what triggers the publishing failure you’re seeing.
You can find more details about this setting and its behavior here:
https://learn.microsoft.com/en-us/power-platform/admin/security/data-storage#storage-shared-access-signature-sas-ip-restriction
Once the fix is deployed, publishing should work as expected.

Thanks again for raising this - we’ll update this thread once the fix is live.