Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Install error Version 1.12 - Requires Streaming API #86

Closed
cropredy opened this issue Nov 11, 2014 · 6 comments
Closed

Install error Version 1.12 - Requires Streaming API #86

cropredy opened this issue Nov 11, 2014 · 6 comments
Labels

Comments

@cropredy
Copy link

When installing Version 1.12 into a sandbox, I got the infamous:

"Your requested install failed. Please try this again.

None of the data or setup information in your salesforce.com organization should have been affected by this error.

If this error persists, contact salesforce.com Support through your normal channels and reference number: 604940119-57161 (929381962)"

After contacting SFDC support, Tier3 identified an exception being thrown on SObject PushTopic which is only available when Permission: "Streaming Api" is enabled. After enabling Streaming API, I was able to install the package. Note that enabling Streaming API requires a call to SFDC Support.

Suggestion: If possible, detect absence of this permission and warn user before the install proceeds with the otherwise user un-diagnosable error as shown above.

Not sure if V1.13 is affected by this issue

@cropredy cropredy changed the title Install error =- Version 1.12 - Requires Streaming API Install error Version 1.12 - Requires Streaming API Nov 11, 2014
@afawcett
Copy link
Collaborator

Sigh, these sort of errors are so frustrating, thanks for reporting it and providing the error codes, i collect them and send them over to Salesforce as evidence they need to improve error handling in this area. I am not able to detect requirements need by the Permisison Sets i package sadly.

However i did for v1.13 work hard to clean out from the .permissionset files all unwanted permissions. I've just checked again and see no reference in the files to Streaming API, so it must be something getting add in the packaging org or packaging process... 👎

So there is nothing much i feel i can do about these errors, apart from feedback to Salesforce. I will keep this issue open though, as i do want to try to replicate this error (seems straight forward in this case) and also double check in the packaging org itself to see if the deployed permission sets from this repo got magically modified in some way.

Again, thanks for reporting, really appreciate it!

@afawcett afawcett added the bug label Nov 12, 2014
@cropredy
Copy link
Author

I'll try and install V1.13 into a different org that I know does not have streaming API permission and see what happens

@cropredy
Copy link
Author

Unfortunately, a 1.13 install into an org w/o Streaming API Permission fails with error 1914396212-9875 (-2106309647).

I note in the SFDC Help doc on Setup | Customize | User Settings:

"Enables Streaming API, which allows you to receive notifications for changes to data that match a SOQL query that you define, in a secure and scalable way. This field is selected by default. If you don’t see this checkbox, first verify that your Salesforce edition has API access. If your Salesforce edition has API access and you don’t see the checkbox, contact Salesforce."

Thus, you might not have seen this before as other orgs may have had Streaming API enabled by default; something about our org (created in 2012) never got the permission enabled.

@afawcett
Copy link
Collaborator

Ah very interested, thanks for sharing this observation, much appreciated!

@afawcett
Copy link
Collaborator

afawcett commented Dec 5, 2014

Ok i've found that the Permission Set definitions in my packaging org for this tool have some additional system permissions set that the tool does not need. Despite my clearing them out in a previous release from the .permissionset files in the repo and deploying them it didn't clear them. So I'll sort this manually and hopefully this will clear up install issues like this for good! Also see issue 33, for same problem with Idea object.

@afawcett
Copy link
Collaborator

Fixed in v1.15

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants