Closed ApplebaumIan closed 3 years ago
What's super strange about this bug is that it doesn't appear on the example App...
@ApplebaumIan Did you find out what the issue was? I'm currently experiencing the same error.
@tijme Unfortunately no, I've had to work on other things. I've been just monkey testing my app in iOS 13 for now. 😪
@ApplebaumIan Did you find out what the issue was? I'm currently experiencing the same error.
@tijme Can I ask you a few question since it seems like this is a dead or dying project? Are you using parallel testing, XCTest Plans, or testing an iPad App in landscape?
@tijme I FINALLY GOT THE EXAMPLE TO BREAK. The issue is that the example is on the latest version of swift monkey on master. So I switched it to using pods and installed version pod 'SwiftMonkeyPaws','~> 2.1.0'
and the example app breaks.
@zalando please add a new version tag as 2.1.1 is 11 commits behind master.
Thank you very much for finding the cause of this issue! I have drafted a new release (2.2.0). I also left a comment in your PR @ApplebaumIan. After we merge it, I will push the new Podspec
to CocoaPods.
@wojciechczerski Glad to hear it and happy to help! Swift Monkey is a really great tool! Glad I can keep it in my test suite🕺
@ApplebaumIan @tijme I have pushed SwiftMonkey 2.2.0
to CocoaPods trunk.
Thank you for the time and effort you spent on this issue @wojciechczerski & @ApplebaumIan. I am sure you have helped many developers with this fix!
I am still facing this issue on Xcode 12 iOS 14.4 even after pointing to 2.2.0. @ApplebaumIan @zalando
I am still facing this issue on Xcode 12 iOS 14.4 even after pointing to 2.2.0. @ApplebaumIan @zalando
Does it work if you replace this monkey.addDefaultUIAutomationActions()
by monkey.addDefaultXCTestPublicActions(app: ...)
?
That will work. But that is not expected requirements @tijme
When running Monkey Tests on iPadOS 14 targets
eventGenerator.sendPinchCloseWithStartPoint
results in aThread 1: EXC_BAD_ACCESS (code=1, address=0x0)