<?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 NotificationPermissionsModule.js</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>bd3aa699 - [packages] rebuild packages after ESLint bump (#14203)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#bd3aa699</link>
        <description>[packages] rebuild packages after ESLint bump (#14203)

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Fri, 27 Aug 2021 21:45:40 +0000</pubDate>
        <dc:creator>Bartosz Kaszubowski &lt;gosimek@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8285c032 - Rename unimodules imports to expo-modules-core</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#8285c032</link>
        <description>Rename unimodules imports to expo-modules-core

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Fri, 13 Aug 2021 22:46:17 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>fb3d99c5 - [permissions] Migrate interface to expo-modules-core (#12961)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#fb3d99c5</link>
        <description>[permissions] Migrate interface to expo-modules-core (#12961)

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Mon, 24 May 2021 12:48:51 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;1714764+tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>a56e4a62 - Remove usage of `fbjs` from most packages (#11396)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#a56e4a62</link>
        <description>Remove usage of `fbjs` from most packages (#11396)* expo-web-browser* expo-device* expo-camera* expo-notifications* legacynotification in expo package* expo-font* expo-constants* expo-updates* expo-sensors* expo-error-recovery* expo-gl* expo-linking* changelogs* rebuild expo-device* add missing space to changelog entriesCo-authored-by: Evan Bacon &lt;baconbrix@gmail.com&gt;Co-authored-by: Evan Bacon &lt;baconbrix@gmail.com&gt;

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Mon, 21 Dec 2020 19:10:17 +0000</pubDate>
        <dc:creator>Charlie Cruzan &lt;35579283+cruzach@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>82d54437 - [expo-notifications] Fix requestPermissions on Safari (at least) (#10296)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#82d54437</link>
        <description>[expo-notifications] Fix requestPermissions on Safari (at least) (#10296)# WhyPart of https://github.com/expo/expo/issues/6895.# HowNoticed &lt;kbd&gt;Request permissions&lt;/kbd&gt; button returns `status: undetermined` on Safari even though I granted the permissions. It turned out `Notification.requestPermission` has two signatures: a legacy, deprecated one `requestPermission(callback): void` and a new one `requestPermission(): Promise`. This code should cover both method implementations.# Test PlanI have verified that the &lt;kbd&gt;Request permissions&lt;/kbd&gt; button works as expected in Safari and Chrome.

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Tue, 22 Sep 2020 18:02:05 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>ce586fbe - [web][notifications] Add permissions (#9576)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#ce586fbe</link>
        <description>[web][notifications] Add permissions (#9576)* Add web permissions to notifications module* Update CHANGELOG.md* fix lint error* Update packages/expo-notifications/CHANGELOG.mdCo-authored-by: Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;* pr feedback* Update exampleCo-authored-by: Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Thu, 06 Aug 2020 21:37:42 +0000</pubDate>
        <dc:creator>Evan Bacon &lt;baconbrix@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>db1c4130 - [expo-notifications] Add preliminary &quot;support&quot; for Web (#8853)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#db1c4130</link>
        <description>[expo-notifications] Add preliminary &quot;support&quot; for Web (#8853)# WhyEven though we don&apos;t support Web in `expo-notifications`, we don&apos;t want to be a pain to the users and throw errors just because of running the code on Web.# HowAdded simple object fallbacks for missing modules on web so that they are queryable by```tsif (!Module.methodAsync) {  throw new Unavailability&#8230;}```Swapped `.ts` + `.web.ts` for `.native.ts` + `.ts` (or + `.web.ts` + `.ts` where it made sense, eg. if we would need to use `localStorage` inside the `.ts` file I renamed it to `.web.ts` and added an empty fallback in `.ts`).# Test Plan- [x] Ran NCL in `bare-expo` on Web, clicked buttons around, noticed the error is readable and makes sense.- [x] Ran `expo-notifications` test-suite on both iOS and Web. It seems iOS tests are a little bit flaky, unfortunately (the errors could also happen due to erroring Expo API, HTTP error 504 when fetching push token, but I was able to make all of the tests pass just refreshing).

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Fri, 19 Jun 2020 00:29:04 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>7cf8d919 - [expo-notifications] Unify types across the API</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#7cf8d919</link>
        <description>[expo-notifications] Unify types across the API

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Fri, 27 Mar 2020 10:19:49 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>d09fc44c - [expo-notifications] Implement notification channel management (#7123)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#d09fc44c</link>
        <description>[expo-notifications] Implement notification channel management (#7123)# WhyWe want to let developers create and choose where to send the notification.# HowImplemented a simple module managing the channels.Decisions I had to make:- I didn&apos;t add the Expo channel polyfill &#8211; do you think it is necessary? I don&apos;t know if any other notifications library would do something like this and if users would benefit from it more than from setting appropriate `sound: true, vibrate: [500, 500]` in the remote push notification payload.- all the methods resolve on platforms that don&apos;t support channels, logging a helpful message with `console.debug`- all enumerable information is an `enum` in TS, and no conversion is done from TS to native and back again, I can add that if it&apos;s needed (is it?)# Test PlanAdded test cases to `test-suite` &#8212; they pass on both a device supporting channels and a device not supporting channels.

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Thu, 05 Mar 2020 08:06:24 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>2e19934f - [expo-notifications] Add permissions requesting methods (#6807)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-notifications/build/NotificationPermissionsModule.js#2e19934f</link>
        <description>[expo-notifications] Add permissions requesting methods (#6807)# WhyPart of `expo-notifications` rework. BTW fixes https://github.com/expo/expo/issues/5093.# How- on iOS:  - implemented a requester that returns full information on current notification settings  - implemented an exported module capable of getting and asking for notification permissions  - added a method so that developers are able to ask for specific notification permissions- on Android:  - implemented a native module that returns a response based on `NotificationManagerCompat`  - moreover, it also returns `importance` of notifications- on web:  - nothing yet, to be researched- in TS:  - added methods and type definitions for all the new features# Test PlanAdded a simple test to `test-suite` and manually checked if the values returned match the settings.

            List of files:
            /expo/packages/expo-notifications/build/NotificationPermissionsModule.js</description>
        <pubDate>Wed, 12 Feb 2020 10:38:50 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
</channel>
</rss>
