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
In my app I'm listening to didActivateApplicationNotification notifications and then add AXObserver to the app that was activated.
I've noticed that in some scenarios I got UnknownUIElement errors when I was trying to add an observable right after launching Chrome.
I think this is due to the fact that chrome has isFinishedLaunching = false when activated.
The solution for me is to listen for another additional event (didLaunchApplicationNotification), but you may want to consider adding a check for isFinishedLaunching in Application initializers.
The text was updated successfully, but these errors were encountered:
tmandry
changed the title
UnknownUIElement when using Chrome immediately after launch
Check for isFinishedLaunching when initializing an Application from NSRunningApplication
Apr 13, 2019
Thanks, I'll consider it. I don't know if that behavior is documented anywhere so I can verify I'm doing the right thing, but that's true for a lot of aspects of these APIs.
If initialized with only a process ID, we should document that we don't check this, either.
In my app I'm listening to
didActivateApplicationNotification
notifications and then addAXObserver
to the app that was activated.I've noticed that in some scenarios I got
UnknownUIElement
errors when I was trying to add an observable right after launching Chrome.I think this is due to the fact that chrome has
isFinishedLaunching = false
when activated.The solution for me is to listen for another additional event (
didLaunchApplicationNotification
), but you may want to consider adding a check forisFinishedLaunching
inApplication
initializers.The text was updated successfully, but these errors were encountered: