setPermission probably doesn't work, WDA stops about appium-ios-simulator HOT 10 CLOSED

Thanks @KazuCocoa . That was the reason why I needed more extensive testing. It might the idea with mobile commands won't work at all and it will be necessary to perform perms adjustments on session startup stage before WDA init.

Anyway. This stuff will require more work.

FYI @dpgraham

from appium-ios-simulator.

@KazuCocoa Can you please try #190 ?

from appium-ios-simulator.

cc @mykola-mokhnach

from appium-ios-simulator.

@mykola-mokhnach
Thanks and sorry, the current logic worked as same as #190 . My scenario was wrong...
(So, the 2 and 3 in the description was my bad.)
https://github.com/appium/ruby_lib_core/pull/160/files#diff-642294321e09de07e102867a6bd7e804R18 is fixed version.

from appium-ios-simulator.

Resetting simulator happens in both way. So, we need to re-connect WDA session after the permission change as you addressed the above.

from appium-ios-simulator.

So there are two question:

• Does the previous implementation (direct access to TCC) work the same as the one, that uses WIX tools?
• restarting the springboard service also resets WDA?

from appium-ios-simulator.

Does the previous implementation (direct access to TCC) work the same as one, that uses WIX tools?

Yes.

restarting the springboard service also resets WDA?

Yes. For example, after setPermission, below error happened.

@@driver.switch_to.alert.text
Selenium::WebDriver::Error::UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to remote server. Original error: Error: connect ECONNREFUSED 127.0.0.1:8100
from UnknownError: An unknown server-side error occurred while processing the command. Original error: Could not proxy command to remote server. Original error: Error: connect ECONNREFUSED 127.0.0.1:8100

Even @@driver.execute_script('mobile: getPermission', {service: 'calendar',bundleId: 'com.example.apple-samplecode.UICatalog'}) worked. (Since the getPermission worked for simulator directly.

from appium-ios-simulator.

Yes. For example, after setPermission, below error happened.

This means it will be necessary to remove setPermission mobile command and move it to capabilities, so we can set permissions before WDA init, but after AUT is installed. getPermissions can be kept though.

Thanks for your assistance

from appium-ios-simulator.

Exactly 👍

from appium-ios-simulator.

I think having it as a capability is a better approach anyway.

from appium-ios-simulator.