Hey @Alexander_T and @controleng -
@Alexander_T, thanks for the update. Glad to hear the re-review went through! Let me know if we can help out further though 
@controleng, thanks for sending all that info, really appreciated. I checked the public app URL and I’m not seeing an obvious DNS/TLS reachability issue from my end. Given that automated install traffic reached your app but the manual reviewer’s traffic never appeared in your Railway logs, this lines up more with a reviewer-network or URL filtering issue than an embedded app/session issue from what I can tell.
Could you share the most recent rejection timestamp and timezone, plus whether you already have a Partner Support ticket open? With that, I can route the app ID/org/app URL with the right context on our end.
In the meantime, I would say to keep any bot challenges, geo/IP/VPN restrictions, browser integrity checks, or similar protections disabled for the app URL, auth callback, and any review-facing redirect domains. Hope to hear from you soon