Flash not running debugger any more. Possible socket issue in Windows-10?

Question

Bounty Update

I am leaving the question essentially the same, but I just want to point out at the beginning here that I'm most interested in help trying to get the socket between flash (Adobe Animate) and the native debugger working again, as I believe that is the issue I'm having. Or is it a socket between flash and Windows?

---

Original Question

I've apparently turned something off? Even when I write really bad code (like trying to call a function that isn't there or divide an integer into a fraction), the flash player boots, shows a background color and stops there. No messages in the output window or compiler errors window. If I fix my code, it all runs fine, but for about 30 minutes (ever since I started trying to work with bitmaps for a sprite sheet) I get no runtime errors no matter what kind of mistake I type in my code. Anyone know how to turn it back on?

I've checked my actionscript settings and I have both warning mode and strict mode checked on.

Could it be a socket issue? I admit I have little to no experience working with sockets and only a surface understanding of what that even means. I've added the socket tag. If someone can see that this is clearly nothing to do with sockets, by all means, I'll remove the tag.

UPDATE: 6/22/16

• I just reinstalled Adobe Animate CC 2015.2 and no change. I'll try compiling it in flash builder when I get a chance to help pigeon hole the problem. (Edit 6/24: flash builder worked! But my trial version expired the next day so is no longer a viable option).

• And I just tried something in the command prompt in Windows 10 as an administrator:

  netsh winsock reset catalog
  netsh int ip reset reset.log hit
  

which I found another user on flashdevelop.org used to fix a similar issue, but no change.

• And I just tried debugging in Flash Builder. It worked fine (debugger caught bugs) but my trial version expired the next day.

update 6/24

• I've tried launching debugger for AIR from within the Adobe Animate CC IDE and it works fine if there are no bugs; it fails to do anything visible (no Iphone emulator, no swf window) if I put a typo or error in the code.

• I also just deleted winsock and winsock2, rebooted Windows, then reinstalled winsock and winsock2. No change.

update 6/25

• Just tried a system restore in Windows to set all my files and settings and drivers etc. to the way it was a week and a half ago... Also completely uninstalled all Adobe products and reinstalled. No change. I can only imagine that wiping my hard drive and reinstalling Windows would do the trick, but come on, it hasn't come to that has it?

As VC.One suggested, I checked the compile error window (cannot believe I didn't check before! Maybe when I checked before there were no compile errors... Only runtime errors?) and the errors are showing up there. Does this mean that it's catching compile errors but just not runtime errors?

Answer 1

When you force/test a runtime error... make sure you check

• Compiler Errors (ALT+F2) and also Output (F2).
  By Output I mean the window that shows traces (and runtime issues). One of those two should have some feedback for you.

A possible solution is to save a new Workspace. So with those windows for Compiler Errors and Output both open (or tabbed, I tab them next to my Timeline) go to Window (in top options like File/Edit/Debug etc) and choose Workspace, then into that you choose New Workspace. Give it a name in the pop-up and okay everything.

Flash should always load that current workspace (next time, go to Workspace option again, check that your specified workspace [by name] has a tick next to it...).

Answer 2

Possible pitfalls: 1 - Use the debug player 2 - Make sure there isn't somewhere a try/catch enclosing the portion of code that triggers the event that may lead to an error 3 - Socket issue: may be exported in debug mode but swf cannot connect to debugger (it waits in a blank state for 60 seconds I guess) 4 - Does it compile ok? If there are compilation errors you may get an SWF anyway but then it will not start ...