fix: SDCB-12186 Fixes wdarun support on random iOS 13 device submodels #3
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* feat: Polish and fix the NPM package * fix root path * missing await
…code (danielpaulus#397) The test-to-skip argument was not working, while test-to-run was just fine (they are both using XCTTestIdentifier internally). One issue was that Xcode sets to options field to 2 and not 6 when both a class-name and a method-name are specified. Also, Xcode doesn't use the module parameter anymore.
Starting with iOS 17 XCUITest logs are sent over two channels. There are debug logs that come over the DTX connection (like they did in the past), but the non-debug messages are sent over a different connection to the com.apple.coredevice.openstdiosocket service. We now open a connection to the openstdiosocket-service before we launch the test runner, and we tell the appservice to which socket it should connect stdio. And after that we pipe the data we get from the stdio-socket to the logoutput.
this was somehow lost in refactoring
The current setlocation only works for iOS below 17, the iOS 17 introduces a new instrumentation service com.apple.instruments.dtservicehub with the channel id com.apple.instruments.server.services.LocationSimulation for the simulated location. Co-authored-by: fish-sauce <[email protected]>
With this changes ios runwda will exit with error when WDA app dies (e.g. killed with ios kill, killed manually with AppSwitcher, or when iPhone is turned off). dtxConnection's BreakdownCallback is implemented with Functionals Options Pattern, so it's fully optional and shouldn't affect any other dtxConnection usages.
* feat: add rsd instrumentation service support * docs: describe DeviceEntry.SupportsRsd * refactor: replace direct checking DeviceEntry.Rsd with helper method
This fixes error: `Pairing failed: err="pkcs7: cannot decrypt data: only RSA, DES, DES-EDE3, AES-256-CBC and AES-128-GCM supported"` While using an elliptic curve certificate for pairing. The old (2019) fullsailer/pkcs7 seems abandoned, mozilla forked it. This version also has support for elliptic curves: OIDEncryptionAlgorithmECDSAP256 OIDEncryptionAlgorithmECDSAP384 OIDEncryptionAlgorithmECDSAP521 Besides RSA and DES. Co-authored-by: renini <renini@local> Co-authored-by: danielpaulus <[email protected]>
* Refactor IO operations in Go code * compiler error fix. Should remove later
This fixes error: `pkcs12: unknown digest algorithm: 2.16.840.1.101.3.4.2.1` while using an p12 cert for pairing which is hashed with the sha256 algorithm. This package is forked from golang.org/x/crypto/pkcs12, which is frozen. Co-authored-by: renini <renini@local> Co-authored-by: danielpaulus <[email protected]>
Co-authored-by: danielpaulus <[email protected]>
* Add tunnel API delete. Co-authored-by: danielpaulus <[email protected]>
michal-przytarski
changed the title
Use lockdown tunnel proxy by default for devices >17.4 Add support for Windows --------- Co-authored-by: [email protected] <[email protected]>
the TUN interface often returned an error when an incomplete IPv6 packet was sent (one IPv6 packet + parts of the next one) sending one packet at a time resolved this issue
* add fat ios binary for mac m1 and amd64 for now
the close call happens in multiple places and we can not be sure that only one of those methods is getting called during an execution
* the defragmenter was not cleaned up completely after the last fragment * clone strings from the XCTAttachments object without cloning them the whole XCTAttachment and XCActivityRecord struct is being kept in memory
…anielpaulus#417) This PR removes the need for starting a tunnel with sudo using gVisor's user space networking stack. `ios tunnel start --userspace` will start a userspace only networking stack that will work without sudo and you can use devices. Pairing does not yet work here, will look into it next. `sudo ios tunnel start` will use normal OS TUN devices for this as before. There is now an experimental mode to automatically start go-ios tunnel management. If you set the `ENABLE_GO_IOS_AGENT` env var to `yes` it will automatically start the tunnel manager agent and you can run commands without any prep.
Rename --enabletun to --userspace
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.