Perforce server URL in the "Source Control Login" restores ":" as "." when prefixed with SSL

Development Pipeline & Plugins
, , ,
1

Hi,

This is a minor bug but a bit annoying. When resetting a project by deleting the Binaries, Intermediate and Saved folder, the perforce Source Control settings are not correctly restored when using an url prefix, “ssl:”. Instead it restores it as “ssl.”. When manually changed to “ssl:” everything is working again but it might take a while before you spot that very minor difference in the url as it is the difference between everything working or not.

Currently when restored or retrieved from p4v: “ssl.subdomain.p4vserver.com:1667”

Expected result when restored or retrieved from p4v: “ssl:subdomain.p4vserver.com:1667”

Steps to reproduce:

  1. Create new project.
  2. Login to the Perforce server with the “Source Control Login” in Unreal. ssl:subdomain.p4vserver.com:1667
  3. Close project
  4. Delete Binaries, Intermediate and Saved to force a restore of the Source Control Settings.
  5. Start Unreal.
  6. Go to the same Source Control Login settings and the url is restored as ssl.subdomain.p4vserver.com:1667.

132962-screenshot_3.png
132962-screenshot_3.png717×290 16.2 KB

2

Hello ,

With the help of another teammember, this was tracked down to this function in Perforce’s API:

https://www.perforce.com/perforce/r15.1/manuals/p4api/chapter.methods.html#clientapi.getport

When I attempted your reproduction, my Server was reset back to Perforce:1666 when I completed step 4 of your reproduction. It seems that your P4PORT may be set incorrectly and is causing this to occur or the Perforce API isn’t parsing it correctly. If the issue is the latter, this is likely an issue on Perforce’s end and not something we can edit. Can you take a look at your P4PORT and ensure that it is set correctly?

3

We haven’t heard from you in a while, . Are you still experiencing this issue? If so, can you attempt what I suggested in my previous comment? In the meantime, I’ll be marking this issue as resolved for tracking purposes.

4

Nope, your answer above fixed it for me.

Thank you very much!