-
We are kind stuck with react-native 0.59 and planning to use notifee. Documentation says its untested on older react-native but I'm willing to try it out. But due to no Auto-link feature - I'm having trouble to get start. Any idea on how can I figure out what the autolink does and I'll try those changes manually to manual link the library? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
There is no support for react-native that old, and it's not something we are likely to support. In general we'll try to go down to 0.63 and that's about it. I can't imagine they'll work well at all, specifically: you need Android API31 symbol access to use this package, that requires gradle 7 tool chain for various reasons, and gradle 7 requires at least react-native 0.64 if I recall correctly. You can patch around all of these by ingesting the specific changes that make everything work but that's a tremendous waste of time vs investment in getting current, in my opinion. |
Beta Was this translation helpful? Give feedback.
-
Hi related to this, due to quite a different project structure that my react-native app has, I am wondering is it possible to use manual linking instead of auto linking? My react native app version is 0.65.1 though. |
Beta Was this translation helpful? Give feedback.
There is no support for react-native that old, and it's not something we are likely to support. In general we'll try to go down to 0.63 and that's about it. I can't imagine they'll work well at all, specifically: you need Android API31 symbol access to use this package, that requires gradle 7 tool chain for various reasons, and gradle 7 requires at least react-native 0.64 if I recall correctly.
You can patch around all of these by ingesting the specific changes that make everything work but that's a tremendous waste of time vs investment in getting current, in my opinion.
https://react-native-community.github.io/upgrade-helper/