Xcode 9 beta 6 : xcuirunner not able to auto-manage System dialog to enable push notifications
| Originator: | nagarkarchetan | ||
| Number: | rdar://34115792 | Date Originated: | 8/28/2017 |
| Status: | Open | Resolved: | No |
| Product: | XCUITest / Xcode | Product Version: | Xcode 9.0 beta 6 (9M214v) |
| Classification: | Bug | Reproducible: | Always |
I have been using XCUITest for UI tests in Xcode 8 since few months. Xcode 8 had a feature where a system dialog of this type would be handled automatically in the test: "XYZ app" would like to send you push notifications. Xcode 8 would auto-click 'Don't Allow' button in this dialog for me, which was perfect. Now, I have been using beta releases of Xcode 9 (currently using beta 6). This behaviour is not supported anymore. The test gets stuck at the System Dialog to allow push notifications. Users are being stuck and forced at writing their own UIInterruption handler. It would be highly appreciated if the XCTest team can handle this issue before the GA release of Xcode 9 (or next beta). Thank you! Steps to Reproduce: 1. Uninstall app if app instance is installed 2. Run UI test using XCTest for an app that requires push notifications.(This system dialog may be about push notifications, location, etc.) 3. Let the push notification system dialog appear when test runs after installing test runner, and target app. Expected Results: Test runner auto dismisses (or auto-accepts) the system dialog. Observed Results: Test runner is stuck at the system dialog, and test cannot proceed. Users are being forced to write their own handlers to handle the system dialog. Version: 10.3.2 Notes: Configuration: Xcode 9.0 beta 6 (9M214v) macOS Sierra 10.12.6 (16G29) Running tests on an iPhone SE
Comments
Please note: Reports posted here will not necessarily be seen by Apple. All problems should be submitted at bugreport.apple.com before they are posted here. Please only post information for Radars that you have filed yourself, and please do not include Apple confidential information in your posts. Thank you!
This was fixed in Xcode 9.0 release build