title: React Native module not working only on iOS
body: <p>I have recently upgraded my react-native project to 0.60. After upgrading, a native module I have been working with has stopped working on iOS, with the error TypeError: Cannot read property 'show' of undefined.</p>
  
  <p>I have been modifying this native module but the only code I had modified after upgrading to RN 0.60 was Android code. My modified module code is at <a href="https://github.com/BradyShober/react-native-braintree-dropin-ui" rel="nofollow noreferrer">https://github.com/BradyShober/react-native-braintree-dropin-ui</a> </p>
  
  <p>The file that is calling the module is</p>
  
  <pre><code>import BraintreeDropIn from 'react-native-braintree-dropin-ui';
  
  const showBraintreeUI = async (token, amount) =&gt; {
      BraintreeDropIn.show({
          clientToken: token,
          countryCode: 'US',
          currencyCode: 'USD',
          orderTotal: amount,
          googlePay: true,
          googleMerchantId: 'merchantID',
          applePay: true,
          merchantName: "Name",
          merchantIdentifier: "ID",
          vaultManager: true
      })
      .then(async (result) =&gt; {
          console.log(result)
          }
          catch(error){
              console.log(error);
          }
      })
      .catch((error) =&gt; {
          if (error.code === 'USER_CANCELLATION') {
              console.log("User cancelled payment");
          }
          else {
              console.log(error);
          }
      });
  }
  
  export { getBraintreeToken, showBraintreeUI };
  </code></pre>
  
  <p>The expected result is the opening of the Braintree Drop In UI which works on Android but on iOS is throwing an error TypeError: Cannot read property 'show' of undefined.</p>
  
  <p>I believe this to be an issue with autolinking, I have been able to get it to work if I right click Libraries in Xcode, then Add files and select the module's .xcodeproject and then add the library in Link Binaries with Libraries. I haven't been able to easily find what I would have to change in the module to not have to do those steps as a workaround.</p>