<?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: Bartmr</title>
    <description>The latest articles on DEV Community by Bartmr (@bartmr).</description>
    <link>https://dev.to/bartmr</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%2F52872%2Fa1f0de2d-9968-4fc5-a4b5-643fe2e126a3.jpeg</url>
      <title>DEV Community: Bartmr</title>
      <link>https://dev.to/bartmr</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/bartmr"/>
    <language>en</language>
    <item>
      <title>Real life example of why you should sort your code by features, and not by technical layers like MVC</title>
      <dc:creator>Bartmr</dc:creator>
      <pubDate>Thu, 22 Aug 2019 11:34:08 +0000</pubDate>
      <link>https://dev.to/bartmr/real-life-example-of-why-you-should-sort-your-code-by-features-and-not-by-technical-layers-like-mvc-18n</link>
      <guid>https://dev.to/bartmr/real-life-example-of-why-you-should-sort-your-code-by-features-and-not-by-technical-layers-like-mvc-18n</guid>
      <description>&lt;p&gt;Practical example of why you should sort your code by feature (users, notes, analytics) instead of technical layer (models, views, controllers, etc)&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--Q8k69Fde--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/cgktf35grkh71pdmvokn.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--Q8k69Fde--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/cgktf35grkh71pdmvokn.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

</description>
    </item>
    <item>
      <title>Not being able to run a React Native or Cordova project after 17th of July, because of AndroidX and Google Play Services</title>
      <dc:creator>Bartmr</dc:creator>
      <pubDate>Tue, 25 Jun 2019 18:14:50 +0000</pubDate>
      <link>https://dev.to/bartmr/not-being-able-to-run-a-react-native-or-cordova-after-17th-of-july-because-of-androidx-and-google-play-services-dop</link>
      <guid>https://dev.to/bartmr/not-being-able-to-run-a-react-native-or-cordova-after-17th-of-july-because-of-androidx-and-google-play-services-dop</guid>
      <description>&lt;p&gt;After the &lt;a href="https://developers.google.com/android/guides/releases#june_17_2019"&gt;17th of July update to the Google Play Services&lt;/a&gt;, some of you who've cleaned up your React Native Android project before a build, might have encountered an error similar to this&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;Attribute application@appComponentFactory value=(android.support.v4.app.CoreComponentFactory) from [com.android.support:support-compat:28.0.0] AndroidManifest.xml:22:18-91
        is also present at [androidx.core:core:1.0.0] AndroidManifest.xml:22:18-86 value=(androidx.core.app.CoreComponentFactory).
        Suggestion: add 'tools:replace="android:appComponentFactory"' to &amp;lt;application&amp;gt; element at AndroidManifest.xml:52:5-309:19 to override.
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;For normal Android applications, the solution is just &lt;a href="https://developer.android.com/jetpack/androidx/migrate"&gt;migrating to AndroidX&lt;/a&gt; and whatever isn't using AndroidX, Gradle deals with converting the import statements on build time by using &lt;strong&gt;Jetifier&lt;/strong&gt;. But Gradle's &lt;strong&gt;Jetifier&lt;/strong&gt; only works on already packaged Android modules. &lt;strong&gt;It doesn't work on native React Native modules&lt;/strong&gt; that bring their full native source code projects intact, and are compiled when you start your React Native app.&lt;/p&gt;

&lt;p&gt;For those cases, the solution is:&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;Install &lt;a href="https://www.npmjs.com/package/jetifier"&gt;this package&lt;/a&gt; and follow its instructions. If your project still doesn't start after that, follow the extra steps below...&lt;/li&gt;
&lt;li&gt;Go to your &lt;code&gt;android/app/build.gradle&lt;/code&gt; file, and exchange all dependencies that are inside the Arctifact Mappings section in the &lt;a href="https://developer.android.com/jetpack/androidx/migrate"&gt;AndroidX Migration guide&lt;/a&gt; with the new AndroidX build artifact paths.&lt;/li&gt;
&lt;li&gt;Go to your own native code inside &lt;code&gt;android/app/src&lt;/code&gt; and do the same with the import statements refering to the Old build artifacts&lt;/li&gt;
&lt;li&gt;Run your app again.&lt;/li&gt;
&lt;li&gt;Comment this post :D&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;Good luck. BTW, first article here on DEV.TO&lt;/p&gt;

</description>
      <category>reactnative</category>
      <category>android</category>
      <category>javascript</category>
      <category>react</category>
    </item>
  </channel>
</rss>
