Problem with latest DE orgs?

[afawcett]

From my blog...

Hi Andy This really very helpful tool, thanks for it. We are using it to deploy report and dashboard for our clients. It work fine with DEV orgs and Sandboxes, but starting this week if we create new DEV org instances and try to use GitHub Salesforce Deploy Tool in Authorization step we get OAuth Error(http://prntscr.com/ljrujg). We compare and check all settings, all looks fine. Could you please help to solve this issue?

[derekdanderson]

Hi Andy, I am also seeing this a lot with SDOs that SEs are spinning up. I can provide you with an org to test with if that would help.

[thedges]

Hey Andy...please find some time to investigate this. It's been a nagging problem now for atleast 3 months or so.

[salahayoubi]

Hey Andy. Have you been able to take a look at the issue? Getting many SEs asking about it. Thanks! :)

[MouDas]

Hi Guys ...there is a workaround. If you just download the code onto your desktop and use the IDE (Eclipse is what I used) to deploy to the org then the component works fine. Here is a link to the doc I put together for the steps I used. https://salesforce.quip.com/tXl3Av5ZPqCF

[MouDas]

FYI @afawcett not sure how the Deploy to Salesforce button works but just wanted to let you know that in the mean time you can let folks know to download the code and deploy through an IDE and it works fine.

[afawcett]

@thedges understood will try to look this weekend... gradually catching up! 👍

[ghost]

We are running into the same issue.

[thedges]

Hey Andy...do you have a managed package that contains your connected app details. Asking as the connected app I see in new orgs doesn't look same as connected app definition in old orgs. I thought I would try to deploy package from scratch in org to see if that helps.

Question...how does the connected app get installed originally as I never go through Setup to create it?

[ghost]

@afawcett any luck? We lean on this heavily and Salesforce Partner Support hasn't been able to identify what the possible cause of the error 1800 might be.

[afawcett]

@jschneider-nexgen looking now folks... sorry about the long delay on getting round to this...standby a little longer.... i'm on it! 👍

[afawcett]

Ok it looks like the org i used to manage the connected app for this tool has been deleted, which is likely causing the issue for new orgs. I'm going to create a new connected app, update the tool and create a package with the connected app in. Which although the package will not be required to be installed will ensure (as a packaging org) that Salesforce's org purge process does not delete it in the future. Once again sorry for the delay on this folks. We will be back in action soon! 👍

[derekdanderson]

@afawcett You are the best!

[afawcett]

Really really sorry for taking so long on this! Should be up and running now! 👍

[thedges]

Thanks Andy. This will help out a lot of people.

On Sat, Feb 23, 2019 at 11:32 AM Andrew Fawcett notifications@github.com wrote:

Ok it looks like the org i used to manage the connected app for this tool has been deleted, which is likely causing the issue for new orgs. I'm going to create a new connected app, update the tool and create a package with the connected app in. Which although the package will not be required to be installed will ensure (as a packaging org) that Salesforce's org purge process does not delete it in the future. Once again sorry for the delay on this folks. We will be back in action soon! 👍

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/afawcett/githubsfdeploy/issues/35#issuecomment-466671601, or mute the thread https://github.com/notifications/unsubscribe-auth/AFrhiUGPol2TFAaWNg26H_445LaGMXTMks5vQXsogaJpZM4ZU40H .

-- Troy Hedges

Solution Engineering | North America Public Sector Mobile: 512-484-5384

http://www.salesforce.com/signature

http://smart.salesforce.com/sig/thedges//pbu_sl/default/link.html