Alert.alert without message kills apps even after refreshing

[thijssmudde]

Unrecognized selector sent to instance was thrown while invoking alertWithArgs on target AlertManager

Environment

Environment:
OS: macOS High Sierra 10.13.3
Node: 9.2.0
Yarn: 1.3.2
npm: 5.6.0
Watchman: 4.9.0
Xcode: Xcode 9.2 Build version 9C40b
Android Studio: 3.0 AI-171.4443003

Packages: (wanted => installed)
react: 16.2.0 => 16.2.0
react-native: 0.52.0 => 0.52.0

Steps to Reproduce

https://snack.expo.io/SJG9v82Kz

See: https://stackoverflow.com/questions/41942681/alert-alert-alertmanager-with-params-exception

Expected Behavior

No crash

Actual Behavior

Crash

[react-native-bot]

Thanks for posting this! It looks like your issue may be incomplete. Are all the fields required by the Issue Template filled out?

If you believe your issue contains all the relevant information, let us know in order to have a maintainer remove the No Template label. Thank you for your contributions.

_{How to Contribute • What to Expect from Maintainers}

[hramos]

Closing after seven days with no follow up from the author.

[thijssmudde]

Updated to the template. It had all useful information before tho

[louisiscoding]

+1 having the same issue.

[siamakEsh]

Same issue.

[trev91]

Same issue. Anyone have a work around?

[thijssmudde]

@trev91 To fix it at least supply an empty string ''

Here is a fix for the reproduction. So by adding 'Are you sure' as second parameter it works. However, that is not how it should be.

Alert.alert('Uitloggen', 'Are you sure?', [
     {
       text: 'Annuleer',
       style: 'cancel'
     }, {
       text: 'Ok',
       onPress: () => { //Go to walkthrough
         Meteor.logout()

         this
           .props
           .navigation
           .dispatch(NavigationActions.reset({
             index: 0,
             actions: [NavigationActions.navigate({routeName: 'Walkthrough'})]
           }))
       }
     }
   ], {cancelable: false})

[react-native-bot]

Thanks for posting this! It looks like your issue may refer to an older version of React Native. Can you reproduce the issue on the latest release, v0.55?

Thank you for your contributions.