Usync 12.2.1 not syncing (stopped with import)
s
Hi, I was wondering if anyone encountered the following issue: We use Usync 12.2.1 on a Umbraco 12.3.1 installation which worked great for a long time. Now, suddenly, when we try to import the data in our staging enviroment, it starts running, but stops when it gets to datatypes and/or document types. then I get spinning buttons. Anyone has any idea on how to fix this?
k
Hi, what types of changes are being reported if you run report ? there is a small fix for renames in v12.2.2 but i am not sure it will do anything else
Also what is the last message - under the progress bar ?
s
The languages and dictionary are imported correctly whenever it gets to datatypes, it get stuck, or in this instance, it gets stuck on templates It goes very quickly from "calculating import order" to done and then I get spinners on the buttons https://cdn.discordapp.com/attachments/1193885582833750066/1194180125667889232/image.png?ex=65af69e8&is=659cf4e8&hm=ee73d251be6faf51769158ed6869893e535765e97b470f7c422788278c927115& https://cdn.discordapp.com/attachments/1193885582833750066/1194180125902786590/image.png?ex=65af69e8&is=659cf4e8&hm=ad3b11995d72d6b497b7660c8237724aeb8404ed8645aa35e3ac697b4bdbd555&
a
Any console errors when that happens?
s
TypeError: Cannot set properties of undefined (setting 'state') at usync.controller.js:296:1 at umbraco-backoffice-js.js.v638403854000000000:159:454 at m.$digest (umbraco-backoffice-js.js.v638403854000000000:171:67) at m.$apply (umbraco-backoffice-js.js.v638403854000000000:174:484) at k (umbraco-backoffice-js.js.v638403854000000000:125:445) at v (umbraco-backoffice-js.js.v638403854000000000:131:40) at y.onload (umbraco-backoffice-js.js.v638403854000000000:131:464) 'Possibly unhandled rejection: {}'
k
that looks like we are doing something wrong showing the error 🤦 - is there an error in the network tab of the browser tools (there should be a red one)- that should have what the error actually is underneath
fix for the js error - here https://github.com/KevinJump/uSync/issues/575 if we can get to what your error is (in the browser console, or after installing the nightly build) we could fix that too before doing a full release.
s
{ "ExceptionMessage": "An item with the same key has already been added. Key: 93a62ad1-4621-44cc-8f91-44b80076532a", "ExceptionType": null, "StackTrace": null } so basicly something is duplicate. Is there any way that I can pinpoint this/change it?
k
i would search the files to see if you can find that GUID value in any of them
if its a doctype or datatype and two have the same ID, then either you need to delete one of the files - or if you think its not a duplicate but somehow they are shared, give one of them a new ID. (but that id might be referenced in a number of places, so you would need to check)
its more likely you have a duplicate file for the same datatype/doctype because it didn't get fully removed in source control or a file copy or something
s
ok, thanks for the explanarion, I will look into it this afternoon and will give some feedback later
k
ok. 👍 - then we will see if there is anything we can do to tidy it up make it easier we will look at that
s
I looked into the issue and it was a rename... updating to the latest usync version gave a good error so no worries there.
77 Views