OK, after another full day I think I’ve fixed all the bugs. At least for now it seems to be working well in Chrome and Electron…but that’s what I thought last night 😕 So, there’s now fulcro-3.8.0-alpha2, and fulcro-inspect 1.0.1 The instructions haven’t changed. Just need to use those latest releases. The updated tool itself, of course, is in the releases page as before. https://github.com/fulcrologic/fulcro-inspect/releases I don’t have a Win or Linux box to test those electron versions, but I did build them. The Mac DMG works well for me.
I am not seeing the latest inspect tool in the chrome store. However, the chrome release in dev mode works well for me.
I’m having to manually reload the tool’s tab sometimes on app reload, but otherwise it looks solid. I’ve not done the release yet. I want to make sure the latest Fulcro is stable on my biggest production system
That makes sense. I keep an eye for potential issues.
@tony.kay wondering if you are running into this issue - rendering a rad report breaks the inspect tool. In my case manually reloading the tools tab does not fix it.
not seeing RAD reports break it. I’ve run those with it for sure. It is possible you’ve put something non-serializable in params?
inspect should still handle that, but I may have missed something
Interesting. This is the report:
(report/defsc-report DocumentList [this props]
{ro/title "All Documents"
ro/source-attribute :document/all-documents
ro/row-pk document/id
ro/columns [document/id]
ro/run-on-mount? true
ro/route "documents"})
It's a simple id querygrab error messages from the inspect tools’ console
and from console of your app
(right-click on inspect and “inspect” to get Inspect’s console 😄 )
I do see the response in the UI and server logs. 1 sec.. checking the inspect log
you said crash…define crash
Did I say crash? Looks more like it disconnects after reloading the app with a "No app connected." message. The tool connects after reopening the inspect window.
Screen recording:
This seems to only happen when I refresh the app. Hot reload work okay so far. Is this the same issue you encountered?
Yes. If you navigate to a new page completely (e.g. http://google.com) and then hit back it’ll reconnect. But “reload” the page doesn’t disconnect/reconnect. I need to figure out how to detect that
I have an event listener on page unload…but that doesn’t seem to do it
So I restarted the service worker on <chrome://serviceworker-internals/>. Reloading the page 10x works.
how about just a right-click in the Inspect pane and “Reload Frame”?
I’ve not had to touch anything else
Yea I did the "reload frame" thing a couple times as well. However, the tool disconnects after reloading the app.
“a couple of times?” I’ve never had to do that.
If I reload the app page, then sometimes I have to reload the Inspect frame. That’s all
is that also what you are seeing?
I think I just need to make an “apps loaded” message in Chrome to tell the tooling to disconnect/reconnect
that should fix it. I’ll see if I can get to that tonight
That might help. Watching the error logs for more info. Not sure if this will interest you or not:
Console: {"lineNumber":0,"message":"Uncaught (in promise) Error: Could not establish connection. Receiving end does not exist.","message_level":3,"sourceIdentifier":1,"sourceURL":""}
doesn’t really help…not enough other context
hm. having trouble reproducing in dev mode 😕
you are using 4.0.6, right?
(of inspect)
yes
I am around for a bit if you want to pair
oh, ok…just a min