Cannot determine files available to pull Log in to development environment

[TheMixDevOps]

I start seeing this after our sandbox updated to a winter 23 preview. Re-login does not help and the message stays the same. Any ideas how to fix that?

[geomuck]

~Thanks for letting us know @TheMixDevOps! Could you please reply with the organization ID where the DevOps Center is installed?~

Actually we've determine that the issue was caused by the rollout of Enhanced Domains.

We'll have a documented workaround shortly. Thanks for your patience!

[kfidelak94]

@TheMixDevOps Here's a description of the issue and associated workaround: https://trailhead.salesforce.com/trailblazer-community/feed/0D54S00000J8Q5vSAF

[TheMixDevOps]

Thank you for the guide. The message now disappeared but this fix only worked for one of the pipelines. Other two pipelines we have are blocked. For those two, when I created new work item and opened it, I was asked "How would you like to work?" so I selected "I want to develop and commit my changes to the work item feature branch from DevOps Center using a connected development environment." and then the screen stayed the same without any confirmation. When I waited a while and then tried to access the work item this red message shows "You don't have permission to view this data, enter credentials for the named credential in your personal settings. Or ask your Salesforce admin for help. Please reload the page or contact your system administrator if the problem persists."

[TheMixDevOps]

Just tried to promote the work item in the first pipeline that I thought was working but got a message "You don't have permission to view this data, enter credentials for the named credential in your personal settings. Or ask your Salesforce admin for help. Please reload the page or contact your system administrator if the problem persists."

[docedemo]

@TheMixDevOps For the second/third pipelines, did you go through the same steps to change the URL in the Named Credentials? The Named Credential records are project-specific so you will need to do that for each project/pipeline.

[TheMixDevOps]

I noticed step "Deselect the “Start Authentication Flow on Save” checkbox" was not followed. I was actually selecting it. Even this time I was following the steps correctly for each pipeline, it did not help. Maybe because I did it first time incorrectly? What to do now

[kfidelak94]

That checkbox should not impact this negatively. Deselecting it just makes it so that you don't have to log in an additional time. I haven't been able to reproduce what you're seeing with some projects that I have. So we're going to need to dig in a bit more. We'll get back to you shortly.

[TheMixDevOps]

It's installed in the production with organisation ID 00D58000000b3T1.

---

From: George Murnock @.> Sent: Monday, August 29, 2022 3:13:12 PM To: forcedotcom/devops-center-feedback @.> Cc: Viktor Vrabel @.>; Mention @.> Subject: Re: [forcedotcom/devops-center-feedback] Cannot determine files available to pull Log in to development environment (Issue #210)

EXTERNAL EMAIL

Thanks for letting us know @TheMixDevOpshttps://github.com/TheMixDevOps! Could you please reply with the organization ID where the DevOps Center is installed?

— Reply to this email directly, view it on GitHubhttps://github.com/forcedotcom/devops-center-feedback/issues/210#issuecomment-1230366133, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AUBUCHIGFH5Z5TTYLUZQOJDV3TAPRANCNFSM57ZWZ7BA. You are receiving this because you were mentioned.Message ID: @.***>

YouthNet UK (legal name of The Mix) is a limited company registered in England and Wales. Company registration number: 3031098. Charity registration number 1048995.

[andresrivas-sf]

Hi @TheMixDevOps, when you followed the work around steps, for your Production Org did you put .sandbox.my.salesforce.com in the URL?

I asking it because that is only for sandbox orgs. For Production Orgs the format is MyDomainName.my.salesforce.com like they mention on Enhanced Domains article.

[TheMixDevOps]

yes ".sandbox." only for sandboxes

[andresrivas-sf]

Hi @TheMixDevOps,

Let's focus in one issue at a time, so it will be easier.

Following the workaround steps Karen mentioned, could you please provide screenshots of your NamedCredentials settings? so we can verify that they were correctly updated.

After perform steps 6 and 7, provide a screenshot of the issue, in order to check if it is another different.