Hello, this is a follow up on a problem we have on iPhone 7 that is still unresolved:
It’s been over 4 months that the issue has been escalated to the engineering team and the issue still persists. Can-we have a status update?

Hello, this is a follow up on a problem we have on iPhone 7 that is still unresolved:
It’s been over 4 months that the issue has been escalated to the engineering team and the issue still persists. Can-we have a status update?
Hi
Hello Jeffrey. Kindly check on this with your colleague Kaitlin, with whom we're having an email exchange. My understanding is that a reply of ours sent to you in November, with a code snippet as requested by your support team, was somehow lost or disregarded. We also find it difficult to interact properly with your team owing to what looks to me as "suboptimal” support ticket management or access - to put it lightly. If you give me your email, I'll gladly send you a copy of my last email to Kaitlin, and keep you in the loop. We have been awaiting since last November for resolution of an issue that we reported then… Thanks for helping out in solving this.
Hi
Hi, just letting you know that we’re still waiting for your reply. So do not close this issue as resolved.
Hi
As you are using two different versions for the SDK, react-native-purchases 8.9.2 and react-native-purchases-ui to 8.9.3, this could be causing problems. Can you please make sure these versions match as this mismatch could be causing the problem? We are currently on 8.9.5, please make sure both purchases and purchases-ui are upgraded to this same version: https://github.com/RevenueCat/react-native-purchases/releases/tag/8.9.5
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.