I know this is an old thread, but this helped me verify the error was only on our dev server (with a different domain). So it was great to find this. I noticed another error that I THINK may be related so wanted to post here for verification that it is caused by the domain change.
-change config to new-domain.com
-try to redeploy old form (breaks as expected, no confusion there)
-submission to old form, successful on ver 2.022.08a/b
-try to EDIT a previous submission throws the below error
My assumption is this is caused by this same behavior of domain info getting stored in the metadata. I have NOT run the scripts in this thread as I can explain why the old forms on dev do not work with a temporary domain. But can anyone confirm that the submission edit error would be fixed by the same scripts?
It’s a release branch, not a tag, but after looking at it a little bit more, I don’t think it would help anyway.
Your asumption seems to be true because edits use KPI now which proxies the request to KoBoCAT to save the data in DB. The problem must occur between KPI and KoBoCAT. KPI is just re-raising the error from KoBoCAT to Enketo.
If new forms work OK, chances are really high that you are true.
ah i see the branch now, thanks. On our dev with the new domain, i deploy a brand new form, submit a form, but get the same error trying to edit. I will run these scripts above and try to update here if i find anything
connected our dev VM to new Sentry account and found the error. See previous issue. When we tried to move to 2.021.24b, we found an error and had to roll back to 2.021.24 and manually modify the KPI DB to remove “synced_with_backend” column. This column was still missing and expected from all new versions. Added this back in, synced_kobocat_media was run on KPI, and all is working as expected.