cannot read property 'configureProvider' of undefined

[SamMatthewsIsACommonName]

Hi, as I made reference to here #14
I'm having an issue with the oath on Android. Do I need to configure the manager differently based on platform? At present my code looks like this

const manager = new OAuthManager('MyAPp');
const config = {
  facebook: {
    client_id: 'MY_CLIENT_ID',
    client_secret: 'MY_CLIENT_SECRET',
  },
};
manager.configure(config);

It works amazingly (Thanks @auser !!) on ios, but in android everything about the manager is then coming up as undefined. I removed all my promises handling etc to just strip it back to console logging the manager variable but I was getting 'cannot read property 'configureProvider' of undefined and it wouldn't go any further.

Is this a bug or is this just user error? I (think) I;ve read the docs quite extensively and everything seems as it's supposed to be? Cheers

[SamMatthewsIsACommonName]

I just realised I hadn't configured anything here. Does this need to be setup or is that only to handle the ios side? If so what values should I put in, is it similar to how the ios is setup? I can't find anything about it in the docs sorry :/

edit: I've set all that stuff up, but still when trying to call manager.authorise('facebook') I get "cannot read property 'authorise' or undefined"

[auser]

Interesting... it should be handled in Android... I just confirmed it's working on android here. What version of rn-oauth do you have?

[auser]

I just pushed an update. Also, the method name is authorize, not authorise

[SamMatthewsIsACommonName]

I just updated to version 2.19, yeah sorry 'authorise' was a typo here it was authorize.
I'm still getting the error. I've moved the function call and setup to a componentWillMount just so there's no additional factors to consider and it works fine on ios but on android I get this:

TypeError: Cannot read property 'authorize' of undefined
    at promisify.js:11
    at tryCallTwo (core.js:45)
    at doResolve (core.js:200)
    at new Promise (core.js:66)
    at promisify.js:6
    at OAuthManager.authorize (react-native-oauth.js:38)
    at AppNavigator.componentWillMount (appNavigator.js:48)
    at ReactCompositeComponent.js:347
    at measureLifeCyclePerf (ReactCompositeComponent.js:74)
    at ReactCompositeComponentWrapper.performInitialMount 

[auser]

What's the difference between your implementation and this? Is there any? https://github.com/fullstackreact/FirestackApp/blob/master/app/views/Authentication/Demos/Providers.js#L38

[SamMatthewsIsACommonName]

Here is the implementation along with the accompanying console logs when just fired in a componentWillMount lifecycle method:

  componentWillMount() {
    const manager = new OAuthManager('MY_APP');
    const config = {
      facebook: {
        client_id: 'MY_ID',
        client_secret: 'MY_SECRET',
      },
    };
    manager.configure(config);
    console.log('manager:', manager);
    manager.authorize('facebook')
    .then(x => console.log(x))
    .catch(err => console.log('error', err));
  }

And the logs:

As I said it works fine on ios that's the strange thing, but with android it's not even getting past the fire the function stage

The only difference I can see is in your code you have the manager defined inside the component then call this.manager

[SamMatthewsIsACommonName]

Also you're passing in provider as a variable to authorize but it equals the string 'facebook' in one case so I can't see any difference there

Also from the ternary operator in promisify it's using Module[fn] rather than fn. As I say works fine on ios though. Don;t know if that helps any?

edit: added response when I run same code on ios

[auser]

Can you relink the library? Rnpm unlink and react-native link? It sounds like the android side didn't get linked

[SamMatthewsIsACommonName]

On trying to do that it seems my folder structure isn't quite what link is expecting, I've pmed you on gitter with the details, not sure if it's expected behaviour or my project is set up wrong?

[auser]

Responded

[signorekai]

I am also encountering this same issue, and react-native unlink then react-native link didn't solve the issue. Any idea?

[SamMatthewsIsACommonName]

Hi @signorekai does your android package name end in com.android by any chance? This was causing a problem with link for me

[signorekai]

No it didn't, unfortunately.

…

On Thu, 19 Jan 2017, 13:41 Sam Matthews ***@***.***> wrote: Hi @signorekai <https://github.com/signorekai> does your android package name end in com.android by any chance? This was causing a problem with link for me — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#37 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ALms1-miDGjGnJgBVLx0s_V-cGLKn5O4ks5rTvdzgaJpZM4LgRVH> .

[auser]

Happy to hop on ScreenHero to help debug.