[eas-shared] Ignore osascript error when launching on Simulator #139
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alanjhughes
approved these changes
Jan 17, 2024
gabrieldonadel
deleted the
@gabrieldonadel/fix-accessibility-access-error
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Why
In some very specific cases, the user may encounter an error stating that
osascript is not allowed assistive access. (-1719)when trying to launch a build in the simulator. This only happened once to me, I tried to reproduce this in different machines and unfortunately couldn't find reproducible stepsHow
Add a try-catch block around the osascript call given that we can safely ignore this error and just continue with the launch of the app
Test Plan
Run the app locally and launch a simulator build from the website