Oops. An internal error [2a8242865da1fa38f7496c0d347cd45c] has occurred. We are working on it. Please try again later
Oops. An internal error [2a8242865da1fa38f7496c0d347cd45c] has occurred. We are working on it. Please try again later
at https://eu-develop.backendless.com/js/bundle.f0db88e0.js:1:1684949
at Object.loadPageLogic (https://eu-develop.backendless.com/js/common--react.3d9249fa.js:2:547365)
at t.value (https://eu-develop.backendless.com/js/904.6588b64b.js:1:843470)
at e.<anonymous> (https://eu-develop.backendless.com/js/904.6588b64b.js:1:820895)
at f (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:615413)
at Generator.<anonymous> (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:616755)
at Generator.next (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:615842)
at i (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:683630)
at a (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:683833)
at https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:683892
at w (https://eu-develop.backendless.com/js/common--modules-d0246239.306c70dd.js:2:221251)Error
at i.value (https://eu-develop.backendless.com/js/common--modules-d0246239.306c70dd.js:2:223705)
at i.value (https://eu-develop.backendless.com/js/common--modules-d0246239.306c70dd.js:2:224289)
at https://eu-develop.backendless.com/js/bundle.f0db88e0.js:1:1685568
at Object.loadPageLogic (https://eu-develop.backendless.com/js/common--react.3d9249fa.js:2:547365)
at t.value (https://eu-develop.backendless.com/js/904.6588b64b.js:1:843470)
at e.<anonymous> (https://eu-develop.backendless.com/js/904.6588b64b.js:1:820895)
at f (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:615413)
at Generator.<anonymous> (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:616755)
at Generator.next (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:615842)
at i (https://eu-develop.backendless.com/js/1231.aab7fef9.js:2:683630)
Problem description
I tried to open the logic of a button.
I suppose that this might be related to the action where I renamed a API operation called in the logic of this button. I tried to restore earlier versions of the UI but the same error occured also with these versions now. I know that I opened succesfully that logic yesterday.
How can I fix the situation and get the UI Builder to be used again?
Steps to reproduce
Please describe steps to reproduce starting from the first action.
Thank you for reporting this issue, and I apologize for the inconvenience and frustration this crash has caused you.
I have investigated the problem with the MySubscriptionsPage and successfully resolved it. You can now access the UI Builder and edit the logic for the proceedToCheckOut button without any errors.
What Happened
The crash was caused by a data desynchronization between your page file and the component file in the database.
The page data incorrectly indicated that the button had logic attached to it.
However, the actual component file itself was completely empty and contained no logic.
When you clicked the Logic tab, the UI Builder tried to load logic that didn’t actually exist, which resulted in the internal error and crash.
The Fix
To fix this, I manually removed the “phantom” logic reference from the page data to resynchronize the files. Please don’t worry - because the component file itself was already empty, no actual logic or data was deleted or lost during this fix.
At this moment, we aren’t entirely sure what caused this desync to happen in the first place, though your theory about renaming the API operation is a helpful lead. If you happen to encounter this exact behavior again, please reach out to us right away so we can investigate the root cause further.
It might be that I started to do some operation / function there but then I decided to do it other way and didn’t yet clean the first idea from the code… Something like that happened yesterday… Perhaps that was the reason of the problem…
I am sorry, perhaps it is because I forgot to close the MySubscriptionsPage and it overwrote your changes now? Sorry, sorry, sorry… Now I closed this MySubscriptionsPage…
Here is what was happening: when you opened the Logic tab for your button, the server was trying to read a file for the Disabled State Logic handler that did not exist yet on our end, which caused the crash instead of simply showing an empty editor. As a temporary fix, you can remove the Disabled State Logic handler. I have already done this for you, so everything should be working fine now.
I have created an internal ticket to investigate this issue and will make sure to let you know as soon as it is fully resolved on our side.
Sorry for the inconvenience this caused and thank you so much for your patience.
Just to help us narrow down the issue: do you usually work alone in the UI Builder, or is there a chance someone else from your team is making changes simultaneously?
