BUG: 'Ghost Widgets' in JSON crash app after saving with new version (1.15.0)
I've tested various methods to replicate the issue but have been unsuccessful. I wonder if the problem causing stale widgets has resolved itself. Many of my existing apps with stale widgets were built using custom templates that already contained these stale widgets, causing them to be carried over time. Unfortunately, I no longer have the original apps from which I created those templates to reverse-engineer the process.
I've noticed that some stale widgets are referenced by the actions of other stale widgets, such as a search widget with an action linked to a stale map. Some widgets may have been embedded within another widget or sidebar when removed, like a sidebar containing a map with a widget controller and search widget (child within a parent). However, all my tests to recreate these sequences, such as setting up parent and child widgets, connecting actions, then removing them, have been unsuccessful. I've tried various combinations of adding, removing, embedding, sending to pending, connecting actions, saving, publishing, creating templates, and republishing. I've even experimented with different device sizes, where one size would have the widget in pending and the other not, then deleting them or switching back to auto. Still, no luck.
In older versions, could you remove a widget directly from the pending list via an ellipsis menu? I was wondering if this used to be possible and caused child widgets to remain when the parent was removed?
Additionally, was the message below always present? If not, are these stale widgets legacy items from before the message was added, resulting from some sequence of removing widgets from one device and not another, or switching from custom to auto, causing them not to be properly removed from the code?
There was also a custom print service referencing a stale print widget, which referenced a stale map with stale widget controllers and search widgets also linked to it. Again, I was unable to reproduce any sequence to create these stale widgets in the context of the print service.
It's also challenging to troubleshoot without access to the draft JSON to compare and see if there are any other clues to what is happening.
Could the sequence require a version update in the middle of the process, making it not replicable while in the same version?
Nonetheless, that's the extent of my time for troubleshooting this. Sorry I couldn't help further.
This was happening to me yesterday as well. Blank screen with Load Config Error after I saved our existing ExB app, luckily I didn't touch our Production version! I tried to remove every single widget to eliminate the issue and just have the blank canvas and the error still persisted!
However, it seems to have been quickly fixed by Esri? All the problematic apps are now working for me...
