Hi @freakthemighty - this is due to a recent change we made to scope permissions by app in the expo client. I don’t think there’s a great way around this in the client app right now, since when a user “denies” permission the client has no idea if they intend to deny permission just to that app, or to the entire expo client. You may just need to err on the side of using askAsync more.
However, note that this should not be a problem in standalone apps (i.e. “denied” will reliably reflect the OS-level permission).
cc @aalices in case there’s something I missed here.