For some reason, a recent commit removed the check for a null return from getCurrentActivity(). But since getCurrentActivity() might return null, the app will crash with a NullPointerException.
This restores the null check.
It also fixes inconsistent handling of null tag argument in both iOS and Android. This does not affect usage from JS because the JS interface will not pass null to that argument; however other native code could still call these methods and pass null for tag.
marcshilling
commented
8 months ago
For some reason, a recent commit removed the check for a null return from
getCurrentActivity(). But sincegetCurrentActivity()might return null, the app will crash with a NullPointerException.This restores the null check.
It also fixes inconsistent handling of null
tagargument in both iOS and Android. This does not affect usage from JS because the JS interface will not pass null to that argument; however other native code could still call these methods and pass null fortag.Fixes: #32