Not sure if this is a bug. I started using launch arguments in my Maestro tests, and I'm finding that they persist such that after I kill the app and start it up again (using expo start --clear) the arg from the test is still present. I'd rather not have to set default values for them everywhere that the app might be launched. Is this expected behavior? Is there a way to clear the args? My initial thought is an onCompleteFlow step that just relaunches the app with default values but curious if there's a better way. I am developing for iOS, launching on Simulator. (As expected, using expo run:ios does clear the launch arguments).
Not sure if this is a bug. I started using launch arguments in my Maestro tests, and I'm finding that they persist such that after I kill the app and start it up again (using
expo start --clear
) the arg from the test is still present. I'd rather not have to set default values for them everywhere that the app might be launched. Is this expected behavior? Is there a way to clear the args? My initial thought is anonCompleteFlow
step that just relaunches the app with default values but curious if there's a better way. I am developing for iOS, launching on Simulator. (As expected, usingexpo run:ios
does clear the launch arguments).