GUI objects can contain other GUI objects. For example a window can contain buttons. When recording a click on these buttons, the expected behavior is that Squish generates object names for these buttons, and that it uses these object names in the recorded script commands.
However, there are cases where it is not easy to decide on a technical level which object should be recorded on, even though the case seems absolutely obvious to the user. As a result (regarding aforementioned example) Squish might record a mouse click on the window object instead.
In Squish for iOS there are a number of such cases, too, where Squish does not drill down into all types of GUI objects to find the deepest/lowest (actually the "most suitable") GUI object when recording.
We plan to improve this over time but first have to analyze typical use cases and make a bunch of technical decisions before we can proceed.
If the recording ends up using the "wrong" object, but the behavior is correct upon replay, feel free to leave the respective command (and object name used in it) as is.
If the recording ends up using the "wrong" object, and the behavior is incorrect upon replay, you can do the following:
Set breakpoint on the respective line of code and execute to it.
Pick the respective wrong object.
Expand its node in
Application Objectsand find the desired object in the tree.
Right click on the desired object node, copy the object name and change the respective line of code to use this other object name instead.