micahdasMA

Has there been any movement on this issue? I am hitting an issue on iOS where it gives the error ``` Property 'elements' does not exist on type 'IosElementAttributes |...

@asafkorem I still get a ts error after updating to 20.12.0 Code `const appElementAttributes = await element(by.id(appElement)).getAttributes(); jestExpect(appElementAttributes.elements.length).toBe(expectedCount);` Error `Property 'elements' does not exist on type 'IosElementAttributes | AndroidElementAttributes |...

I am also experiencing this when trying to use `--maxworkers 5` on Bitrise CI Here is the relevant section of the bitrise.yml ``` - npm@1: inputs: - command: run e2e:build...

@noomorph Have you been able to take a look at this issue?

@noomorph Yes you are right, I forgot to add the `npx`, but after I updated the bitrise.yml file, I continue to get the original error @adamivancza can you share your...

Thanks! I had distinct steps to reset the lock file and to run the tests, but adding them together in a single step seems to do the trick!

I may have spoken too soon! While the tests now indeed run with multiple workers, it seems that they consistently are not able to launch properly, with the issue I...

@noomorph I am running it in debug mode w/ the Metro bundler on CI.

I'm also experiencing this

@noomorph I think that would do exactly what I want! Thanks for sharing. In the meantime, I will see what I can do with the app protocol handlers.