1. Home
  2. Documentation
  3. Using Dropsource
  4. Resolving Errors

Resolving Errors

Dropsource validates your project as you work, and will alert you to any errors or potential issues in the To Do list on the left of the editor.

error list

Errors will prevent your app from building and running. If you have any errors in your app, you won’t be able to download the source code for it, because Dropsource writes the code when you run the app.

Warnings alert you to issues that may prevent the app from functioning the way you expect it to, but will not stop it from running.

warnings

If you encounter a build error when you attempt to run your app, Dropsource support will look into the issue and give you a status update.

If you’re having trouble resolving an error you’re seeing in the editor, check out the list below for steps to rectify the problem. Otherwise get in touch via the Chat chat button button in Dropsource for premium project support, or post a question on the forum.

Common Issues

Error details:

Errors

Alert Validation
Message: An action [ action name ] in the event [ event name ] for [ element name ] on page [ page name ] should not have any buttons with the same label.

Trigger: The same name is assigned to more than one button for an Alert.

Solution: Locate the Show Alert Action in the specified Event and change the button names so that no two are the same.

API Auth Invalid

Message: The auth form for the API [ api name ] has been assigned an invalid value for a field.

Trigger: A field in the auth modal for an API is assigned an invalid value.

Solution: Open the API tab in the right sidebar and locate the API that is missing a required field. Click the Auth link next to the API name. In the Auth modal, fill out the form with valid values. You can do this on any page.

API Auth Missing

Message: The auth form for the [ API name ] needs to be filled out.

Trigger: A field in the auth modal for an API is empty.

Solution: Open the API tab in the right sidebar and locate the API that is missing a required field. Click the Auth link next to the API name. In the Auth modal, fill out the form. You can do this on any page.

Body Parameter Deleted

Message: The property [ property name ] in the body for route [ request name ] on page [ page name ] has been deleted but is still in use. Please clear its binding.

Trigger: A body parameter that was bound has been deleted.

Solution: Open the API tab on the relevant page and click the request. In Parameters, select Body, click the field and clear the current selection.

Body Parameter Invalid

Message: The property [ property name ] in the body for route [ request name ] on page [ page name ] has been assigned an invalid value.

Trigger: A body parameter has been bound to an invalid value.

Solution: Open the API tab on the relevant page and click the request. In Parameters, select Body, click the field and make a valid selection.

Deleted Path in Use

Message: The request [ request name ] on page [ page name ] is using a path that has been deleted. Please delete the request.

Trigger: A deleted path is in use as a request.

Solution: Open the request in the API tab and delete it from the relevant page.

Deleted Response Event

Message: The [ status code ] response of [ request name ] on page [ page name ] has been deleted but is still running actions. Please remove any actions from the response event.

Trigger: A request with Actions added to Events has been deleted.

Solution: Open the request in the API tab and Manage the relevant status code Event, removing any Actions.

Device Variable Data Type Deleted

Message: The data type [ data type name ] from the plugin [ plugin name ] has been deleted. The device variable [ variable name ] uses this data type, so you need to either delete the variable or change its data type.

Trigger: A Device Variable is declared using a data type that has been deleted.

Solution: Select the variable in the Device Variables drawer on the left and change its data type to a valid option.

Dynamic Element Validation

Message: The element [ element name ] on page [ page name ] is set to dynamic but hasn’t been assigned a data source. [ Element name ] must have a data source when set to dynamic.

Trigger: An Element is set to dynamic but has not been assigned a Data Source from an API response.

Solution: Bind a Data Source to the dynamic Element (i.e. Table, List, Page Controller, or View Pager) or set the Element to static content using its Properties. To bind a Data Source, add an API request to your page and click the Data Source in Responses, choosing the dynamic Element.

Element Name Validation

Message: There are [ count ] elements named [ name ] on page [ page name ].

Trigger: The same name is assigned to two or more Elements on the same page.

Solution: Locate the Elements on the relevant page and change their names so that each one is unique.

Empty App Validation

Message: This app doesn’t have any pages. Click the Pages button to add one.

Trigger: The app does not contain any pages.

Solution: Open Pages on the left and add a page to the app.

Invalid Action Parameter

Message: The action [ action name ] in the event [ event name ] for [ element name ] on page [ page name ] has an invalid value for the parameter [ parameter name ]. Please make a new selection.

Trigger: An Action field has been assigned an invalid value.

Solution: Open the specified page and element, click Manage for the Event, and make a valid selection for the field.

Invalid Lifecycle Parameter

Message: The action [ action name ] in the lifecycle event [ event name ] has an invalid value for the parameter [ parameter name ]. Please make a new selection.

Trigger: An Action field on a lifecycle Event has been assigned an invalid value.

Solution: Open the Event in the App Lifecycle drawer on the left and select a valid value for the specified field.

Invalid Response Assignment

Message: The response value [ responseValue ] from the [ response name ] response of [ requestName ] on page [ page name ] is a [ expected type ] but is being assigned to an incompatible type. Please clear the binding or assign it to a compatible type.

Trigger: A response field is bound to an invalid Element for its type.

Solution: Open the specified page and request, click the response field and make a new, valid selection for the field’s data type.

Key Page Validation

Message: 1 key page has not been assigned a page.

Trigger: The key page field is empty.

Solution: Click the key button in Pages and select a page from the drop-down list.

Lifecycle Parameter Missing

Message: The action [ action name ] in the lifecycle event [ event name ] is missing a value for the required parameter [ parameter name ].

Trigger: An Action field on a lifecycle Event is missing a value.

Solution: Open the Event in the App Lifecycle drawer on the left and select a value for the specified field.

Multiple Child Elements in Dynamic Parent

Message: Only one element is allowed to be the child of [ element name ] on page [ page name ] when a data source is assigned. Please delete all but one child or set [ element name ] to not be [ current value ].

Trigger: A dynamic Element has more than one child Element.

Solution: Delete or move all but one of the child Elements or set the parent Element to static content using its Properties.

Multiple Data Source Assignments to Same Element

Message: The element [ element name ] on page [ page name ] has been assigned data sources from these routes: [ route name ], [ route name ], etc. It can only have one data source assigned to it.

Trigger: An Element has more than one data source assigned to it.

Solution: Open the API tab for the page and edit the relevant request(s). Alter the Data Source selections so that only one is assigned to the Element.

Multiple Fields Binding to Same Element

Message: The property [ property name ] of element [ element name ] on page [ page name ] is bound to multiple response values in the [ status code ] response of [ request name ]. It should only be bound to one response value.

Trigger: More than one field in a single response status is bound to a single Element.

Solution: Open the Responses in the API tab for the relevant request. Alter the field selections so that only one is bound to each Element.

No App Name

Message: This app does not have an app name. Click the Settings button to add one.

Trigger: The app name is empty.

Solution: Open the app Settings and add a name.

No App Preferences

Message: The App Preferences modal is missing [ missing fields ].

Trigger: One or more fields in the app preferences modal is empty.

Solution: Open the project Settings and complete all required fields.

No Child Element in Dynamic Parent

Message: The element [ name ] on page [ page name ] is assigned a data source but doesn’t have a child element. [ name ] must have a single child element when assigned a data source.

Trigger: A dynamic Element is assigned a Data Source but has no children.

Solution: Add a single child Element (i.e. Table Cell, Dynamic List Tile, or View) to the parent element (i.e. Table, List, Page Controller, or View Pager) or set the parent Element to static content using its Properties.

Null Action Field Validation

Message: The action [ action name ] in the event [ event name ] for [ element name ] on page [ page name ] is missing a value for the required parameter [ parameter name ].

Trigger: A required field in an Action is missing.

Solution: Edit the relevant Event by selecting the Element or Request and opening Properties > Events. Select the relevant Event and edit or delete the Action so that no required fields are set to null.

Page Variable Data Type Deleted

Message: The data type [ data type name ] from the plugin [ plugin name ] has been deleted. The page variable [ variable name ] uses this data type, so you need to either delete the variable or change its data type.

Trigger: A Page Variable is declared using a data type that has been deleted.

Solution: Select the variable in the Page Variables drawer on the right and change its data type to a valid option.

Page Variable Validation

Message: The page [ page name ] is set as a key page. Key pages cannot have required page variables.

Trigger: A key page has a Page Variable declared as required during inbound navigation.

Solution: Open the key page and select the variable in the Page Variables tab on the right – uncheck the Is required during inbound navigation checkbox.

Parameter Binding Deleted

Message: The parameter [ parameter name ] in the route [ request name ] on page [ page name ] has been deleted but is still in use. Please clear its binding.

Trigger: A parameter that was bound has been deleted.

Solution: Open the API tab on the relevant page and click the request. In Parameters, click the field and clear its selection.

Parameter Binding Invalid

Message: The parameter [ parameter name ] in the route [ request name ] on page [ page name] has been assigned an invalid value.

Trigger: A parameter has been bound to an invalid value.

Solution: Open the API tab on the relevant page and click the request. In Parameters, click the field and select a valid value.

Parent Data Source Mismatch

Message: The assignment of [ response value name ] from the [ status code ] response of [ request name ] on page [ page name ] needs to a assigned to a child of the the data source [ data source name ]. The parent data source assignment is currently set to the data source [ data source name ] from the [ status code ] response of [ request name ].

Trigger: The Data Source for the parent Element (i.e. Table, List, Page Controller, View Pager) does not match the required Data Source. The response value assigned to the child Element is associated with another request.

Solution: Open the API tab and edit the relevant request. Clear the selection for the Data Source assignment.

Parent Data Source Missing

Message: The assignment of [ response field ] from the [ status code ] response of [ request name ] on page [ page name ] needs to be assigned to a child of the data source [ data source name ]. That data source is not currently present.

Trigger: The Data Source for a child field is missing.

Solution: Open the API tab and edit the relevant request. The Data Source should be bound to a dynamic parent Element and the fields inside it to child Elements of the dynamic parent.

Push Transition Validation

Message: The action Go To Page in the event [ event name ] for [ element name ] on page [ page name ] is not allowed to use a push transition because it does not have a nav bar.

Trigger: A page without a nav bar has a Go To Page Action set to use push transition.

Solution: Open the Event with the Go To Page Action and click Edit. Alter the transition so that it does not use the push option.

Request Bindings Invalid

Message: You are running the request [ request name ] from the [ event name ] event of element [ element name ] on page [ page name ]; however, the element [ element name ] does not have access to the selected data source used in parameter [ parameter name ] for the request.

Trigger: An inaccessible Data Source value has been bound to a request Parameter.

Solution: Open the request in the API tab and edit the Parameter selection to an accessible value.

Required Parameters Missing

Message: The parameter [ parameter name ] in the route [ request name ] on page [ page name ] is required and needs a value assigned.

Trigger: A value has not been assigned to a required parameter.

Solution: Open the API tab on the relevant page and click the request. Open the Parameters section and click the null parameter – select a value.

Response Binding Deleted

Message: The response value [ field name ] from the [ response name ] response of [ request name ] on page [ page name ] has been deleted but is still in use. Please clear its binding.

Trigger: A response field that was bound in an API request has been deleted.

Solution: Open the specified page and request, click the response field and clear its current selection.

Response Data Binding Deleted

Message: The element [ element name ] on page [ page name ] is being assigned a value from the deleted value [ data type name ] in the [ response status ] response of [ request name ]. Please clear the assignment.

Trigger: A response field that has been deleted is assigned to an Element.

Solution: Open the specified page and clear any bindings in the request responses / status code Event Actions for the deleted field.

Static Parent Validation

Message: The element [ element name ] on page [ page name ] is set to [ current value ] but has been assigned a data source. [ Element name ] must not have a data source when set to [ current value ].

Trigger: An Element is set to static but has been bound to a Data Source.

Solution: Either unassign the Data Source(s) associated with the Element or set the Element to dynamic content using its Properties.

Tab Bar Index Validation

Message: Every page with a tab bar must have a unique tab index. The tab index for the following pages is set to [ index ]: [ page name ].

Trigger: More than one page in the tab bar has the same index.

Solution: Open one of the specified pages, select the page Element, and edit the Tab Index Property on the right.

Unexpected Data Source

Message: The assignment of [ response value name ] from the [ status code ] response of [ request name ] on page [ page name ] needs to be assigned to a child of the data source [ data source name ]. The parent data source assignment is currently set to the data source [ data source name ] from the [ status code ] response of [ request name ].

Trigger: A child Element is bound to a field inside a different Data Source to the one bound to the parent Element.

Solution: Open the API tab for the page and edit the relevant request. Either remove the assignment from the child Element or remove the Data Source assignment from the parent Element.

Unexpected Parent Data Source

Message: The assignment of [ response field ] from the [ status code ] response of [ request name ] on page [ page name ] should not be a child of any data source. The current parent assignment is of the data source [ data source name ] from the [ status code ] response of [ request name ].

Trigger: A field inside a Data Source is bound to an Element that is not inside a dynamic parent.

Solution: Open the API tab for the page and edit the relevant request. Remove the binding from the field to the dynamic child Element.

Warnings

Run Request Action Missing Warning

Message: It looks like you want to use the [ API name ] request [ request name ] on page [ page name ]. You need to use an action to run the request before it will work.

Trigger: An API request has been added to a page but no Run API Request Action has been added for it.

Solution: You need to add a Run API Request Action for any requests you want to run in a page – this issue will not prevent your app from building, but your request will not execute when the app runs. Choose the page or an Element inside it, open the Properties > Events, and click Manage for the Event you want the request to execute on. Select Run API Request, choose the relevant request, and Save your Action.

Was this article helpful to you? Yes No

How can we help?