Comment on page
Known Issues
Unfortunately, Maestro does not yet have Android support of
inputText commands that have unicode characters in them (follow this GitHub issue for status updates). Only ASCII characters are supportedSometimes, tapOn will try to tap again if it doesn't detect a hierarchy change. To fix such cases, use
retryTapIfNoChange. For example:- tapOn:
text: "Some Button"
retryTapIfNoChange: false
Either the app is not installed or the
appId is wrong. Note that depending on the app type, the identifier can be different.To find the appID you can perform the following:
On Android:
- 1.Execute
adb shell pm list packagesto get a list of all installed packages. - 2.Search for the appID manually or use
grepin the above command to search for part of the name:adb shell pm list packages | grep <name>
On iOS
- 1.Execute
xcrun simctl listapps booted | grep CFBundleIdentifierto get a list of all installed packages - 2.Search for the appID manually or use
grepin the above command to search for part of the name:xcrun simctl listapps booted | grep CFBundleIdentifier | grep <name>
On iOS,
hideKeyboard is done with the help of scrolling up and down from the middle of the screen since there is no native API to hide the keyboard. If using this command doesn't hide the keyboard we recommend clicking on some non-tappable region with
tapOn points command, similar to how a user would hide the keyboard when interacting with your app.Apps that have pagination (fetch data on scroll) inside UITableView / UICollectionView views sometimes result in fetching data at the moments when it is not expected, hanging inside the lists, and flows being broken when testing with
maestro.
There is a bug in XCTest framework that makes UITableView / UICollectionView willDisplayCell method being called whenever UI test APIs are being called. Since maestro relies on XCTest APIs under the hood it might break the pagination logic for some apps.
Suggested workaround - inside willDisplayCell check whether the indexPath is really visible via UITableView.indexPathsForVisibleRows or UICollectionView.indexPathsForVisibleItems. Code example:// This function should be implemented in a class conforming to UITableViewDelegate
// in case of UICollectionView `collectionView(_:willDisplay:forItemAt:)` from
// UICollectionViewDelegate should be used
func tableView(_ tableView: UITableView,
willDisplay cell: UITableViewCell,
forRowAt indexPath: IndexPath) {
// additional check whether the cell is currently visible or not is needed
// to make sure calls caused by XCTest or other random tableView reloads
// do not unintentional data fetch request
guard let visibleIndexPaths = tableView.indexPathsForVisibleRows,
visibleIndexPaths.contains(indexPath),
<additional checks that were previosly there> else { return }
print("load new data..")
}