I’m struggling with the Forge black box. How to inspect a forge deployed app / forge tunnel?
For example I have this problem right now:
- I launch ‘forge tunnel’ with my Forge app, that also has a Connect backend.
- Talking to the Connect backend fails:
- It returns a 404: It seems to talk to the wrong place.
- So, How do I trace/debug something lik that. I want to know:
- What URL was actually used? What was the request it built up.
- What config did it actually load?
At the moment I feel like the ‘manifest’ and the actual app are in a inconsistant state and I need a way to debug that.
Update:
Probably issue I had (guessing): I updated a remote URL. That seems requires a re-installation/upgrade. Forge deploy/tunnel will be stuck to the old URL until then.
Generally, the question stands as is. Any hints on how debug forge would help.
Yes, I can attach a debugger, but that often does not help.
For example, the invokeRemote in tunnel forge talks to yet another proxy via https://forge-outbound-proxy.services.atlassian.com/frc/remote/connect. But I want to see the ‘final’ request it built up to my backend. That I cannot see with a regular debugger. I want some kind of forge inspector, for all the network traffic.