QuaOs

> > Hi. > > Also run into this issue. Here is my [reproduction repo](https://github.com/quaos/test-expo-ssl-pinning-1/tree/with-expo-dev-client-updates) with Expo SDK 49.0 + expo-dev-client v2.4.12 > > I just tried downgrading expo-dev-client to...

### UPDATE I've created a test repo in attempt to reproduce the issue, but still can't: [test-expo-ssl-pinning-1](https://github.com/quaos/test-expo-ssl-pinning-1) My latest investigation revealed that the execution does not enter TrustKit's `[TSKPinningValidator handleChallenge:completionHandler:]`...

***UPDATE: As of 11.10.2022, the workaround above stopped working after new changes to another model interface*** ``` GenerateMetadataError: No declarations found for referenced type DeepPartial in 'MyItemsApiController.updateItem ```

Also run into this randomly with Jest v29.5.0 . There was not "Logging after tests" message, but found this in between the tests: ``` (node:66) MaxListenersExceededWarning: Possible EventEmitter memory leak...

> @cristian1206 > > Thanks for the investigation into the issue. Indeed, iOS maintains a session cache, which re-uses connections if they've been made successfully before. This is detailed in...

@frw @cristian1206 ### UPDATE Here is my latest attempt to fix this: * Call `initializeSslPinning` in the very entrypoint of the app (`index.ts`), before calling Expo `registerRootComponent` * Share the...

@cristian1206 > Hello @quaos . I have the following questions: > > 1. If you do not initialize truskit and make a request to the domain that does not work...

#### UPDATE I've created a test repo in attempt to reproduce the issue, but still can't: [test-expo-ssl-pinning-1](https://github.com/quaos/test-expo-ssl-pinning-1) However, I could successfully run the original project with debugging in XCode (it...

### UPDATE Here are the latest log and stacktraces, showing that in the original repo the app execution does not enter TrustKit validator methods at all: #### Test Repo (entering...

### UPDATE Upon deeper investigation, I found that NONE of these **network delegate methods** existing in the original repo is getting called: * `react-native-ssl-public-key-pinning > SslPublicKeyPinning.m > RCTHTTPRequestHandler (SslPublicKeyPinning).didReceiveChallenge` *...