Blocker to deploy Coded App developed using Coding Agnets

Hi All, I built an app to get a hands on development using Coding Agents and UiPath skills. While my app is functional and working as expected however when I am trying to deploy the app on the orchestrator I am facing below issues as seen the snap attached where it is asking me provide app url name, but whatever name I am giving it is not meeting the criteria. Also the author of the deployed app is UiPath Developer which usually is not case.
I am seeking help regarding the same on deploying the app on the cloud environment or is there any documentation regarding the same which I have missed.


This usually happens due to naming constraints and metadata mismatch during deployment.

You can verify below:

App URL / name must follow strict rules (lowercase, no spaces, no special characters except hyphen)
Ensure the package author and version metadata are properly set while publishing
Try republishing with a different package name + version (e.g., 1.0.1)

I republished with new package version, updated author and metadata configurations also I have kept the same. Still the same issues persists.

Could you please verify that the App name and package name match exactly? If not, update and republish the package. Also, ensure the package is published to the same folder/feed as the app.

I was able to deploy in my personal workspace folder while previously I was trying to deploy in Shared folder. I am not sure how this is connected but for now the app was deployed.

Post this the app is not showing any content. It is blank page. Do I need to embed something somewhere?

For the blank page, can you confirm whether the app loads correctly when run locally in Coding Agent/Web Studio? Also, check the browser Developer Tools (F12) for any errors and verify that all required resources, endpoints, and environment variables are configured in the target folder/environment.

If possible, please share any console errors or screenshots from the blank page.

Hi @kkapula4,

Every aspect of the app is working perfectly and as expected in local but not post deployment. What I feel might be causing issues are below points:

  • The app is designed to display details from Shared folder, but app is deployed in MyWorkspace as it is not allowing to deploy in Shared folder.
  • The Shared folder details, Folder Id are all provided in env file and were deployed with same. May be these configurations are mismatching somewhere.
  • There is not option to edit env variables in the app deployment configuration.

Below is the snap from page load error. I believe there is something missing which I am not able to see.

Thanks,
Ashish

@RaoAshish

As per error its looking for some assets which are not present in the deployed folder

cheers

Hi @Anil_G

Yes, I see but the app does not need an asset to operate, nor any data is stored in the same.
It needs to access storage bucket, and those details are provided in the env file already.

Thanks,
Ashish

@RaoAshish

is the storage bucket from same folder or is the folder details also provided to it?

go to networks tab and check what request body you see there

cheers

Hi @Anil_G,

As mentioned earlier storage bucket being accessed and app deployed are different folder but the folder details are provided in env file. The network tab details are as in below snap.

Thanks,
Ashish

@RaoAshish

Are you on community enterprise trail or enterprise?

one thing I observed is on staging its working not on enterprise version

also the error still is triggered from the storage bucket browse itself

cheers

Hi @Anil_G,

I am using community version not enterprise trial and probably community version has some issues.
If anyone from UiPath can see and revert here it would be a great help.

Thanks,
Ashish

@RaoAshish

can you please check here and do the steps for configuring relative asset paths

looks like that is causing the issue

cheers

Could you try deploying a very simple sample app to the same Shared Folder and check if it exhibits the same behavior? That would help determine whether the issue is app-specific or related to the folder/environment configuration.

I referred this and made changes and yes these deployment options were missing. I cannot say I reached my goal but all the blockers were resolved. Only dev changes remain, but I am able to see the changes now.

Thank you so much @Anil_G and @kkapula4 for your help and guidance in figuring out the issues with the app.

Happy Building!

Thanks,
Ashish