<?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 NativeErrorManager.d.ts.map</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2015</copyright>
    <generator>Java</generator><item>
        <title>6d19a6af - [sweet][kotlin] Add basic &apos;LogBox&apos; integration (#15834)</title>
        <link>http://172.16.0.5:8080/history/expo/packages/expo-modules-core/build/sweet/NativeErrorManager.d.ts.map#6d19a6af</link>
        <description>[sweet][kotlin] Add basic &apos;LogBox&apos; integration (#15834)# WhyWhen something goes wrong when invoking prop setters, we can&apos;t inform the user about it. Previously, we just ignored such a case and logged the exception to the native console. However, it isn&apos;t ideal in a long run. So, I&apos;ve added a simple `LogBox` integration to display exceptions there. # HowUnfortunately, `LogBox` doesn&apos;t have a native API. To display something in it, I have to send an exception to js (as an event) and log it there. I&apos;ve created a new module that is registered in the kotlin bridge. This module isn&apos;t necessary on Android, but it&apos;s helpful. Moreover, we will need it on iOS. &gt; Note:I&apos;ve changed how we obtain `NativeUnimoduleProxy` from the react context. The old way wasn&apos;t working in every case.# Test Plan- bare-expo &#9989;(This error was thrown in prop setter)![image](https://user-images.githubusercontent.com/9578601/148577303-cfd86502-784d-4658-808f-02c79f0d0296.png)

            List of files:
            /expo/packages/expo-modules-core/build/sweet/NativeErrorManager.d.ts.map</description>
        <pubDate>Wed, 26 Jan 2022 12:09:45 +0000</pubDate>
        <dc:creator>&#321;ukasz Kosmaty &lt;lukasz.kosmaty@swmansion.com&gt;</dc:creator>
    </item>
</channel>
</rss>
