Some native applications are developed in a way that can prevent the Recorder from recording a script or from playing back successfully.
In some cases, resolving playback issues requires coding changes in the script that can only be performed by the mobile application developer.
Isolating playback problems
If you encounter playback errors but cannot identify the problem, you can try to record the script using another tool, such as Charles Web Debugging Proxy Application. Charles Proxy records and displays all of the data that is sent and received, so you may be able to identify the areas of the application that prevent it from being recorded and possibly create a workaround.
Workarounds when playback fails
This section provides some examples of working around the additional security implemented in native applications during playback.
When you record a script, cookies are captured and stored and used during playback. Often cookies expire and are no longer valid after the initial recording session. Delete all of the cookies stored during recording before playback. For more information, see Managing cookies.
Cookies can be stored in multiple actions in the script, so make sure to delete all instances. This ensures that new cookies are captured each time the script is run.
Insert code for handling dynamic content
For added security, some applications use session tokens or other IDs that can only be used once. In some cases, handling these IDs requires inserting code into the script so that a new token or ID is captured during each subsequent playback of the script. For more information, see Handling dynamic content.