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

[Android] ReactRootView layout configuration inside native app #13476

Closed
ahetawal-p opened this issue Apr 12, 2017 · 3 comments
Closed

[Android] ReactRootView layout configuration inside native app #13476

ahetawal-p opened this issue Apr 12, 2017 · 3 comments
Labels
Resolution: Locked This issue was locked by the bot.

Comments

@ahetawal-p
Copy link

Trying to add a ReactRootView to my existing layout which looks like this

ReactRootView contentView = new ReactRootView(context);
LinearLayout container = (LinearLayout) parent.findViewById(R.id.view_container);
contentView.startReactApplication(reactInstanceManager, "MyComponent", null)
container.addView(contentView, -1, new LinearLayout.LayoutParams(MATCH_PARENT, WRAP_CONTENT));

With the above setup, my reactview never gets rendered, since the height is always 0.
I have to explicitly provide the height to my layout as -

container.addView(contentView, -1, new LinearLayout.LayoutParams(MATCH_PARENT, 200));

How does ReactRootView handles the layout params when embedded inside a android native app ?

@hslls
Copy link

hslls commented Apr 13, 2017

I encountered the same problem.

@hramos hramos added the Icebox label Jul 25, 2017
@hramos
Copy link
Contributor

hramos commented Jul 25, 2017

Hi there! This issue is being closed because it has been inactive for a while. Maybe the issue has been fixed in a recent release, or perhaps it is not affecting a lot of people. Either way, we're automatically closing issues after a period of inactivity. Please do not take it personally!

If you think this issue should definitely remain open, please let us know. The following information is helpful when it comes to determining if the issue should be re-opened:

  • Does the issue still reproduce on the latest release candidate? Post a comment with the version you tested.
  • If so, is there any information missing from the bug report? Post a comment with all the information required by the issue template.
  • Is there a pull request that addresses this issue? Post a comment with the PR number so we can follow up.

If you would like to work on a patch to fix the issue, contributions are very welcome! Read through the contribution guide, and feel free to hop into #react-native if you need help planning your contribution.

@hramos hramos closed this as completed Jul 25, 2017
@githubdoramon
Copy link

@ahetawal-p you just saved my life after a lot of struggle, hahahaha.... I can understand why, but people don't seem to give a f*** for using react-native with existing native apps, which I think is the best use for it. Thanks a lot

@facebook facebook locked as resolved and limited conversation to collaborators Jul 25, 2018
@react-native-bot react-native-bot added the Resolution: Locked This issue was locked by the bot. label Jul 25, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Resolution: Locked This issue was locked by the bot.
Projects
None yet
Development

No branches or pull requests

5 participants