Nic Wise

turns out you have to manually pass them all thru. ``` - path: - "paths-here/" config: trigger: "thing-to-trigger" build: env: - BUILDKITE_PULL_REQUEST - BUILDKITE_PULL_REQUEST_BASE_BRANCH - BUILDKITE_PULL_REQUEST_REPO ```

related to https://github.com/oblador/react-native-keychain/issues/567 I think :(

Seeing this error on Android 13 (pixel) but not a lot of other places. We can move to FB, but that'd require all of our users to either sign back...

Interesting. Our one user who can reproduce it has bio enabled (finger). (we have a load of customers with the problem, but only one test device we can reproduce it...

I've FINALLY managed to get the device we had failing (as well as a bunch of customer devices). Pixel 5 + Android 13. I also have a Pixel 6a +...

oh the irony :) ``` // decrypt the bytes using cipher.doFinal(). Using a CipherInputStream for decryption has historically led to issues // on the Pixel family of devices. // see...

OK, I'm 99% sure I've found the problem. On this device, we fail to generate an RSA key cos reasons: ``` RNKeychainManager: warming up started at 1053735047449122 RNKeychainManager: Probe cipher...

Further to this. 2 devices. Pixel 6a + 13, Pixel 5 + 13 Both fail to generate the RSA key. Same error around keysize. However, the 6a (which largely works)...

so.... merge? not merge?

Any movement/change on this? We hit it with a customer who's phone's clock was 10-15 mins in the future (no, I dont know why...) We are using it for storage,...