<?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 EXKernelServiceRegistry.h</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>489c2041 - [ios] Remove legacy notifications module code (#24325)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#489c2041</link>
        <description>[ios] Remove legacy notifications module code (#24325)

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Fri, 15 Sep 2023 23:18:39 +0000</pubDate>
        <dc:creator>Will Schurman &lt;wschurman@expo.io&gt;</dc:creator>
    </item>
<item>
        <title>75d03742 - [iOS][Expo Go] Remove legacy screen orientation code (#14649)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#75d03742</link>
        <description>[iOS][Expo Go] Remove legacy screen orientation code (#14649)

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Thu, 07 Oct 2021 14:41:40 +0000</pubDate>
        <dc:creator>Bart&#322;omiej Bukowski &lt;bartlomiej.bukowski@swmansion.com&gt;</dc:creator>
    </item>
<item>
        <title>a9a91078 - Revert &quot;[ios] Remove legacy ScreenOrientation code (#11371)&quot; (#12217)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#a9a91078</link>
        <description>Revert &quot;[ios] Remove legacy ScreenOrientation code (#11371)&quot; (#12217)This reverts commit 454e16d504aee225b3bdc8ee3fedbbdc051c7209.# WhyAfter #11371, `lockAsync` is broken in iOS Expo Go; it causes the current orientation to change but does **not** persist the lock, which causes various issues. Additionally, the app.json `orientation` setting has no effect either. Essentially, all apps are permanently locked to `DEFAULT` orientation.# Test Plan- [x] NCL tests pass- [x] test-suite tests pass- [x] app.json `orientation` setting has an effect

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Mon, 15 Mar 2021 17:42:36 +0000</pubDate>
        <dc:creator>Eric Samelson &lt;esamelson@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>454e16d5 - [ios] Remove legacy ScreenOrientation code (#11371)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#454e16d5</link>
        <description>[ios] Remove legacy ScreenOrientation code (#11371)

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Wed, 16 Dec 2020 15:42:20 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;1714764+tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>70103ccd - [android][ios] add support for development loads in expo-updates AppLoader (#9599)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#70103ccd</link>
        <description>[android][ios] add support for development loads in expo-updates AppLoader (#9599)# WhyFollow up to #9461 and #9523 . The development client&apos;s `AppLoader` classes are used to load manifests for both development and production bundles, but expo-updates is not intended to be used to load projects in development. We need to bypass expo-updates&apos; caching and database layers for development mode loads.# HowUnfortunately we cannot reliably determine before loading a manifest whether it is for a development or production mode project. Instead, I&apos;ve added/expanded upon the ability of the calling class to abort a `LoaderTask` upon its cached/remote manifest callback being fired.Now, the new ExpoUpdatesAppLoader classes will check for development mode at 3 separate stages -- 1) before starting the load, if the URL is clearly indicative of a project in development, 2) when the cached manifest is returned, and 3) when the remote manifest is loaded. If it determines at any of these three stages that it&apos;s trying to load a development mode project, it will abort the `LoaderTask` early and delegate to RN to load the development bundle, similar to how the current, non-expo-updates AppLoader classes in both clients work.# Test PlanManual tests of loading a development mode project on both platforms, after enabling the ExpoUpdatesAppLoader class in Kernel.java/EXKernelAppRecord.m. Also ensured that loading production experiences did not break.

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Wed, 12 Aug 2020 03:36:48 +0000</pubDate>
        <dc:creator>Eric Samelson &lt;esamelson@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>607c2bf5 - Remove obsolete kernel service EXGoogleAuthManager (#5660)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#607c2bf5</link>
        <description>Remove obsolete kernel service EXGoogleAuthManager (#5660)

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Mon, 16 Sep 2019 14:15:56 +0000</pubDate>
        <dc:creator>Szymon20000 &lt;szymon20000@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8e23f9f5 - [ios][android] Drop SDK 31 and 32 (#5381)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#8e23f9f5</link>
        <description>[ios][android] Drop SDK 31 and 32 (#5381)# Whyresolves: https://github.com/expo/expo/issues/5146# HowUsing `et rm-sdk` expotools command.# Test PlanRun NCL.

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Tue, 20 Aug 2019 13:50:09 +0000</pubDate>
        <dc:creator>Szymon20000 &lt;szymon20000@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>b6008592 - [expo-branch] First 3rd party library unimodule wrapper! (#5165)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#b6008592</link>
        <description>[expo-branch] First 3rd party library unimodule wrapper! (#5165)We would like to provide a way to users to optionally include `react-native-branch` in their standalone apps. Fixes https://github.com/expo/expo/issues/5132.I added support for React Native-specific unimodules to React Native adapter. Right now it works like this:- unimodule `expo-branch` depends on `react-native`, so it can use its API. It&apos;s no longer a uni-platform module, more an optinmodule (I guess the name won&apos;t stick)- we copy `react-native-branch` vendored module directly to the unimodule. It will compile, since we added necessary dependencies to the unimodule- `BranchPackage &lt; org.unimodules.Package` implements `ReactPackage` interface too, forwarding all the calls to the vendored `RNBranchPackage`.- when the module registry provider creates a module registry from a list of `Packages`, it can filter out `ReactPackages` &#8212; and so it does, putting them into a local internal module (`ReactPackagesProvider`) which only purpose is to carry those to `ModuleRegistryAdapter` which is responsible for creating a list of React Native modules out of a module registry. The adapter grabs the `ReactPackagesProvider` and adds React Native modules to the list.I have confirmed that adding `BranchPackage` to a list of installed unimodules&apos; packages creates `RNBranchModule` and exports to JS.

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Tue, 06 Aug 2019 13:17:13 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>636b55ab - [expo-branch] First 3rd party library unimodule wrapper! (#5165)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#636b55ab</link>
        <description>[expo-branch] First 3rd party library unimodule wrapper! (#5165)# WhyWe would like to provide a way to users to optionally include `react-native-branch` in their standalone apps. Fixes https://github.com/expo/expo/issues/5132.# HowI added support for React Native-specific unimodules to React Native adapter. Right now it works like this:- unimodule `expo-branch` depends on `react-native`, so it can use its API. It&apos;s no longer a uni-platform module, more an optinmodule (I guess the name won&apos;t stick)- we copy `react-native-branch` vendored module directly to the unimodule. It will compile, since we added necessary dependencies to the unimodule- `BranchPackage &lt; org.unimodules.Package` implements `ReactPackage` interface too, forwarding all the calls to the vendored `RNBranchPackage`.- when the module registry provider creates a module registry from a list of `Packages`, it can filter out `ReactPackages` &#8212; and so it does, putting them into a local internal module (`ReactPackagesProvider`) which only purpose is to carry those to `ModuleRegistryAdapter` which is responsible for creating a list of React Native modules out of a module registry. The adapter grabs the `ReactPackagesProvider` and adds React Native modules to the list.# Test PlanI have confirmed that adding `BranchPackage` to a list of installed unimodules&apos; packages creates `RNBranchModule` and exports to JS.

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Tue, 06 Aug 2019 13:17:13 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>7100de8c - [ios] Upgrade notifications framework to User Notifications Framework (#2316)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#7100de8c</link>
        <description>[ios] Upgrade notifications framework to User Notifications Framework (#2316)* Updated notificationsMoved new permissions files to packagesfixupdated yarn.lockfixesRequested changesfix  after rabaseMade requested changesRenamed UserNotificationCenterProxy classesRun `pod install`* Post-review fixes* Minor JS fixes* Do not remember pending notifications in Expo Client (behavior matching previous one)* Prevent blocking main queue at all times by EXUserNotificationRequester* Do not scope categories identifiers in ejected applications* Apply review comments* Remove obsolete if condition* Do not store resolver and rejecter in EXUserNotificationRequester* Update Pods* Add support for deleting custom notification categories* Pass notification to a remembered experience when tapped a notification in backgrounded Expo Client* Update jest-expo mocks* Ensure permissions consuming happens on permissions queue in EXRemoteNotificationRequester* Do not scope notification identifiers* Change cancelScheduledNotification into cancelScheduledNotificationAsync returning native Promise* Deny scheduleNotificationAsync with both time and repeat set on iOS* Allow scheduleNotificationAsync with both time and repeat set on iOS using deprecated UILocalNotification* Add more notification testing buttons to NCL* Export EXUserNotificationManager service as kernel service* Add EXNotificationsIdentifiersManager protocol capable of scoping and unscoping identifiers* Require both RemoteNotificationManager and UserNotificationManager in EXNotifications module* Scope and unscope action identifiers by EXUserNotificationManager* Update pods

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Mon, 03 Dec 2018 16:36:04 +0000</pubDate>
        <dc:creator>Szymon20000 &lt;szymon20000@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>022bf92a - Register singleton modules with a macro (#2914)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#022bf92a</link>
        <description>Register singleton modules with a macro (#2914)* [ios] Register singleton modules with macro* [ios] Singleton modules fixes:- move EXPermissionsManager to expo-permissions package,- remove sharedInstance from EXSingletonModule- add name argument to EX_REGISTER_SINGLETON_MODULE- add singleton modules to EXHomeAppManager* [ios][expo-core] Remove obsolete variable definition* [ios] Remove EXSingletonModule references from EXModuleRegistry and EXModuleRegistryProvider* [ios] Add EX_EXPO_CLIENT macro definition* [ios] Remove EX_EXPO_CLIENT preprocessor definition in favor of setting SupportsAppMultiplexing in Info.plist* [ios] Suppress warnings about not being able to call -name on EXSingletonModule classes instances* [ios] Update podsfbshipit-source-id: 3cf91c0

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Fri, 17 Aug 2018 15:54:55 +0000</pubDate>
        <dc:creator>Stanis&#322;aw Chmiela &lt;sjchmiela@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>3980c593 - make modals play well with expo menu (#2379)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#3980c593</link>
        <description>make modals play well with expo menu (#2379)fbshipit-source-id: 251bdc0

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Wed, 09 May 2018 17:26:27 +0000</pubDate>
        <dc:creator>Tomasz Sapeta &lt;tsapeta@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>62dd6356 - Permissions per experience (#2161)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#62dd6356</link>
        <description>Permissions per experience (#2161)* [android] Permissions module - ask for permissions per experience* [android] Do not check/request permissions on the native side; customize the perm dialog* [expo-sdk] Check permissions before invoking native method* Revert &quot;[expo-sdk] Check permissions before invoking native method&quot;This reverts commit f20c90d7622ec00d206a7e116f70f5c63714e1e0.* [android] DO check permissions on the native side but do not request* [ios] Scoped permissions - wip* [ios] Proper perm in dialog; save user defaults correctly* [ios] Check permissions when required* [ios] Review updates* [ios] Multiple kernel services fixes* [android] Permissions per experience for Android &lt; M* [android] Change shape of permissions in metadata; further refactor for older Android APIs* [android] Apply changes to previous SDKs* [ios] Apply changes to previous SDKsfbshipit-source-id: 328961f

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Fri, 13 Apr 2018 21:27:58 +0000</pubDate>
        <dc:creator>Alicja Warcha&#322; &lt;aa.warchal@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>30fccd70 - Updates module (#2203)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#30fccd70</link>
        <description>Updates module (#2203)fbshipit-source-id: 477c902

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Fri, 16 Mar 2018 19:15:30 +0000</pubDate>
        <dc:creator>Eric Samelson &lt;esamelson@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>89c6c39c - OTA Updates improvements (#1925)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#89c6c39c</link>
        <description>OTA Updates improvements (#1925)* [android] fetch updated manifest on launch and allow specified amount of time to do this before populating experienceactivity* [android] only consume response once in onCachedResponse* [android] removed CountDownTimer in favor of Handler.postDelayed* [WIP][android] moved all new manifest loading code to new methods with AtomicBundleListener rather than ManifestListener* [android] moved JS bundle loading to before populating experienceactivity* [android] refactored most of the new logic into its own AtomicBundleListener class per conversation with Jesse* [ios][wip] beginning ios changes* [ios] WIP* [ios] more wip, have full manifest-fetching logic in AtomicBundleManager* [ios] reverted changes to bridgeRecord in favor of creating new AppRegistry and AppRecord classes; will eventually refactor everything to use these rather than BridgeRegistry; getManifestAsync now uses AtomicBundleManager for fetching manifest* [ios] wip, start on bundle loading* [ios] wip wip wip. not sure how much of the logic to be moving from EXFrameReactAppManager to new class - maybe should keep _jsResource logic in original* [ios] bundle loading now working from atomic bundle manager* [ios] renamed new class to AtomicBundleLoader to avoid using word Manager* [ios] trying to get reloading to work again; there is some weird issue with objc/js communication but going to save it for later* [ios] wip with adding js bundle loading into timeout - currently just setting a timeout directly on the request* [ios] bundle loading part of timeout* [ios] renaming methods to use underscore prefix* [ios] fully replace EXKernelBridgeRegistry and BridgeRecord with AppRegistry and AppRecord* [ios] refactor request bundle method to use FrameReactAppManager as delegate* [ios] renamed AtomicBundleLoader to AppLoader per Ben&apos;s suggestion* [ios] step 1 in resolving reloading issue* [ios] fix reloading on ios -- now using a UUID to identify record rather than manifestUrl, and we enforce uniqueness after the entire manifest/bundle is loaded to give time for the other record to be removed. Also, changed _appRegistry to an NSMutableDictionary, since NSMapTable was no longer needed and NSMutableDictionary is easier to copy -- safer since we&apos;re mixing mutations &amp; enumeration more.* [ios] a couple more fixes to make sure we&apos;re handling possible duplicate AppRecords properly* [ios] better handling of various cases with possible inconsistencies/network errors* [ios] add loadedFromCache key to manifest* [ios] separated resolveWithCachedManifest and resolveWithCachedBundle to avoid situation where resolveWithCachedManifest is called with an error after manifest _finished == YES and therefore bundle never gets fetched* [android] added loadedFromCache key to manifest, not sure why it&apos;s always false...* [android] loadedFromCache manifest key working now* [android] prevent onManifestCompleted from being called twice* [ios] EXKernelAppLoader - control downloading bundle entirely, and don&apos;t resolve with manifest until after bundle has been downloaded successfully* [ios] removed now obsolete EXKernelBundleLoaderDelegate methods* [home] first step in loading progress fix - move manifest and bundleUrl fetching to a separate flux action, and allow a BrowserScreen to be mounted to show loading progress before manifest is fetched* [ios][home] bundle loading progress now showing; need to show assets/icon properly, and resolve occasional crash when bundle download reaches 100%* [home] fixed missing icons and name in project history* [ios][home] send new manifest optimistically to JS as soon as we receive it so that JS can show the correct icon and background color on loading screen* [home] moved some logic from BrowserActions to Browser to try and keep actions more pure* [ios] fix for opening client from a notification - previously an EXKernelAppRecord was never created in this case. Might want to think about only ever creating AppRecords when the manifest is requested* [home] improve safety/handling of optimisticManifest* [home] fix for standalone apps where props.task is initially null* [ios] pass recordId into frame so it can use this to unregister itself safely instead of trying to iterate through all of the records to find a potentially non-unique experienceId. Also, register AppRecords when manifest is requested as there is no reason for them to exist before this* [ios] add new EXCachedResourceBehavior to never read from the cache but make sure we are always writing to it* [android] don&apos;t send manifest or bundle until we have either downloaded a new bundle or timed out* [android] only write the manifest that we are actually using to shared preferences* [android] correct loadedFromCache value (again)* [android] fix loading icon and progress for dev mode - don&apos;t try and download the bundle in exponent code* [android] send optimistic manifest to ExperienceActivity as soon as we download it so that the activity can display the proper loading screen/icon/task info* [android] use AtomicBundleListener for detached and shell apps as well* [android] make sure that AtomicBundleListener is the only thing that is calling loadJSBundle (for non-kernel bundles)* [android] fix opening detached apps after the first run* [android] improve handling of failures* [home] stop accidentally swallowing errors wfrom fetching manifest on iOS* [ios] clean up stopTimer usage, as anytime we call _resolve we don&apos;t want to call it again* [ios] simplify timeout on JS bundle fetching - since the NSTimer will take care of resolving anyway, we don&apos;t need to set the timeout on the JS bundle request based on the timer* [android] renamed AtomicBundleListener to AppLoader as this is a better description of what it does* [server] updated unversioned schema with new app.json fields* [ios][android] make sure to only fetch remote manifest if the shouldCheckForUpdate is true* [android] if in dev mode, skip the cached manifest + set timer step and just go fetch the remote manifest every time* [ios][android] stop making bad assumptions -- if  a cached manifest exists, it is possible that the corresponding bundle does not exist for some reason, and in this case we should download rather than failing to user* [ios] resolved first cycle of ben&apos;s comments* [ios][home] resolved some of ben&apos;s 2nd round of comments* [ios] resolved most of ben&apos;s 3rd round of comments&apos;* [ios][server] resolved a few more comments* [ios] added status enum property to EXKernelAppRecord &amp; so that kernel services can skip over any AppRecords which are partially loaded* [ios] add todo to get rid of lazy copy workaround* [android] resolve jesse&apos;s comments* [android] store loading errors in ExponentSharedPreferences, and make sure that we always try to load a new manifest + bundle if this is set to true when loading experience* [ios] resolved last of Ben&apos;s comments, including adding a way for AppRecord to be notified when bridge has successfully loaded JS* [schema] mark loadJSInBackgroundExperimental as deprecated* [android] fix loading apps for the first time in dev modefbshipit-source-id: 4d763d0

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Wed, 14 Feb 2018 05:19:28 +0000</pubDate>
        <dc:creator>Eric Samelson &lt;esamelson@users.noreply.github.com&gt;</dc:creator>
    </item>
<item>
        <title>aa1f6391 - Improve assets bundle runtime implementation, support most asset types (#1691)</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#aa1f6391</link>
        <description>Improve assets bundle runtime implementation, support most asset types (#1691)fbshipit-source-id: d3045f7

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Sat, 13 Jan 2018 01:01:29 +0000</pubDate>
        <dc:creator>Janic Duplessis &lt;janicduplessis@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>8a7f6184 - Move EXKernelModuleDelegate into separate kernel module service</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#8a7f6184</link>
        <description>Move EXKernelModuleDelegate into separate kernel module servicefbshipit-source-id: 3c5c0112cd

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Tue, 11 Jul 2017 18:03:15 +0000</pubDate>
        <dc:creator>Ben Roth &lt;spongebucket@gmail.com&gt;</dc:creator>
    </item>
<item>
        <title>9f8d9b9d - Formalize `EXKernelService` protocol, allow services to listen to bridge lifecycle of all apps</title>
        <link>http://172.16.0.5:8080/history/expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h#9f8d9b9d</link>
        <description>Formalize `EXKernelService` protocol, allow services to listen to bridge lifecycle of all appsfbshipit-source-id: 20d02633d2

            List of files:
            /expo/apps/eas-expo-go/ios/Exponent/Kernel/Core/EXKernelServiceRegistry.h</description>
        <pubDate>Tue, 11 Jul 2017 02:15:08 +0000</pubDate>
        <dc:creator>Ben Roth &lt;spongebucket@gmail.com&gt;</dc:creator>
    </item>
</channel>
</rss>
