Mobile app Error: No Objects in Response

Feedback Apps
,
1

Please could you help me? Mobile app on ios throws an error as “there were no objects in this response”.

3

@Dominik_Celuch ,

Try this:

  1. Check API Endpoint:

    • Ensure that the API endpoint you are calling is correct. Verify that the URL, parameters, and method (GET, POST, etc.) are properly configured.

  2. Inspect Request and Response:

    • Use tools like Postman or curl to test the API endpoint manually. This way, you can observe what the API returns directly and confirm if the issue lies with the API itself or with how the mobile app processes the data.
    • Look for correct headers (like Authorization or Content-Type) and ensure they are set correctly.

  3. Review API Documentation:

    • Check the API documentation to see the expected structure of the response. If the API documentation states that certain parameters or body data are required, ensure these are included in your request.

  4. Handle Empty Responses:

    • In your UiPath workflows, make sure there is error handling in place for empty responses. For instance, you can add conditions to check if the response contains data before proceeding.
    • Use a Try-Catch activity to gracefully handle cases where the response does not meet expectations.

  5. Log the Output:

    • Utilize logging in your workflows to capture responses. Use the Log Message activity to log the output of the API call. This can help you identify if the API is returning an empty array or an error message.

  6. API Rate Limits:

    • Some APIs have a rate limit that can lead to denied or empty responses after many successful calls. Verify if you’re hitting any rate limits by consulting the API documentation or contacting support.

  7. Authentication Issues:

    • Ensure that your authentication tokens or credentials are valid. Expired tokens or incorrect credentials can lead to unauthorized access and result in empty responses.

  8. Check for Filters or Query Parameters:

    • If you are using filters or query parameters in your request, verify that they are correct and not filtering out all results. Try removing any filtering to see if the API returns data.

  9. Debugging the UiPath Workflow:

    • If the API call is part of a larger UiPath workflow, step through the workflow in debug mode to identify where it might be failing.
    • Ensure that variables used to capture the response are initialized and assigned properly.
4

@naveen.s

this error appears during the login to the UiPath orchestator mobile app :slight_smile:

Im sorry my mistake, I should have been more precise.

5

@Dominik_Celuch ,

Try below steps:

1. Check Server URL

  • Ensure that the URL you are using to access the Orchestrator is correct. This includes checking for any typographical errors and ensuring that it includes the correct protocol (http:// or https://).
  • Make sure that you are using the appropriate endpoint for the mobile app.

2. Network Connectivity

  • Verify that your mobile device is connected to the internet and that there are no firewalls or proxies blocking the request to the Orchestrator.
  • Try accessing the Orchestrator via a web browser on the same network to see if you are experiencing connectivity issues.

3. API Permissions

  • Ensure that the user account you are trying to log in with has the necessary permissions to access the Orchestrator. Admin roles usually have broader access.
  • Verify that the API access is enabled for your user.

4. Check Orchestrator Version Compatibility

  • Ensure that the version of the UiPath Orchestrator you are trying to connect to is compatible with the mobile app version. If there was a recent update to either, check the release notes for any changes related to the API or mobile app compatibility.

5. Review Authentication Settings

  • Ensure that the authentication method configured in the Orchestrator aligns with what you are using in the mobile app. For instance, if you are using Windows Authentication, make sure that is supported through the app.

6. Inspect Server Logs

  • If you have access to the Orchestrator server logs, check them for any errors or warnings that might provide insight into why the login is failing.
  • Look for any error messages during the authentication process.

7. Mobile App Cache

  • Sometimes, app caches can cause issues. You could try clearing the cache of the UiPath Orchestrator mobile app via the settings on your device.

8. Test with Different User Accounts

  • If possible, try to log in using a different user account to see if the issue persists. This can help determine if the issue is user-specific.

9. Reinstall the App

  • If you have tried other solutions without success, consider uninstalling and then reinstalling the UiPath Orchestrator mobile app. This may resolve any corrupted files or settings.
6

@Dominik_Celuch,

It’s already reported issue. May be the team is still working on it. @loginerror Could you please update on this?

7

It’s ridiculous is what it is. What’s their market cap again?