Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[RNScreens] Failed to initialise dummy layout in onHostResume. This is not expected. Android #2324

Closed
Kabeer-Haseja opened this issue Aug 29, 2024 · 10 comments
Labels
Missing info The user didn't precise the problem enough Missing repro This issue need minimum repro scenario Platform: Android This issue is specific to Android

Comments

@Kabeer-Haseja
Copy link

Kabeer-Haseja commented Aug 29, 2024

Description

when we run app we are getting this
versions that i am using
"react-native": "0.75.2",
"react-native-safe-area-context": "^4.10.9",
"react-native-screens": "^3.34.0",

and kotlin version
kotlinVersion = "1.9.24"
Screenshot_20240829_115709

Steps to reproduce

just update the react native screen

Snack or a link to a repository

..

Screens version

3.34.0

React Native version

0.75.2

Platforms

Android

JavaScript runtime

None

Workflow

None

Architecture

Fabric (New Architecture)

Build type

Release mode

Device

Android emulator

Device model

No response

Acknowledgements

Yes

Copy link

github-actions bot commented Aug 29, 2024

Hey! 👋

It looks like you've omitted a few important sections from the issue template.

Please complete Snack or a link to a repository section.

@github-actions github-actions bot added the Missing info The user didn't precise the problem enough label Aug 29, 2024
Copy link

Hey! 👋

The issue doesn't seem to contain a minimal reproduction.

Could you provide a snack or a link to a GitHub repository under your username that reproduces the problem?

@github-actions github-actions bot added Missing repro This issue need minimum repro scenario Platform: Android This issue is specific to Android labels Aug 29, 2024
@kkafar
Copy link
Member

kkafar commented Aug 29, 2024

@Kabeer-Haseja can you provide us with reproduction / stack trace at least? You might also want to try out 3.35.0-rc.1 version of the library

@Kabeer-Haseja
Copy link
Author

@kkafar when i enable new architecture newArchEnabled=true and run the app it come up with the that screen that i already showed to you

@kkafar
Copy link
Member

kkafar commented Aug 29, 2024

@Kabeer-Haseja Thats understandable, but it does not happen for me.
Have you tried out 3.35.0-rc.1? It might be already patched.

@kkafar kkafar added the Close when stale This issue is going to be closed when there is no activity for a while label Aug 29, 2024
@Kabeer-Haseja
Copy link
Author

Hi @kkafar,

I encountered an issue while trying to install [email protected]. The other packages, such as:

•	@react-navigation/bottom-tabs: ^6.6.1
•	@react-navigation/native: ^6.1.18
•	@react-navigation/native-stack: ^6.11.0
•	@react-navigation/stack: ^6.4.1

are not supported after the installation.

Here’s what I did to install [email protected] (though it’s not an ideal approach):

1.	Removed react-native-screens package: I started by removing the existing react-native-screens package.
2.	Ran npm install: After removing the package, I ran npm install to install all the remaining dependencies.
3.	Reinstalled react-native-screens: Finally, I installed [email protected].

However, when I tried to add all the packages back together and ran npm install, I encountered errors with the packages mentioned above.

@github-actions github-actions bot removed the Close when stale This issue is going to be closed when there is no activity for a while label Aug 30, 2024
@LinhLM23496
Copy link

+1

@sanchezzzs
Copy link

sanchezzzs commented Sep 6, 2024

same problem on armv8 with newArchEnabled=true, armv7 works fine.
"react-native-screens": "^3.34.0"

UPD:

changing MainApplication

if (BuildConfig.IS_NEW_ARCHITECTURE_ENABLED) {
            load()
}

to

if (BuildConfig.IS_NEW_ARCHITECTURE_ENABLED) {
            load(bridgelessEnabled=false)
}

solved the problem

@abrah4mr
Copy link

@kkafar Seems to work with 3.35.0-rc.1 version.

I have RN 0.75 with the flag enabled, and once I installed the rc version it work.

@kkafar
Copy link
Member

kkafar commented Sep 25, 2024

I'll close the issue, since the fix is already merged & released with rc version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Missing info The user didn't precise the problem enough Missing repro This issue need minimum repro scenario Platform: Android This issue is specific to Android
Projects
None yet
Development

No branches or pull requests

5 participants