Hwee-Boon Yar
Hwee-Boon Yar
Does this work for chains other than mainnet? Otherwise OpenSea covers this right?
Ok. Lower priority?
As in the 2nd transaction becomes pending and is stuck there, but the original transaction completed? But either way the transaction status for both should be picked up, right? Maybe...
I think we shouldn’t. This is as a failover? Because it might not be able to support our load. Read load > write.
@oa-s I see this sometimes. And sometimes tapping on the textbox doesn't focus on it at all, and then I think I have to kill the simulator to fix it...
Then *maybe* it will manifest on device with a hardware keyboard.
Who do we show the warnings to?
See if the modified title reflects what you mean?
It's definitely Safari for me. If I kill Safari, `.windows()` is fast, otherwise it takes 6-17 seconds. (`.windows({ visible: true })` takes a similar amount of time)
I'm using Ruby 2.3.1 via RVM for RubyMotion, but on macOS 10.12.6. Is there an easy way to reproduce the issue?