You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 16, 2024. It is now read-only.
implementation "com.facebook.react:react-native:+" // From node_modules
line is no where to be found, so the replace fails and the firebase implementation never gets added.
In RN 0.71 and beyond, it seems that React Native Gradle Plugin is being used and instead of the above line, inserts this line in the build.gradle instead:
Then the Firebase implementation gets inserted and notifications work like they should.
What do you guys think would be the best way to fix this? Should we search for either of the anchors and add the firebase line if either are found? Use regex? Just hoping I can avoid forking the repository and hosting it myself :)
Thanks!
The text was updated successfully, but these errors were encountered:
"react-native": "0.72.5",
"expo": "^49.0.0",
"@intercom/intercom-react-native": "4.0.1",
"config-plugin-react-native-intercom": "^1.10.1",
I have been unable to get Android notifications working for Intercom, and finally found the issue today.
In this library's
withIntercomAndroid.js
, the code for inserting the Firebase implementation in thebuild.gradle
is the following:However, in my generated
build.gradle
, theline is no where to be found, so the replace fails and the firebase implementation never gets added.
In RN 0.71 and beyond, it seems that React Native Gradle Plugin is being used and instead of the above line, inserts this line in the
build.gradle
instead:So, if I change the anchor line above to this:
Then the Firebase implementation gets inserted and notifications work like they should.
What do you guys think would be the best way to fix this? Should we search for either of the anchors and add the firebase line if either are found? Use regex? Just hoping I can avoid forking the repository and hosting it myself :)
Thanks!
The text was updated successfully, but these errors were encountered: