# Component is invisible after app returns to active state from background state

**URL:** <https://discourse.threejs.org/t/component-is-invisible-after-app-returns-to-active-state-from-background-state/84018>\
**Category:** Questions\
**Tags:** react-native, react-three-fiber\
**Created:** [June 14, 2025, 12:59pm UTC](https://discourse.threejs.org/t/component-is-invisible-after-app-returns-to-active-state-from-background-state/84018 "2025-06-14T12:59:51Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jbd44](https://avatars.discourse-cdn.com/v4/letter/j/7bcc69/32.png) [@jbd44](https://discourse.threejs.org/u/jbd44)\
**Post date:** [June 14, 2025, 12:59pm UTC](https://discourse.threejs.org/t/component-is-invisible-after-app-returns-to-active-state-from-background-state/84018/1 "2025-06-14T12:59:51Z")

</div>

I have a simple React Three Fiber component in my React Native app. It works how I want it too. There is one problem, when the app is sent to the background and then returned to an active state the component becomes invisible:

I can see it, just for a few milliseconds, when the app returns to an active state from the background, but it then disappears. I can see that `useFrame()` starts returning frames when the app becomes active again (seen as an incrementing count, x, and y values in my test), so it looks like some parts are still working behind the scenes, but nothing is visible.

Has anyone experienced a similar issue?