<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in EXRemoteNotificationPermissionSingletonModule.m</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>efd75dec - [ios] Migrate all remaining native code</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/ios/EXNotifications/Permissions/EXRemoteNotificationPermissionSingletonModule.m#efd75dec</link>
        <description>[ios] Migrate all remaining native code

            List of files:
            /expo/packages/expo-notifications/ios/EXNotifications/Permissions/EXRemoteNotificationPermissionSingletonModule.m</description>
        <pubDate>Mon, 16 Aug 2021 13:40:38 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>096a701b - [expo-notifications][expo-permissions] Move notification permission requesters to notifications package (#8486)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/ios/EXNotifications/Permissions/EXRemoteNotificationPermissionSingletonModule.m#096a701b</link>
        <description>[expo-notifications][expo-permissions] Move notification permission requesters to notifications package (#8486)# WhyFixes https://github.com/unimodules/react-native-unimodules/issues/136. This is what we wanted to do anyway&#8212;move code responsible for permissions to respective modules.# How- removed `EXUserNotificationPermissionRequester` as it was left only as a fallback for when `expo-notifications` is not installed. Now that in Expo Client `expo-notifications` will be installed, this class would never be used.- moved remote notification permission requester from `expo-permissions` to `expo-notifications`, effectively removing support for calling `askAsync(Permissions.NOTIFICATIONS)` from `expo-permission` if `expo-notifications` is not installed  - while moving I write a way for the requester to receive callbacks about permission being accepted or declined. I used a `UIApplicationDelegate` singleton module to which requesters can register to receive callbacks.  - since new notification permission requesters now may return `null` inside the permission response I had to either:    - add support for `NSNull` in `EXPermissionsManager` (it is returned by the user notifications permissions requester)    - exclude `notifications` and `userFacingNotifications` from being saved to kernel service since we don&apos;t scope them even so (thanks @lukmccall for the tip!)        We decided to stick to the second idea.# Test Plan- [x] Ran Expo Client on an ExpoClient-less device, fetched and asked for both notification-related permissions.

            List of files:
            /expo/packages/expo-notifications/ios/EXNotifications/Permissions/EXRemoteNotificationPermissionSingletonModule.m</description>
        <pubDate>Wed, 27 May 2020 18:19:34 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
</channel>
</rss>
