Passing null or undefined as a value to setItem or multiSet doesn't result in an error.

Current behavior

If null or undefined is passed as a value to setItem or multiSet then no error is generated and therefore any listening .catch() methods/catch blocks/error callbacks don’t fire to let you know something went wrong.

Expected behavior

I would expect an error to be generated in the same way as if any other invalid value was passed e.g. number, bool, object.

Repro steps

            try {
              await AsyncStorage.setItem('aTestKey', null, e => {
                console.error(`Error in callback`, { e });
              });
            } catch (e) {
              console.error(`Error in catch`, { e });
            }

Environment

• Async Storage version: 1.6.2
• React-Native version: 0.61.4
• Platform tested: Android
• Logs/Error that are relevant: N/A

[leemcmullen]

Fantastic, thanks @Krizzu - much appreciated 👍

[krizzu]

@leemcmullen Yes, you’re right - the error is being swallowed for null/undefined in here.

Going to fix that 😃