Linking.openUrl with a telephone number throws an error

[andrewsouthard]

React Native version:
System:
OS: macOS Mojave 10.14.6
CPU: (4) x64 Intel(R) Core(TM) i5-5257U CPU @ 2.70GHz
Memory: 37.91 MB / 8.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 12.4.0 - ~/.nvm/versions/node/v12.4.0/bin/node
Yarn: 1.12.1 - ~/.yarn/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v12.4.0/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.4, macOS 10.14, tvOS 12.4, watchOS 5.3
Android SDK:
API Levels: 27, 28
Build Tools: 27.0.3, 28.0.0, 28.0.2, 28.0.3
System Images: android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.5 AI-191.8026.42.35.5791312
Xcode: 10.3/10G8 - /usr/bin/xcodebuild
npmPackages:
react: 16.9.0 => 16.9.0
react-native: 0.61.0 => 0.61.0

Steps To Reproduce

1. react-native init phonetest
2. Change App.js to the following:

import {Button, Linking, SafeAreaView} from 'react-native';

const App = () => {
  return (
    <SafeAreaView>
      <Button
        onPress={() => {
          Linking.openURL('tel:555-867-5309').catch(err =>
            console.error('An error occurred', err),
          );
        }}
        title="Call"
      />
    </SafeAreaView>
  );
};

export default App;

3. react-native run-ios

Describe what you expected to happen:
Dialog box asking whether to call the number or cancel

Instead, received the following error:

[react-native-bot]

It looks like you are using an older version of React Native. Please update to the latest release, v0.61 and verify if the issue still exists.

The "Resolution: Old Version" label will be removed automatically once you edit your original post with the results of running `react-native info` on a project using the latest release.

[lucasbento]

This is expected, you can not make phone calls on simulator, if you test this on a real device you will see that it works.

[andrewsouthard]

@lucasbento That makes sense. Thanks! Would it be possible to throw an error message indicating that to prevent any confusion?

[kelset]

Would it be possible to throw an error message indicating that to prevent any confusion?

Maybe instead of an error it could be a warning?
That said, I think that it's a good idea anyway - could you open a PR for it? 🤗

(since Hacktoberfest is close and I think that it's not too complicated - but I may be wrong - I'll also add the good first issue label)

[lucasbento]

Yeah, this definitely would benefit from a better error message!

[espipj]

@kelset I think this can be closed now 😺

[kelset]

awesome, thanks!