Giters

vmurin / react-native-azure-auth

React Native library implementing Azure AD OAuth2 API

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

AzureAuth different sources

jaltenbernd opened this issue · comments

commented

If I run a pod install inside the ios folder, I get the following error:

[!] There are multiple dependencies with different sources for AzureAuth in Podfile:

  • AzureAuth (from ../node_modules/react-native-azure-auth/ios)
  • AzureAuth (from ../node_modules/react-native-azure-auth)

The reason I ran the command was because it says it can't find the module AzureAuth. Then followed by:

[Sat Aug 15 2020 17:26:57.738] ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)
[Sat Aug 15 2020 17:26:58.776] ERROR Invariant Violation: Module AppRegistry is not a registered callable module (calling runApplication)

I started with a brand new React Native app and added this module.

commented

Hi John,

I think you issues are not related to the library but to your setup and accident :)

Just take a look on the similar issues on stackoverflow and/or github. See related examples below:

Feel free to reopen the issue if you have further questions. I will also extend and slightly improve the pod file shortly.

Regards
Vlad

commented

@vmurin I am also getting this error, only for this specific repo. Only the last link you sent is related to the pod install error, and the answer is not useful.

The solutions suggested here also do not resolve the issue. facebook/react-native#26642

the podfile reference is correctly pointing to the root of the module, so it really seems like a possible issue with this module for the latest cocoapods.

commented

@vmurin @jaltenbernd The error is resolved by unlinking the two repos that it says to link in the installation instructions. Which tells me it's autolinking and those steps need to be removed from the readme.

commented

@vmurin @jaltenbernd The error is resolved by unlinking the two repos that it says to link in the installation instructions. Which tells me it's autolinking and those steps need to be removed from the readme.

@almercier Thanks for your suggestion. As a library author I can't know do you use autolinking or not. That's why the README follows the official documentation for Automatic linking (dont mix up with autolinking ;-)) )

But I will add the note about autolinking issue.
Thank you again!