Nothing is working in UiPath Apps

Feedback Apps
, ,
4

Hi Karl,

Thank you for taking the time to share this feedback, I regret not seeing this post sooner. There are several different items you’ve raised, so I’m going to do my best to address them individually.

Broken bindings

Toughest one first… In the beginning of July, we discovered a critical bug that impacted < 5% of developers over the course of 2 weeks which lead to spontaneous missing bindings. It’s important to note that deployed/production apps were not impacted by this issue, only apps opened in the designer (and only for certain users in certain browsers).

We take product issues like this very seriously. The last thing we want is for developers to lose their hard work or break their trust in the product. Upon discovery, we immedietly added an in-product notification to warn potentially impacted users, provide a workaround, and describe how to rollback if they had been impacted. Simultaniously, the team conducted an in-depth investigation to identify the root cause and roll out a fix. We regret this issue and have since added additional end-to-end testing to prevent edge cases like this in the future.

Public Apps

As a part of making public apps generally available this summer, the free preview became a paid feature for enterprise customers. Community and Trial accounts may continue to explore this feature for free, within reason. To limit disruption for enterprise preview participants, existing public apps where not disabled, but creating new public apps only becomes available with purchase.

App Deployment

In response to customer and community feedback like this we’ve made some changes to the way your apps are published and deployed. Consequently, the way you add a user as “run only” on an app is by adding them to the folder that the app is deployed in. You can learn more about this here: Deploying Apps.

I’m not certain what your exact issue was when you tried to showcase your app, but I’d be happy to connect to learn more. It sounds like it may have been a combination of this bug plus some of the product changes described above.