From 846d8be0164b7655b8a3a95779b722eaeda34ace Mon Sep 17 00:00:00 2001 From: Justin Poliachik Date: Wed, 7 Feb 2024 16:11:45 -0500 Subject: [PATCH] fix: add expo instructions to maestro setup (#122 by @Jpoliachik) --- docs/recipes/MaestroSetup.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/recipes/MaestroSetup.md b/docs/recipes/MaestroSetup.md index 7d37d97f..bc921f65 100644 --- a/docs/recipes/MaestroSetup.md +++ b/docs/recipes/MaestroSetup.md @@ -68,7 +68,7 @@ We're using a few different actions and assertions in this flow. Let's take a lo `assertVisible` - This assertion checks to see if the text we pass in is visible on the screen. `tapOn` - This action taps on the specified element. In our case, we're tapping on the text we pass in. -To run our flow, first make sure the app is loaded on the simulator (or running via metro through `yarn ios`, for example). Then execute maestro from its test directory with the following command: +To run our flow, first make sure the app is loaded on the simulator or running via metro through `yarn ios`. If you're using Expo Go, you'll need to do a development build in [Expo CNG](./SwitchBetweenExpoGoCNG.md) first. Then execute maestro from its test directory with the following command: ```bash cd .maestro