Skeleton hides real content.

[AshishAlagiyac-lab]

I am using react-native-auto-skeleton as a wrapper in my app.

below is my code:

const AutoSkeletonWrapper = ({ isLoading, children }) => {
  return (
    <View>
      <AutoSkeletonView isLoading={isLoading}>
        {children}
      </AutoSkeletonView>
    </View>
  );
};

Please check below screen recording:
https://drive.google.com/file/d/1WWdqjGRQl55KeYVALMTiPunXk9SV2Xk2/view?usp=sharing

After I apply a filter and then remove it, the list data exists but text does not appear.
Only the skeleton background stays visible.
If I restart the app, everything works again.
If I remove this library, the issue disappears.

Problem Behavior:

• When isLoading becomes false, real UI sometimes does NOT show.

What I tested:

• Removing the library → everything works.

Environment:

• React Native: 0.82.1
• Library version: ^0.1.30
• Platform: Android / iOS

Request:

@pioner92 , @techadvisorbe
Please check — the skeleton overlay is not clearing after state changes.
Let me know if there is a recommended fix.

[dhaval-stc]

Facing same issues

[rizwan-shivalli-jmtco]

+1

[pioner92]

@AshishAlagiyac-lab
Hi, this is an interesting case. Could you please share a minimal reproducible example so that I can repeat it and reproduce the bug on my side?

As far as I understand, the bug reproduces when there is dynamic content inside the skeleton. For example, the skeleton is first shown with 10 items, then with 8 (or vice versa), then later with 12, and the items themselves are different.

If you could write a minimal example that demonstrates this content change, even using a simple setTimeout, where this bug becomes visible, that would be very helpful.

[hizbullaharif]

@pioner92 I have this Example.

The name is there but when it loaded some times it got missed

https://drive.google.com/file/d/1QQjpxWN2sWvCfy0d1JaF_T4X6qM8j_FA/view?usp=sharing

[SimpleCreations]

I think the idea behind this library is great, but it needs a lot of polish before it can be actually usable in production.

Currently, when remounting elements inside the skeleton view, the library breaks the entire app, and the issues persist across screens, requiring full app restart. I haven't read the source code, but to me this indicates fundamental architectural issues, because the library is capable of influencing native elements outside <AutoSkeletonView>.