Package "@notifee/react-native" does not contain a valid config plugin. #799

MaxAst · 2023-06-20T08:21:01Z

I've started getting this error today

Package "@notifee/react-native" does not contain a valid config plugin.
Learn more: https://docs.expo.dev/guides/config-plugins/#creating-a-plugin

Cannot use import statement outside a module
    Error: build command failed.

when running expo start -c or eas build. AFAIK, I haven't made any changes that could have led to this error

The text was updated successfully, but these errors were encountered:

leggomuhgreggo · 2023-06-21T01:15:22Z

Looks like the plugin directory has been deleted in version 7.8.0

Actually -- now that I look at the actual config plugin code that was removed -- I'm wondering if the idea is tha the config plugin isn't really needed anymore?

I don't see anything called out in the changelog

Might even suggest keeping a shim file, that prints a deprecation warning -- just to avoid the abruptness. Also these docs may need to be update

MaxAst · 2023-06-21T05:00:41Z

@leggomuhgreggo I think you're right. I removed the notifee config plugin from my app.config.js and everything is working fine so far. Tried it with a development build and a production build

MaxAst · 2023-06-21T05:02:45Z

@helenaford is this expected? If so, shall I create a PR to update the docs saying that for expo projects no further action is required after npm/yarn/pnpm installing @notifee/react-native?

helenaford · 2023-06-21T11:24:47Z

@MaxAst that's correct. yes please! Although it might be that the docs are updated but the website isn't as we're trying to move over to another hosting platform

helenaford · 2023-06-21T13:22:55Z

I've also updated the release-notes to make it clear. thanks again, for flagging this

github-actions · 2023-07-19T13:37:59Z

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

MaxAst · 2023-07-20T06:55:39Z

@helenaford I just cloned the repo to update the docs, but saw that the docs are indeed already updated w.r.t to not needing an expo config plugin. While I was on it, I also updated the docs w.r.t the eas build Android server image - The default Android server image on eas now uses JDK 11 by default: #824.

Shall I leave this issue open until the new docs are deployed?

kgdiem · 2023-07-30T14:58:53Z

I started a new project using expo v ~48.0.18 and notifee ^7.8.0 yesterday;

After adding notifee I started getting an error, Notifee native module not found.

Is it expected that after adding notifee / any prebuilt code, Expo Go is no longer a valid route for testing?

EDIT:
Figured it out;

In case anyone else stumbles across this w/ the same issue, you have to run npx expo run:ios / npx expo run:android or npx expo run:ios -d after adding native code.

github-actions · 2023-08-27T15:38:06Z

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

hqasmei · 2023-09-05T18:23:16Z

Hi, is this been solved?
I am having that same error still.

Milk-Cool · 2023-09-07T11:33:58Z

same here :(

Bialson · 2023-09-19T22:04:58Z

If you are building on your own machine, just add in your build.gradle file in android folder the following line:

allprojects {
    repositories {
        maven { url "$rootDir/../node_modules/@notifee/react-native/android/libs" } // <- this line
    }
}

lasharela · 2023-09-23T22:43:37Z

Sorry but in official documentation I still see:

{
  "name": "my app",
  "plugins": [
    "@notifee/react-native"
  ]
}

is plugin needed for expo or not?

Bialson · 2023-09-24T06:23:02Z

In latest version there is no more Expo plugin.

If you want to use this library in your app you need to add native code manually to your app. You need to create development build, because Expo Go doesn't support native modules.

github-actions · 2023-10-22T06:38:11Z

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

ryonwhyte · 2023-11-20T23:26:39Z

I think the docs still need to be updated. Expo now uses JDK 11 by default and the instruction to add the config plugin still exist here https://notifee.app/react-native/docs/installation#expo-support

mikehardy · 2023-11-21T13:41:38Z

Hi there @ryonwhyte 👋 - Expo support here specifically is community supported vs react-native CLI, and in general in an open source repository any statement that starts with "I think ... still need to be..." should be mentally read as "I'll propose a PR to..." - it's how the open source world moves forward...

For anyone else following along I recognize there are a few PRs here that have gotten stale and not been merged over the last few months but I will go back and harvest everything I can, we will merge any + all reasonable PRs 🙏

ryonwhyte · 2023-11-22T07:25:07Z

@mikehardy Agreed! I see these changes have already been proposed. c441b9a

mikehardy · 2023-11-22T14:09:19Z

Ah then it is likely the problem is just the docs site is not currently being published even after we merge docs.

I had forgotten that was also an issue in this repo 😞 - Tracked down the issue for that one and reopened it #559

pencilcheck · 2023-12-16T17:12:30Z

The doc stills said that expo plugin is still supported: https://notifee.app/react-native/docs/installation

Ok, based on the commit linked above, basically just delete the notifee plugin lines in app.config.js then you are all set.

mikehardy · 2023-12-16T19:05:26Z

Yep! @pencilcheck apologies that the published docs are currently not in sync with the committed docs. This is a bug and it is obviously not a great developer experience.

If you click in to here you will see current docs: https://github.com/invertase/notifee/blob/main/docs-react-native/react-native/docs/overview.md

brimby · 2023-12-24T20:54:16Z

The docs still aren't right though because they say you need to use some old ubuntu image, when in reality the current default will suffice.

Please note that Notifee needs Java JDK 11+ to build on Android. If you are building the app with EAS, you need to change the image used for the build. You will have to use image as ubuntu-18.04-jdk-11-ndk-r19c or another image that has jdk 11 as in the following configuration. ([EAS Build Server Configuration](https://docs.expo.dev/build-reference/infrastructure/#image--ubuntu-1804-jdk-8-ndk-r19c--alias--default))

mikehardy · 2023-12-26T12:17:16Z

Ah, I think I may have just fixed building with JDK11+ ( #933 - such that JDK17 will work and JDK21 won't work yet but will work once google finally releases android gradle plugin 8.2.1 with a bugfix)

If you can find post a PR to whatever docs page is still recommending that it will get done before I get a chance to

vivere-dally · 2024-03-29T18:01:23Z

Hi @mikehardy, apologies for tagging you out of the blue. Trying to use this library and I got confused about the docs. I looked into the repo for the commited docs, followed through and still got into an issue such as #350. What docs should be followed in order to give a complete walk-through for a correct setup for the library?

mikehardy · 2024-03-30T02:10:00Z

Hmm should be the docs in git 🤔

cleytonchagasbr · 2024-05-31T13:58:27Z

Hello guys, for ios, where is docs currently?

joaqo · 2024-07-08T15:48:42Z

Docs are still outdated.

linhnph05 · 2024-08-07T14:26:04Z

I have run it successfully but it is not the same in the official docs and even in the git docs. Here is my step:

npx expo install @notifee/react-native
cd ios/ && pod install --repo-update ( I don't sure if needed)
In eas.json

"development": {
  "developmentClient": true,
  "distribution": "internal",
  "android": {
    "image": "ubuntu-20.04-jdk-11-ndk-r19c"
  }
},

npx expo prebuild --clean
eas build --platform android --profile development --local OR npx expo run:ios
Right now cant run npx expo run:android - maybe I need JDK 11+ on my Android emulator

alanbacon · 2024-09-06T23:40:52Z

I still have to modify the build.gradle file as instructed here: #350 (comment)

I do not need the alternate ubuntu image to make things work.

mfrfinbox · 2024-10-02T16:28:39Z

My 2 cents here, as of today I didn't have to use the image "ubuntu-20.04-jdk-11-ndk-r19c" to build succesfully using EAS build.

7dp · 2024-10-04T02:48:47Z

Hi folks, i have a similar problem.
I then tried adding the notifee's maven repo into my android section in app.json and now my npx expo prebuild command works again. Don't forget to remove the "@notifee/react-native" from the plugins section too.

"plugins": [
  [
    "expo-build-properties",
    {
      "android": {
        "extraMavenRepos": [
          "../../node_modules/@notifee/react-native/android/libs"
        ]
      }
    }
  ]
]

You need to install the expo-build-properties first:

npx expo install expo-build-properties

Have a nice day!
And thanks for this great 👍 lib!

bdtren · 2024-10-07T14:34:25Z

Hi folks, i have a similar problem. I tried adding the notifee's maven repo into your android section in app.json and now my npx expo prebuild command works again. And removed the "@notifee/react-native" from the plugins section.
"plugins": [
  [
    "expo-build-properties",
    {
      "android": {
        "extraMavenRepos": [
          "../../node_modules/@notifee/react-native/android/libs"
        ]
      }
    }
  ]
]
You need to install the expo-build-properties first:
npx expo install expo-build-properties
Have a nice day! And thanks for this great 👍 lib!

This is working, thank you!

From my side, I did:

remove the Android and iOS folder if they are exist
remove the "@notifee/react-native" from plugin in app.json
run: npx expo install expo-build-properties
add above lines to app.json
run npx expo prebuild --clean
run: npx expo run:android

mikehardy · 2024-10-07T15:39:52Z

I like the workaround of using a standard expo method of adding android build properties, however, it still puzzles me that this is necessary.

Specifically, in the module's build.gradle we do a lookup to find where the notifee module is installed:

notifee/packages/react-native/android/build.gradle

Lines 23 to 39 in ca4572a

    
           // https://github.com/facebook/react-native/blob/a70354df12ef71aec08583cca4f1fed5fb77d874/ReactAndroid/build.gradle#L168-L201 
        
           def findNodeModulePath(baseDir, packageName) { 
        
             def basePath = baseDir.toPath().normalize() 
        
             // Node's module resolution algorithm searches up to the root directory, 
        
             // after which the base path will be null 
        
             while (basePath) { 
        
               def candidatePath = Paths.get(basePath.toString(), "node_modules", packageName) 
        
               if (candidatePath.toFile().exists()) { 
        
                 return candidatePath.toString() 
        
               } 
        
               basePath = basePath.getParent() 
        
             } 
        
             return null 
        
           } 
        
           def notifeeDir = findNodeModulePath(projectDir, "@notifee/react-native") ?: "$rootDir/../node_modules/@notifee/react-native" 
        
           println ":${project.name} @notifee/react-native found at $notifeeDir"

...and then we add a maven repo pointing in there so that nothing else should be required for module consumers:

notifee/packages/react-native/android/build.gradle

Lines 111 to 116 in ca4572a

    
           rootProject.allprojects { 
        
             repositories { 
        
               maven { 
        
                 url "$notifeeDir/android/libs" 
        
               } 
        
             }

This works for most people but obviously not for some, why not?

Separately I'm thinking on how to get rid of the whole split between core + module, as that helps us meet the goal of having a core that works across flutter or react-native but is in reality just an artifact of when Notifee was closed source and the core was proprietary. There are other ways to achieve our cross-platform goal that may not require an AAR and this irritating extra maven repo thing (see #1115 where I contemplate doing a source copy at build / publish time so code isn't duplicated but it's not a "library" style anymore)

Either way, reopening as the expo docs could use an update with the workaround if some Expo user has a moment?

Would be this file I believe https://github.com/invertase/notifee/blob/main/docs-react-native/react-native/docs/installation.md#expo-support

...and it looks very very out of date

github-actions · 2024-11-04T16:40:59Z

Hello 👋, to help manage issues we automatically close stale issues.

This issue has been automatically marked as stale because it has not had activity for quite some time.Has this issue been fixed, or does it still require attention?

This issue will be closed in 15 days if no further activity occurs.

Thank you for your contributions.

nomi-shah · 2025-01-03T13:24:33Z

expo-build-properties

Hi folks, i have a similar problem. I tried adding the notifee's maven repo into your android section in app.json and now my npx expo prebuild command works again. And removed the "@notifee/react-native" from the plugins section.
"plugins": [
  [
    "expo-build-properties",
    {
      "android": {
        "extraMavenRepos": [
          "../../node_modules/@notifee/react-native/android/libs"
        ]
      }
    }
  ]
]
You need to install the expo-build-properties first:
npx expo install expo-build-properties
Have a nice day! And thanks for this great 👍 lib!
This is working, thank you!

From my side, I did:

remove the Android and iOS folder if they are exist

remove the "@notifee/react-native" from plugin in app.json

run: npx expo install expo-build-properties

add above lines to app.json

run npx expo prebuild --clean

run: npx expo run:android

Same problem here with expo 52 and notifee 7.9.0 also tried the latest :(
Still no luck. Spend almost two days.
Now I am thinking to revert to the native CLI. :(

bdtren · 2025-01-03T13:34:34Z

Same problem here with expo 52 and notifee 7.9.0 also tried the latest :(
Still no luck. Spend almost two days.
Now I am thinking to revert to the native CLI. :(

Hey @nomi-shah ,

Did you try downgrade to expo 51? I just implemented Push notification last week and this workaround still working fine.

Expo 52 still not stable, it causing issues in react-native-maps, react-native-paper, ... so I think you shouldn't use it in production app for now.

nomi-shah · 2025-01-03T13:49:12Z

Same problem here with expo 52 and notifee 7.9.0 also tried the latest :(
Still no luck. Spend almost two days.
Now I am thinking to revert to the native CLI. :(

Hey @nomi-shah ,

Did you try downgrade to expo 51? I just implemented Push notification last week and this workaround still working fine.

Expo 52 still not stable, it causing issues in react-native-maps, react-native-paper, ... so I think you shouldn't use it in production app for now.

Thank you for your response, @bdtren.

I haven’t tried Expo 51 yet. Is it possible to downgrade from Expo 52 to Expo 51? I’m new to mobile app development, so could you please share the exact Notifee version you’re using and the steps you followed? Also, are you using the bare workflow?

I’ve implemented native FCM notifications and am not using the Expo notification packages.

bdtren · 2025-01-03T13:56:20Z

@nomi-shah

"@notifee/react-native": "^7.9.0",
"@react-native-firebase/app": "^21.0.0",
"@react-native-firebase/messaging": "^21.0.0",
"expo": "~51.0.39",

I just tried above with "expo": "~52.0.17" and notification is working. Maybe it is because of some other issues from your side?

MaxAst mentioned this issue Jun 20, 2023

[React native] Latest release causes an error #797

Closed

helenaford added needs-feedback Waiting on response to questions docs labels Jun 21, 2023

github-actions bot added the Type: Stale label Jul 19, 2023

github-actions bot removed the Type: Stale label Jul 20, 2023

github-actions bot added the Type: Stale label Aug 27, 2023

github-actions bot removed the Type: Stale label Sep 5, 2023

github-actions bot added the Type: Stale label Oct 22, 2023

github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 6, 2023

sregg mentioned this issue Jul 26, 2024

Compatibility issues with Expo version 0.10.16 #950

Closed

mikehardy reopened this Oct 7, 2024

mikehardy added help wanted android expo and removed Type: Stale labels Oct 7, 2024

This was referenced Oct 9, 2024

Could not find any matches for app.notifee:core:+ as no versions of app.notifee:core are available. #350

Closed

Official Expo config plugin #1121

Open

github-actions bot added the Type: Stale label Nov 4, 2024

mikehardy added Keep Open this label avoids the stale bot and removed Type: Stale labels Nov 5, 2024

XChikuX mentioned this issue Dec 20, 2024

Have a issues [ notifee_react-native:compileDebugHavaWithJavac ] #1012

Closed

Package "@notifee/react-native" does not contain a valid config plugin. #799

Package "@notifee/react-native" does not contain a valid config plugin. #799

Comments

MaxAst commented Jun 20, 2023

leggomuhgreggo commented Jun 21, 2023 • edited Loading

MaxAst commented Jun 21, 2023

MaxAst commented Jun 21, 2023 • edited Loading

helenaford commented Jun 21, 2023

helenaford commented Jun 21, 2023

github-actions bot commented Jul 19, 2023

MaxAst commented Jul 20, 2023

kgdiem commented Jul 30, 2023 • edited Loading

github-actions bot commented Aug 27, 2023

hqasmei commented Sep 5, 2023

Milk-Cool commented Sep 7, 2023

Bialson commented Sep 19, 2023

lasharela commented Sep 23, 2023

Bialson commented Sep 24, 2023

github-actions bot commented Oct 22, 2023

ryonwhyte commented Nov 20, 2023

mikehardy commented Nov 21, 2023

ryonwhyte commented Nov 22, 2023

mikehardy commented Nov 22, 2023

pencilcheck commented Dec 16, 2023 • edited Loading

mikehardy commented Dec 16, 2023

brimby commented Dec 24, 2023

mikehardy commented Dec 26, 2023

vivere-dally commented Mar 29, 2024

mikehardy commented Mar 30, 2024

cleytonchagasbr commented May 31, 2024

joaqo commented Jul 8, 2024

linhnph05 commented Aug 7, 2024 • edited Loading

alanbacon commented Sep 6, 2024

mfrfinbox commented Oct 2, 2024

7dp commented Oct 4, 2024 • edited Loading

bdtren commented Oct 7, 2024

mikehardy commented Oct 7, 2024

github-actions bot commented Nov 4, 2024

nomi-shah commented Jan 3, 2025

bdtren commented Jan 3, 2025 • edited Loading

nomi-shah commented Jan 3, 2025

bdtren commented Jan 3, 2025 • edited Loading

leggomuhgreggo commented Jun 21, 2023 •

edited

Loading

MaxAst commented Jun 21, 2023 •

edited

Loading

kgdiem commented Jul 30, 2023 •

edited

Loading

pencilcheck commented Dec 16, 2023 •

edited

Loading

linhnph05 commented Aug 7, 2024 •

edited

Loading

7dp commented Oct 4, 2024 •

edited

Loading

bdtren commented Jan 3, 2025 •

edited

Loading

bdtren commented Jan 3, 2025 •

edited

Loading