Allen Kinzalow
Allen Kinzalow
Thanks @nadetastic, we've split up our function containing this snippet and will log the errors of both. I will report the results. Thanks!
@ankit-tailor Any news on this fix?
> 👋 @akinzalowevidation Have you found anything since your last update? Hi @tannerabread we are still following this but have made one observation: We recently switched from `react-native-secure-storage` to `react-native-mmkv`...
@nadetastic We are still experiencing this problem, but I do have an update: Here is how we are now obtaining an access token in production: ```js import { Auth }...
> Is that Expo-specific? @boorad Yes, a managed Expo application. We were previously on `0.6.1` with no issues until issue #241 started happening. I don't think downgrading OpenSSL, the alternate...
> I get that, and I am suggesting use the release candidates, not downgrade. But why does Expo need the extra `../../` on your include_directories paths? If dependencies are installed...
@boorad Does #303 also fix this issue for iOS?
@daniel-moya I discovered that this issue was happening due to improper mocking of `react-native-safe-area-context`. Adding the following to mocks fixed the issue for me: ``` import mockSafeAreaContext from "react-native-safe-area-context/jest/mock"; jest.mock("react-native-safe-area-context",...
Is there a reason this was never merged?
I am also experiencing this issue.