You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The apk I am trying to analyze uses non-standard port for its communication with the server (e.g. 5678).
After reflutter-ing and signing the apk, the app now uses port 8083 for its communication to the gateway with Burp invisible proxy running.
However, this makes the modified app communication fails. I don't know if this issue is specific to reFlutter or it's the Burp proxy that I need to modify in order to analyze the app requests and communications (feel free to close this issue if it's unrelated, but any pointer and insights will be much appreciated)
The text was updated successfully, but these errors were encountered:
@jayluxferro , I think we should abandon the socket.cc patch
And let the user intercept traffic using TunProxy (Android) or Potatso (iOS). The previous engines take too long to recompile (and don't need to), but the new versions will compile as they should.
The apk I am trying to analyze uses non-standard port for its communication with the server (e.g. 5678).
After reflutter-ing and signing the apk, the app now uses port 8083 for its communication to the gateway with Burp invisible proxy running.
However, this makes the modified app communication fails. I don't know if this issue is specific to reFlutter or it's the Burp proxy that I need to modify in order to analyze the app requests and communications (feel free to close this issue if it's unrelated, but any pointer and insights will be much appreciated)
The text was updated successfully, but these errors were encountered: