[Android] Invoking setProperty on null object ref (RN 0.79+ support)

[akuul]

Description

With the release of React Native 0.79, SafeAreaView on Android started giving an error. I saw a similar issue, but decided to open a new one with more context. iOS works fine.

Attempt to invoke interface method 'void com.facebook.react.uimanager.ViewManagerDelegate.setProperty(android.view.View, java.lang.String, java.lang.Object)' on a null object reference

This is probably related to the facebook/react-native#48602 commit.

This purely happens with the SafeAreaView. Replacing with the one from React Native works fine.

Steps to reproduce

1. Wrap component with SafeAreaView and start app on Android

Snack or a link to a repository

Safe Area Context version

5.3.0

React Native version

0.79.0

Platforms

Android

Architecture

Fabric (New Architecture)

Build type

Debug mode

Device

Android emulator

Device model

Pixel 9

Acknowledgements

Yes

[lucasFigueira1]

I'm experiencing this same problem

[KestasVenslauskas]

Yup same problem

[MohamedAbdElmoniem]

same

[adolfogc]

I'm facing the same issue, temporarily using RN's solved it:

// import {SafeAreaView} from 'react-native-safe-area-context';

import { SafeAreaView } from 'react-native';

[KunaalMangal]

I'm experiencing the same issue. After removing the SafeAreaView from react-native-safe-area-context, everything started working fine.

[djangoamidala]

if you want to fix it you can use this
you just get the Insets and use it in your own view, perfectly working everywhere and no error :)

import React from 'react';
import { View } from 'react-native';
import { useSafeAreaInsets } from 'react-native-safe-area-context';

export const SafeView = ({ children, style }) => {
const insets = useSafeAreaInsets();

const top = typeof insets.top === 'number' ? insets.top : 0;
const bottom = typeof insets.bottom === 'number' ? insets.bottom : 0;
const left = typeof insets.left === 'number' ? insets.left : 0;
const right = typeof insets.right === 'number' ? insets.right : 0;

return (
<View
style={[
{
paddingTop: top,
paddingBottom: bottom,
paddingLeft: left,
paddingRight: right,
},
style,
]}
>
{children}

);
};

export default SafeView;

[jbrodriguez]

spent 2 installs from scratch thinking it was something about react-native-screens or reanimated setup

google search didn't bring this issue up, had to trial/error discard components until i figured it out

😐

hopefully gets solved soon

[baharudin-yusup]

Same here

[AngeloMancilla]

// import {SafeAreaView} from 'react-native-safe-area-context';

import { SafeAreaView } from 'react-native';

This solved the problem in my case <3

[ahmed-lotfy-dev]

same here it got resoved by using react native's save area view

import { SafeAreaView } from 'react-native';

[prakashmaharayt980]

i spend 2 days on this
finaly it work thank for report

[diegolmello]

I can confirm #610 fixed it.

[beydogan]

I'm still having same issue on android prebuilds(without expo go), using react-native-safe-area-context@5.4.0 and react-native@0.79.2

Workarounds don't work either because expo-router has peer dependency to react-native-safe-area-context. So app doesn't boot on android.