You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using the system.element(by.system.label("Allow")) method that was released two weeks ago is almost useless unless your app is built to conform to this. We login and the privacy alert is shown but there's some delay and no way to account for the delay other than a hard wait.
Above is not accepted due to 'Argument type IndexableSystemElement is not assignable to parameter type NativeElement' we should be able to call waitFor on this method since there's no way to precisely expect an iOS system alert.
What was the expected behaviour?
Ideally you would be able to wait until the alert is shown using other methods.
Was it tested on latest Detox?
I have tested this issue on the latest Detox release and it still reproduces.
@noomorph@APrincipe21This is not a bug. This usage is invalid. System APIs can't be used with waitFor.
This can be an enhancement request, so I'll keep this open with new labels + contributions are welcome :)
TBH, I need to see it with my own eyes, other dialogs that we test on our test-app doesn't have this issue..
For now, if you have to, you can do a busy-sleep or implement some try-catch mechanism as a workaround.
What happened?
Using the
system.element(by.system.label("Allow"))
method that was released two weeks ago is almost useless unless your app is built to conform to this. We login and the privacy alert is shown but there's some delay and no way to account for the delay other than a hard wait.Above is not accepted due to 'Argument type IndexableSystemElement is not assignable to parameter type NativeElement' we should be able to call waitFor on this method since there's no way to precisely expect an iOS system alert.
What was the expected behaviour?
Ideally you would be able to wait until the alert is shown using other methods.
Was it tested on latest Detox?
Did your test throw out a timeout?
Help us reproduce this issue!
No response
In what environment did this happen?
Detox version:
React Native version:
Has Fabric (React Native's new rendering system) enabled: (yes/no)
Node version:
Device model:
iOS version:
macOS version:
Xcode version:
Test-runner (select one): jest / other
Detox logs
Detox logs
Device logs
Device logs
More data, please!
No response
The text was updated successfully, but these errors were encountered: