# Input Value keyword from Appiumlibrary example using Robotframework

**URL:** <https://forum.robotframework.org/t/input-value-keyword-from-appiumlibrary-example-using-robotframework/7870>\
**Category:** Libraries\
**Created:** [3 October 2024 18:16 UTC](https://forum.robotframework.org/t/input-value-keyword-from-appiumlibrary-example-using-robotframework/7870 "2024-10-03T18:16:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![georgala](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/georgala/32/3387_2.png) [@georgala](https://forum.robotframework.org/u/georgala)\
**Post date:** [3 October 2024 18:16 UTC](https://forum.robotframework.org/t/input-value-keyword-from-appiumlibrary-example-using-robotframework/7870/1 "2024-10-03T18:16:27Z")

</div>

Could anyone give me an example of Input Value keyword usage?  
Im using this format:

`Input Value //XCUIElementTypeTextField[@index="3"] subscriberid`

and im getting the following exception:

```python
InvalidArgumentException: Message: The following required parameter is missing: ["text"]
Known required parameters are: ["text"]
You have provided: ["id","value"]

```

Any idea about the correct format?

---

<div class="post-metadata">

**Author:** ![HelioGuilherme66](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/helioguilherme66/32/34_2.png) [@HelioGuilherme66](https://forum.robotframework.org/u/HelioGuilherme66)\
**Post date:** [4 October 2024 08:50 UTC](https://forum.robotframework.org/t/input-value-keyword-from-appiumlibrary-example-using-robotframework/7870/2 "2024-10-04T08:50:53Z")

</div>

The documentation says it is an iOS only keyword. There is other one with the same function, which is `Input Text`.

 ![image](https://europe1.discourse-cdn.com/flex005/uploads/robotframework1/original/2X/9/9c2f0a9f60d4f481f3c44d2f3dc4cb34404df79a.png)  
[Input Value](https://serhatbolsu.github.io/robotframework-appiumlibrary/AppiumLibrary.html#Input%20Value)

You can try to explicitly pass the named argument:

```robotframework
Input Value //XCUIElementTypeTextField[@index="3"] text=subscriberid

```

---

<div class="post-metadata">

**Author:** ![georgala](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/georgala/32/3387_2.png) [@georgala](https://forum.robotframework.org/u/georgala)\
**Post date:** [4 October 2024 10:51 UTC](https://forum.robotframework.org/t/input-value-keyword-from-appiumlibrary-example-using-robotframework/7870/3 "2024-10-04T10:51:40Z")

</div>

Hello,  
I used Input Text until i upgrade my iPhone 12 (real device) to iOS 18.0. Through Quicktime player i can see from the case execution that robot types the text exactly at the text field but when im moving to the next screen the result isnt the expected. If im going to type it manually through my keyboard then all fine. Thats why i want to try through Input Value keyword.  
I tried this syntax:  
`Input Value //XCUIElementTypeTextField[@index="3"] text=subscriberid`  
but the exception message was the same. Also note that from the Appium inspector there are no ‘text’ attribute available.

---

<div class="post-metadata">

**Author:** ![HelioGuilherme66](https://dub1.discourse-cdn.com/flex005/user_avatar/forum.robotframework.org/helioguilherme66/32/34_2.png) [@HelioGuilherme66](https://forum.robotframework.org/u/HelioGuilherme66)\
**Post date:** [4 October 2024 12:59 UTC](https://forum.robotframework.org/t/input-value-keyword-from-appiumlibrary-example-using-robotframework/7870/4 "2024-10-04T12:59:51Z")

</div>

I can only think that `subscriberid` is being interpreted as a Python variable. (maybe you used some real text, then just ignore what I’ve written).

Maybe the actual XCUITEST command had changed for that version, and AppiumLibrary is not updated to it.

You could try to use XCode/XCUITEST (whatever iOS tool exist for testing) to simulate that input.

Other experience, would be to:

- activate the input element
- open the iPhone keyboard
- type the content

(I really don’t know how or if possible)

Finally, as a last resort, make your test semi-automated, by adding a pause, and input the content manually, so other steps could proceed.
