I can't open my project - Exception: Error: id already in use

Post reply

❤Follow Topic(5)

0 favourites

6 posts

From the Asset Store

7 Errors

$15 USD

7 Errors is a game where you have to find the 7 mistakes before time runs out. Can you find all 7? Have fun looking.

BassoGames

- relixes
- - Joined 7 May, 2015
  - 29 topics • 90 posts
- 1
- 29 Aug, 2023
- Quote
Hello, first of all I wanted to start saying that this is not a bug.

I'm working on a project and at some point in time I had to use git and work in different branches.

Now that I tried merging both branches and open the project, I get this error:

[Project] Exception opening: Error: id already in use
at va.h2c (projectResources.js:1008:26)

at new g (projectResources.js:31:329)

at d.l (main.js:292:207)

at n.Mta (projectResources.js:193:3)

at n.hja (projectResources.js:202:448)

at async Promise.all (/r225/index 11)

at async Promise.all (/r225/index 0)

at async n.cpd (projectResources.js:134:402)

at async Promise.all (/r225/index 1264)

at async e.mbc (projectResources.js:139:120)

I'm here hoping Ashley, another scirra staff or a experienced user could point out what could be causing this type of error, so I can try finding the problem on the project.

Thanks in advance!
- fredriksthlm
- - Joined 6 Jun, 2016
  - 32 topics • 1,065 posts
- 1
- 30 Aug, 2023
- Quote
Are you working in r225 ??
Try Construct 3

Develop games in your browser. Powerful, performant & highly capable.
Try Now Construct 3 users don't see these ads
- Ashley Construct Team Founder
- Moderator
- - Joined 21 May, 2007
  - 669 topics • 30,331 posts
- 1
- 30 Aug, 2023
- Quote
I can't tell what the problem might be just from that. I'd suggest reversing the changes and retry the merge, and make sure you do it carefully. It's best to avoid merging if you can - if you have two branches where someone does something like add an event variable with the same name, then merging them will result in a bad project. So avoid merging, and if you have to, do it really carefully. And... yeah, if you're still using r225, you should definitely update. It might be related to a bug we already fixed long ago.
- relixes
- - Joined 7 May, 2015
  - 29 topics • 90 posts
- 1
- 30 Aug, 2023
- Quote
We try to be very carefull when merging and when we have issues the console usually outputs a error that helps finding out what exactly is the issue, but this time we got this "Error: id already in use" wich sounds a bit generic.

For the c3 version, yeah, we still use r225. At this point we need to stick with it for multiple project related reasons.
- Jase00
- - Joined 5 Jan, 2012
  - 107 topics • 1,031 posts
- 1
- 30 Aug, 2023
- Quote
Unrelated but purely curious, what project reasons do you stick with r225? Perhaps there's good reason and maybe others might need to consider it, but can't think of a reason off top of my head.

I think one of the recent updates added a UID option that helps with github-related stuff, may be relevant to you.
- relixes
- - Joined 7 May, 2015
  - 29 topics • 90 posts
- 3
- 30 Aug, 2023
- Quote
With the help of skymen we managed to track the issue. It seems the engine generated the same value for different objects imageSpriteId. So looks like we just got unluck for the engine to roll a number that were the same in different branches. IIRC this has been fixed and shouldn't happen in recent c3 versions.

Thanks everyone!

Jase00
Some reasons why we stick with r225:

- We would need to adapt many plugins to work in r226+ version because of a change in how structure for plugin in JS works

- We work on a big project, so updating C3 version would ocasionally create bugs in the project that were hard to track

- It makes life of third party company we work with easier