Fernando Azarías's questions

I have an app that when I'm running with Expo, the permissions work fine and the dialog box appears to accept or deny them. However, when I generate the apk with expo build:android and install it on my phone, the app does not ask me for permissions. In application manager my app does not show any permissions that have been accepted or rejected so I cannot manually enable them.

This is my App.json

{
  "expo": {
    "name": "dev-1",
    "slug": "dev-1",
    "privacy": "public",
    "sdkVersion": "36.0.0",
    "platforms": ["ios", "android", "web"],
    "version": "1.0.1",
    "orientation": "portrait",
    "icon": "./assets/icon.png",
    "splash": {
      "image": "./assets/splash.png",
      "resizeMode": "contain",
      "backgroundColor": "#ffffff"
    },
    "updates": {
      "fallbackToCacheTimeout": 0
    },
    "assetBundlePatterns": ["**/*"],
    "ios": {
      "supportsTablet": true
    },
    "android": {
      "package": "com.fernandoAzarias.tenedores",
      "permissions": ["CAMERA_ROLL", "LOCATION"],
      "versionCode": 2
    },
    "description": "An app just for learn React Native"
  }
}

This is a part of the code that obtains the permissions

const changeAvatar = async () => {
    const resultPermissions = await Permissions.askAsync(
      Permissions.CAMERA_ROLL
    );
    console.log(resultPermissions);
    setLog([...log, resultPermissions]);
    if (resultPermissions.granted) {
      const result = await ImagePicker.launchImageLibraryAsync({
        allowsEditing: true,
        aspect: [4, 3]
      });

setLog saves the permissions object, which allows me to display them on the screen. I am getting this as a response:

{
  canAskAgain: false
  expires: never,
  granted: false
  Permissions: {
    cameraRoll: {
      canAskAgain: false
      expires: never
      granted: false
      status: denied
    }
  }
}

Clearly the app does not have permissions, but in the application manager the app does not have any permissions and it does not show anything, so I cannot enable disable.

I hope you can help me.

I am learning how to unit test in vue. I would like to know how to test a method. I am using jest and vue test utils. In the vue documentation I can't find anything similar to test a method.

So far, what I have is the following

introducir el código aquíimport { shallowMount } from '@vue/test-utils'
import Usuario from '@/components/Usuario.vue'

describe('componente Usuario.vue', () => {
it('calls testMethod on mount', () => {
    const wrapper = shallowMount(Usuario, {
        methods: {
            activarUsuario
        }
    })
    wrapper.vm.activarUsuario = jest.fn()

    expect(activarUsuario).toBeCalled()
});

})

I have a login where they start through facebook. I want to add the option to log in using Twitter. But for that I must also be able to handle errors with accounts that have the same email that have already been registered before. That is, if a user registers with facebook with the email [email protected] and then wants to enter with twitter with the email [email protected]. I must detect that and handle it. The documentation gives this code as an example:

// Step 1.
// User tries to sign in to Twitter.
auth.signInWithPopup(new firebase.auth.TwitterAuthProvider()).catch(function(error) {
  // An error happened.
  if (error.code === 'auth/account-exists-with-different-credential') {
    // Step 2.
    // User's email already exists.
    // The pending Twitter credential.
    var pendingCred = error.credential;
    // The provider account's email address.
    var email = error.email;
    // Get registered providers for this email.
    auth.fetchProvidersForEmail(email).then(function(providers) {
      // Step 3.
      // If the user has several providers,
      // the first provider in the list will be the "recommended" provider to use.
      if (providers[0] === 'password') {
        // Asks the user his password.
        // In real scenario, you should handle this asynchronously.
        var password = promptUserForPassword(); // TODO: implement promptUserForPassword.
        auth.signInWithEmailAndPassword(email, password).then(function(user) {
          // Step 4a.
          return user.link(pendingCred);
        }).then(function() {
          // Twitter account successfully linked to the existing Firebase user.
          goToApp();
        });
        return;
      }
      // All the other cases are external providers.
      // Construct provider object for that provider.
      // TODO: implement getProviderForProviderId.
      var provider = getProviderForProviderId(providers[0]);
      // At this point, you should let the user know that he already has an account
      // but with a different provider, and let him validate the fact he wants to
      // sign in with this provider.
      // Sign in to provider. Note: browsers usually block popup triggered asynchronously,
      // so in real scenario you should ask the user to click on a "continue" button
      // that will trigger the signInWithPopup.
      auth.signInWithPopup(provider).then(function(result) {
        // Remember that the user may have signed in with an account that has a different email
        // address than the first one. This can happen as Firebase doesn't control the provider's
        // sign in flow and the user is free to login using whichever account he owns.
        // Step 4b.
        // Link to Twitter credential.
        // As we have access to the pending credential, we can directly call the link method.
        result.user.link(pendingCred).then(function() {
          // Twitter account successfully linked to the existing Firebase user.
          goToApp();
        });
      });
    });
  }
});

My problem is in this part:

var provider = getProviderForProviderId(providers[0]);
auth.signInWithPopup(provider).then(function(result) {

The browser tells me:

getProviderForProviderId" is not defined

I don't know what I should do with the previous 2 lines.