Geraint White
Geraint White
This issue is really annoying. Has anyone got an update or are we still required to rename our imports?
The irony is that 5.0.0 doesn't have the darwin arm64 binaries uploaded so the build fails on the M1 host 🤷♂️
I have version 5.0.1 in my package.json for use on macOS (M1 and x86) and put the following line in my Dockerfile. ``` RUN npm install [email protected] ```
Can we Upgrade the old project version to the latest version 0.69 without adopting new architecture?
I am also interested in knowing this. I attempted upgrading from 0.68.2 -> 0.69.1 without using the new architecture and encountered lots of build issues so shelved it for another...
Can we Upgrade the old project version to the latest version 0.69 without adopting new architecture?
> im in the middle of updating a project from 0.68 to 0.69 and i have not enabled new architecture. so it should be possible. Have you got both Android...
Is there any solution to this? I'm trying to use the library in a react native project which has the android project in a subfolder of the repo.
`@grit96/react-native-proximity` is my fork of the project that includes https://github.com/williambout/react-native-proximity/pull/13 and https://github.com/williambout/react-native-proximity/pull/20 to make the module work properly.
I use the module with `react-native` 0.59.x but there are some other pull requests relating to 0.60+ support which you might need to implement.
@williambout this is important to get merged because without it the app will crash on iOS 13.
In the meantime I've published a fork including those two pull requests under [@grit96/react-native-proximity](https://www.npmjs.com/package/@grit96/react-native-proximity).