Tomáš Martykán
Tomáš Martykán
To keep the default behavior the same as before, so we don't accidentally break anything. The goal is to make it default, but after testing it as opt-in
The inline build is fine due to our tree shaking, but if you import `connect-web` as a module in some external project and use default webpack settings, you will get...
It seems only necessary request is 1x `getAccountInfo` to get the owner, but it's making a bunch more. Maybe we can re-use `details: 'basic'` to do exactly this?
We can probably skip this, I found a way to do this in Playwright by proxying requests https://github.com/trezor/trezor-suite/pull/13031/files#diff-5b46eb0967298a9da65edf50f48035404d32ffec1dcb49dfece3565799117ae7R10
We fixed a race condition in our handshake process, which was happening when doing 2 calls subsequently, as is the case here when connecting the device (getFeatures, cardanoGetPublicKey). It was...
Closing as stale, we haven't had recent reports of this issue
Regarding Sentry, I don't think it's an actual uncaught exception, it's just that Chrome shows failed network requests in the log. I don't see any requests going to Sentry about...
I believe we can test iOS as well, it should work on both with the emulator.
So I attempted to adjust the test for iOS, however there are some issues during onboarding and coin enabling, which block the progress of the test: ``` The app is...
Ok, understandable, but currently all the iOS tests don't match the real behavior of the app. When I build and run `ios.sim.release` tests, it's actually using the Debug variant, which...