Hopefully this is what you are looking for…
wappler.zip (1.7 KB)
Are you sure you did exactly this:
- Restarted Wappler in debug mode
- Recreated the issue
- Closed Wappler and attached the debug log here?
i.e. is this debug log generated immediately after recreating the problem, as i don’t see much inside it.
Hi Teodor, I was clicking on ‘Submit Error Report…’ which gave me this dialog
So I clicked ‘Yes’ and sent you the log file. It would seem that it wasn’t restarting with logging so I used the tray icon and clicked ‘Restart with logging’.
Here is the new log file from today.
wappler.zip (2.6 KB)
Please confirm if this is OK as Wappler crashed when I tried to close the API after recreating the problem.
It took a number of attempts to recreate the issue when restarted with logging. After I did what you asked, I restarted Wappler in ‘normal’ mode and recreated the issue straight away.
Hi @Teodor, I was wondering if the error report was OK and were you able to reproduce this issue?
bump - did @UKRiggers give you enough info to deal with this?
Hi @Teodor and @George,
did anything come of your investigations into this issue. I continue to get this problem.
Again, pressing Ctrl-S to save and the API gets cleared or partially cleared.
Are you getting this on the latest Wappler 6 RC 1?
No, I am still on 5.8.2
You can install and run Wappler 6 rc1 as a separate app and test.