<?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: Pascu Eduard</title>
    <description>The latest articles on DEV Community by Pascu Eduard (@pascu_eduard_e6badc572f36).</description>
    <link>https://dev.to/pascu_eduard_e6badc572f36</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4208925%2Fcaf14be0-be27-43f1-9830-3460eb0e7919.png</url>
      <title>DEV Community: Pascu Eduard</title>
      <link>https://dev.to/pascu_eduard_e6badc572f36</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pascu_eduard_e6badc572f36"/>
    <language>en</language>
    <item>
      <title>What Actually Breaks When You Bump targetSdkVersion to 36 (and How to Fix It)</title>
      <dc:creator>Pascu Eduard</dc:creator>
      <pubDate>Mon, 26 Oct 2026 14:13:53 +0000</pubDate>
      <link>https://dev.to/pascu_eduard_e6badc572f36/what-actually-breaks-when-you-bump-targetsdkversion-to-36-and-how-to-fix-it-1l1g</link>
      <guid>https://dev.to/pascu_eduard_e6badc572f36/what-actually-breaks-when-you-bump-targetsdkversion-to-36-and-how-to-fix-it-1l1g</guid>
      <description>&lt;p&gt;Google Play requires target API 36 from November 1, 2026 (extension available in Play Console). If you've been putting off the upgrade, here's what's actually going to break — and it's not the version bump.&lt;/p&gt;

&lt;h2&gt;
  
  
  The version bump is the easy part
&lt;/h2&gt;

&lt;p&gt;Changing &lt;code&gt;targetSdkVersion&lt;/code&gt; to 36 in your &lt;code&gt;build.gradle&lt;/code&gt; or &lt;code&gt;app.json&lt;/code&gt; takes 30 seconds. What happens next is the real work.&lt;/p&gt;

&lt;h2&gt;
  
  
  The edge-to-edge trap
&lt;/h2&gt;

&lt;p&gt;&lt;strong&gt;API 36 removes the edge-to-edge opt-out.&lt;/strong&gt; On Android 15 (API 35), you could add this to your theme to keep the old behavior:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight xml"&gt;&lt;code&gt;&lt;span class="nt"&gt;&amp;lt;item&lt;/span&gt; &lt;span class="na"&gt;name=&lt;/span&gt;&lt;span class="s"&gt;"android:windowOptOutEdgeToEdgeEnforcement"&lt;/span&gt;&lt;span class="nt"&gt;&amp;gt;&lt;/span&gt;true&lt;span class="nt"&gt;&amp;lt;/item&amp;gt;&lt;/span&gt;
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;p&gt;On API 36, &lt;strong&gt;this no longer works.&lt;/strong&gt; Your app content will draw behind the status bar and gesture area unless you handle insets on every screen.&lt;/p&gt;

&lt;p&gt;If you use &lt;code&gt;Theme.AppCompat.Light.DarkActionBar&lt;/code&gt; and rely on the default Action Bar, your content will start appearing &lt;em&gt;behind&lt;/em&gt; the action bar. If you have bottom navigation, it'll be hidden behind the gesture pill.&lt;/p&gt;

&lt;h2&gt;
  
  
  The fix (the part nobody prices correctly)
&lt;/h2&gt;

&lt;p&gt;For React Native / Expo:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Use &lt;code&gt;react-native-safe-area-context&lt;/code&gt; for proper edge-to-edge layout&lt;/li&gt;
&lt;li&gt;React Native 0.81+ has &lt;code&gt;edgeToEdgeEnabled&lt;/code&gt; Gradle property&lt;/li&gt;
&lt;li&gt;Check every screen for status bar / navigation bar overlap&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;For native Android:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Call &lt;code&gt;WindowCompat.enableEdgeToEdge(window)&lt;/code&gt; after &lt;code&gt;super.onCreate()&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Use &lt;code&gt;WindowInsetsCompat&lt;/code&gt; to add padding where content overlaps system bars&lt;/li&gt;
&lt;li&gt;
&lt;code&gt;android:fitsSystemWindows="true"&lt;/code&gt; on root layouts is a quick fix&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  What else changes
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;
&lt;strong&gt;Predictive back&lt;/strong&gt; is enforced — test your back button handling&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;StatusBar &lt;code&gt;backgroundColor&lt;/code&gt; and &lt;code&gt;translucent&lt;/code&gt; props stop working&lt;/strong&gt; (use &lt;code&gt;react-native-edge-to-edge&lt;/code&gt; instead)&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;Modal &lt;code&gt;statusBarTranslucent&lt;/code&gt; and &lt;code&gt;navigationBarTranslucent&lt;/code&gt;&lt;/strong&gt; are always &lt;code&gt;true&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;App orientation/size restrictions ignored on large screens&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;
&lt;strong&gt;&lt;code&gt;adjustPan&lt;/code&gt; keyboard behavior is broken&lt;/strong&gt; in edge-to-edge mode&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  My 12-step checklist
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Bump &lt;code&gt;targetSdkVersion&lt;/code&gt; to 36&lt;/li&gt;
&lt;li&gt;Build and note every visual regression&lt;/li&gt;
&lt;li&gt;Fix edge-to-edge insets on every screen (the big one)&lt;/li&gt;
&lt;li&gt;Test on Android 15+ physical devices&lt;/li&gt;
&lt;li&gt;Check status bar, navigation bar, gesture area&lt;/li&gt;
&lt;li&gt;Test keyboard behavior&lt;/li&gt;
&lt;li&gt;Verify predictive back works&lt;/li&gt;
&lt;li&gt;Check landscape/large screen behavior&lt;/li&gt;
&lt;li&gt;Test modal and bottom sheet rendering&lt;/li&gt;
&lt;li&gt;Verify no content draws under cutouts&lt;/li&gt;
&lt;li&gt;Run full test suite&lt;/li&gt;
&lt;li&gt;Build release AAB and verify on device&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;I also have a diagnosis script and verification script — if you're stuck, I put together a rescue kit: &lt;a href="https://payhip.com/b/uLfXa" rel="noopener noreferrer"&gt;Expo API-36 Android Release Rescue Kit&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Good luck before Nov 1 — it sneaks up fast.&lt;/p&gt;




&lt;p&gt;&lt;em&gt;Disclosure: This post references my own product.&lt;/em&gt;&lt;/p&gt;

</description>
      <category>reactnative</category>
    </item>
  </channel>
</rss>
