<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: Dragos11</title>
    <description>The latest articles on DEV Community by Dragos11 (@dragos11).</description>
    <link>https://dev.to/dragos11</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F46079%2F6512776e-8667-4f69-9b6d-3726a8c6e98c.png</url>
      <title>DEV Community: Dragos11</title>
      <link>https://dev.to/dragos11</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/dragos11"/>
    <language>en</language>
    <item>
      <title>React Native: Cross-platform differences</title>
      <dc:creator>Dragos11</dc:creator>
      <pubDate>Thu, 13 Dec 2018 11:12:53 +0000</pubDate>
      <link>https://dev.to/dragos11/react-native-cross-platform-differences-3e2</link>
      <guid>https://dev.to/dragos11/react-native-cross-platform-differences-3e2</guid>
      <description>

&lt;p&gt;Hello, in this article I tried to give you some examples about the differences that you may encounter when using React Native components. Some quick tips and heads-up about these "problems"&lt;/p&gt;

&lt;p&gt;&lt;a href="https://catalinxyz.com/react-native-cross-platform-or-not/"&gt;https://catalinxyz.com/react-native-cross-platform-or-not/&lt;/a&gt;&lt;/p&gt;


</description>
      <category>reactnative</category>
      <category>crossplatform</category>
      <category>javascript</category>
    </item>
    <item>
      <title>React-Native Modals Problems</title>
      <dc:creator>Dragos11</dc:creator>
      <pubDate>Wed, 22 Nov 2017 11:54:33 +0000</pubDate>
      <link>https://dev.to/dragos11/react-native-modals-problems-5d0</link>
      <guid>https://dev.to/dragos11/react-native-modals-problems-5d0</guid>
      <description>&lt;p&gt;Ok, the problem is the following one: I try to render a modal that has a loader (ActivityIndicator as the native-component) and it is preceded by an Alert. &lt;/p&gt;

&lt;p&gt;The modal is showed while the call to the API is on loading and the response hasn't arrived. When the response has come the Alert is rendered. For some reasons the ios closes the alert immediately and the modal with the loader remains on the screen forever. You have to close the app in order to get rid of it. &lt;/p&gt;

&lt;p&gt;After some documentation I found that the alert native component is deep inside a modal and I think that the iOS loses track of the modals he has to close. After some brainstorming with some better developers than me(almost everyone) we found a solution: SetTimeOut(), even with 0(practically instant) so the iOS has time to decide what modals to close. Happy Happy, Joy Joy for about 2 or 3 days when we tested the app on some devices. The devices can't close the modals as it should. So I decided to look better on the dearest friend of man, the internet. I tried looking if react-native offers an &lt;em&gt;onModalClose&lt;/em&gt; method and I found out that there was such a method, but only on the rc. So the only chance is to wait for the next release. Come on REACT :D&lt;/p&gt;

</description>
      <category>react</category>
      <category>native</category>
      <category>modal</category>
      <category>alert</category>
    </item>
  </channel>
</rss>
