When updating the main component, the instance of it resets to something different

Sounds simple. But have you ever cleared your cache in Figma?

I would start there and see if it helps.

Make sure you shut Figma down completely before running the script.

What happens if you right click in the instance and choose “go to component”?

Does it find the component or does it go to your library but not find the component?

When I right click the instance and go to the main component, it goes to the library to the exact main component. which is how it should look. but the instance looks different. which is why im so CONFUSED.

Yup. That screams cached data.

Try clearing the chache.

i just cleared the cache, its doing the same thing it didn’t get fixed. here is a video pls help 😭 😭 😭 😭 😭 😭

the version the instance is reverting to is definitely an older version of the component. its missing some of the newer properties i set up in the main component. 😭

That is really confusing and not very clear as to how you are using the instance or the component. From the video it looks like you are copying and pasting the component. ??? Not that you are dragging in an instance in the assets.

We cannot see the left sidebar to tell what is a component and what is an instance. It is also rather odd to see the component acting like that. We need the whole screen and more than the fast clip like that to be able to help.

If you can share the file we can check it out. That is going to be the only way.

the file is from work so it’s confidential but I will see if I can get permission to share. side question; is there a difference between copy pasting and dragging the instance from asset library? if i copy paste, the component shows like this meaning it’s an instance if I’m not mistaken.

That should be correct, yes.

Sometimes if you copy a component and paste it to a different file, it actually pastes as a component, not as an instance. But your shows as an instance, yes.

Thanks for sharing that.

This is the part of your post that causes us some confusion.

“and then update the library in a different file that has this same component, it resets to an old version of the component”

It says component. A lot.

So which file really has the component?

Is the source library the home of the component?

Then there should not be a “same component” in a different file.

I might suggest a test where you create a file, set the library sources in assets, and the DRAG THE INSTANCE FROM THE ASSETS SIDEBAR.

Sorry for the all caps there.

But try it this way and not with copy paste.

Try it in your existing file.

Then try it in a totally new file.

See if you get different results.

sorry in that phrase, I meant component instance. the main component lives in a separate UI Kit file where all our main components live.

what’s happening is that whenever I publish updates to the main component and then update the library in the external file, the instance auto updates to an old version of the component. but the weird part it it doesn’t affect all of the instances of the same component in the file

Yeah that really just doesn’t make sense. Stinks.

Sharing the file likely won’t help unless we can see the library too. 😕

To get someone to get in to help you, you might have to share and grant access to the file.

Sorry there is not any other way to assess it further otherwise.

Wait.

So it is just the ONE instance that is giving you issues?

Delete it. Add it again.

no, its a random amount of instances, maybe like 10-15, and then some are unaffected. even if i delete the instance, and copy paste again from the library, it still happens to the new instance. There must be something I messed up with the main component for it to act like this, but can’t figure out what. I’ll get back when I can get permission to share both the files.

That is just crazy.

It is so much harder when there is just no reason.

❤️

Last two ideas…

First, after you publish, when you go into the prototype file and you update the assets, is it possible that you are not selecting “update on all pages?” I know in UI3 I hate where they moved that and I forget the toggle is down there now.

Second…

Understanding that it is a pain in the rear to just keep trying random stuff…

Every once in a while, one of my robust component instances will freak out in the prototype file.

For example, in yours, the caret icon is not updating correctly.

I have no real evidence that this works or might help…but sometimes I go into just ONE of the instances and drill into that caret icon and do a reset on the icon. In the instance.

Then magically the rest of the wonky instances fix themselves like they are like “oh, you mean us too?”

It is like the update just doesn’t get communicated to them when you run it.

However, I have also had it where I have had to find each of the wonky instances and do that reset the offending bits and pieces on each one.

Might not be much help…but you are not alone with these types of things.

The more I read this comment you might be right about the main component having issues.

But what? That almost makes no sense too. 🤬

Have you tried making a completely NEW FILE and connecting the asset library in the new file. Then make some instances on different pages in the new file.

Do they work properly? Update properly?

I also still think the copy/paste from the library is where your problem lies. That is just not how assets are used. The asset tab and dragging them in to the file is how connections are maintained.

no, its a random amount of instances, maybe like 10-15, and then some are unaffected. even if i delete the instance, and copy paste again from the library, it still happens to the new instance. There must be something I messed up with the main component for it to act like this, but can’t figure out what. I’ll get back when I can get permission to share both the files.

Thanks for providing solution. It help me a lot.