checkForUpdateAsync throws exception

SDK Version: 46
Platforms(Android/iOS/web/all): ios

Hi, why does checkForUpdateAsync of expo-updates throw an exception if there is no update available. instead of returning null? I thought it should only throw an exception if something unexpected happens.

How can I differentiate between “no update available” and unexpected network issue?

From the docs I get that you will only get a rejected promise, if you run in DEV mode:


Other than that you should get an object back that contains isAvailable boolean to see, if there is an update.

Yeah I assumed that, too. But the screenshot is from an internal production build that I installed on the device.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.