Skip to main content
cameronmcefee
cameronmcefee
Inspiring
January 11, 2013
Question

PlugPlugRequestFailed when using retrievePreference()

  • January 11, 2013
  • 1 reply
  • 762 views

Hello,

I've recently converted a panel of mine from a Extension Builder project. Since then when I try to retrieve data from Photoshop's storage I get PlugPlugRequestFailed. To see if the way I converted my project may be the cause, I created a fresh project with just the preference code and it still failed. Just to double check the data was still there, I debugged an old version of the panel and it was able to retrieve the data just fine. All of my other SyncRequestResult related code like getHostEnvironment() works fine. What kind of dependencies are there for retrievePreference() that might cause this?

var csxs:CSXSInterface = CSXSInterface.getInstance();

var ggDataResult:Object = csxs.retrievePreference("ggData");

if (SyncRequestResult.COMPLETE == ggDataResult.status && ggDataResult.data) {}

Thanks,

Cameron

This topic has been closed for replies.

1 reply

cameronmcefee
cameronmcefeeAuthor
Inspiring
January 25, 2013

After a few days of digging into this I've made some progress. It's working on my end, and I've narrowed down where the problem exits. Unfortunately I don't actually know what the issue is.  I was able to track it back to being caused by my migration from a normal flex builder project to a Extension Builder project. The culprit exits in the manifest. My original file was using a manifest.xml that was built by reverse engineering the Kuler panel a few years ago when I first built GuideGuide.

When I moved to the Extension Builder project, I trusted it to generate a valid manifest file and tried to port my data as best as I could. The result caused the error mentioned above.  To resolve the issue above I grabbed my old manifest file and replaced its contents for the Extension Builder generated one.

The resulting diff didn't present any obvious changes. The only significant change noted is that the generated version used <DispatchInfo> elements with any Host attribute. My older (working) manifest specified two separate <DispatchInfo>  elements, one with Host="PHXS" and the other with Host="PHSP".  My best guess is that without the host specified, the plugin doesn't know where to connect the PlugPlug request.

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices