package or namespace load failed for ‘tidyverse’ in namespaceExport(ns, exports): undefined exports: %>%

I was helping someone get up and running with R/RStudio today, and we struggled to get the tidyverse to load. We tried uninstalling/re-installing R/Studio/packages but no luck. I've never come across this issue before. What's the best way to troubleshoot?

library(tidyverse)

Error: package or namespace load failed for ‘tidyverse’ in namespaceExport(ns, exports):
undefined exports: %>%

sessionInfo()
R version 3.6.3 (2020-02-29)
Platform: x86_64-apple-darwin15.6.0 (64-bit)
Running under: macOS Catalina 10.15.4
Matrix products: default
BLAS:   /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib
LAPACK: /Library/Frameworks/R.framework/Versions/3.6/Resources/lib/libRlapack.dylib
locale:
[1] en_US.UTF-8/en_US.UTF-8/en_US.UTF-8/C/en_US.UTF-8/en_US.UTF-8
attached base packages:
[1] stats     graphics  grDevices utils     datasets  methods
[7] base
loaded via a namespace (and not attached):
 [1] Rcpp_1.0.3       rstudioapi_0.11  magrittr_1.5
 [4] tidyselect_1.0.0 lattice_0.20-38  R6_2.4.1
 [7] rlang_0.4.6      blob_1.2.1       dplyr_0.8.4
[10] tools_3.6.3      grid_3.6.3       broom_0.5.4
[13] nlme_3.1-144     xfun_0.12        tinytex_0.19
[16] DBI_1.1.0        assertthat_0.2.1 tibble_2.1.3
[19] lifecycle_0.1.0  crayon_1.3.4     purrr_0.3.3
[22] tidyr_1.0.2      vctrs_0.3.0      glue_1.3.1
[25] compiler_3.6.3   pillar_1.4.3     generics_0.0.2
[28] backports_1.1.5  pkgconfig_2.0.3

Did you check all the packages are up to date? Maybe there's a version incompatibiity.

%>% comes from the magrittr package, check that this is loaded ok.

Thanks @woodward. It's a fresh install of R/RStudio and first time downloading tidyverse. sessionInfo() shows the correct magrittr version too.

Hello,

I've encountered the same problem with "tidyverse" and with the "pool" package. I cannot load the packages properly without loading "magrittr" first. My main problem is, that I cannot check my package build due to this error or even load a package via devtools::load_all().

Any solutions so far?

Greetings

This topic was automatically closed 21 days after the last reply. New replies are no longer allowed.