I too am having this error, now with the latest Flash Catalyst beta (beta 2). I'm on a Mac, running snow Leopard, and no matter what I do or under what circumstances I try, I cannot export an FXPL from my library, which does have custom components in it. To answer Bruce's first question, I do receive a file save dialog - I only receive the error after choosing a filename and location for saving (I've tried in several different locations, but the result is the same in all of them).

-Jeremy

Try this. Select the Flash Catalyst Application in the Finder Applications view. Right click and select Get Info. Under sharing and permissions. Tell me what it says. If admin is read only that could be a problem.

If we can find the path to the project_tmp we can check the permissions on that.

Also check on the folders

[User]/Library/Application Support/Adobe/Flash Catalyst/

[User]/Library/Application Support/Adobe/Flash Catalyst/workspace

[User]/Library/Application Support/Adobe/Flash Catalyst/workspace/project

It's been a while since I knew what that information means.

For now use the Get Info window. It should be:

workspace folder:

system - read & write

staff - read & write

everyone - read

Project folder:

you - read & write

staff - read only

everyone - read only

Also close FC and delete the .fxpTemp file and restart.

I've done two things to try and troubleshoot the issue further to no avail:

- I launched Catalayst as root (I had done that incorrectly earlier).  WHen I did that, I was able to export a library, but the exported file was not importable anywhere, and on top of that, Catalyst could no longer open any fxp file after that.  In other words, never run Catalyst as root.

- I fixed the issue by deleting the entire [User]/Library/Application Support/Adobe/Flash Catalyst/ directory.  After restarting Catalyst, the directory was recreated.  However, I still could not export a library.

That means that the permissions issue resides elsewhere.

Is anyone from Adobe on these forums?  Could you perhaps shed some light on where Catalyst tries to create its temp files during library export?

That's the only thing that I haven't tried yet, but had been trying to avoid doing that, since the Adobe installations seem to be fragile.  My past experience with CS4 has taught me that uninstalling and reinstalling has unintended consequences to other suite applications.  I didn't want to risk fixing Catalyst at the expense of possibly breaking Photoshop.  I will try the reinstallation this weekend.

Thanks again for all your help and advice, thx1138!

Thanks kindly for replying Tara!

I'm afraid that I've already tried deleting the folder (actually, the workspace parent folder), but I tried deleting the workspace folder again exactly as you instructed (after quitting Catalyst).  Unfortunately, the library export problem persists.

Logs are posted below.

!SESSION 2010-07-01 16:05:11.744 -----------------------------------------------

eclipse.buildId=unknown

java.version=1.6.0_20

java.vendor=Apple Inc.

BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US

Framework arguments:  -keyring /Users/gizmometer/.eclipse_keyring -showlocation

Command-line arguments:  -os macosx -ws carbon -arch x86 -clean -keyring /Users/gizmometer/.eclipse_keyring -consoleLog -showlocation

!ENTRY com.adobe.thermo.core 1 0 2010-07-01 16:05:25.497

!MESSAGE Loading ThermoPanels from bundleentry://52/ThermoPanelsSWF/ThermoPanels.swf

!ENTRY org.eclipse.core.net 1 0 2010-07-01 16:05:34.619

!MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences

!ENTRY org.eclipse.equinox.p2.ui.sdk 2 0 2010-07-01 16:05:34.709

!MESSAGE Could not locate the running profile instance

I am having the same problem. Plus this is happening on my Mac at home, and on my Windows XP box at work. I've tried all the mentioned fixes here (except for a re-install) at Home.

I'm seeing no entries in the logs when this error occurs.

Some more details.

On my windows machine (Windows XP, in a highly controlled corp env). I go to export a library item and:

And then on my Mac (OS X 10.6.4, in a home / non-administered env ) -- using a different file (nothing is the same between these 2 machines)

Admin rights makes no difference.  I have admin rights and nothing has fixed it.  In fact, running Catalyst as root only made the situation worse, but making it impossible to load any other FXP after that.  I had to roll-back from time-machine.

I have still not been able to remedy this "marked as read-only" problem, and from the looks of this thread, the problem is spreading.

I can not post steps to reproduce, because the problem seems to be systematic.  After installing Panini, the same problem exists in Panini.

Could someone tell me where the filename_tmp directory gets created?  I can't find it in order to try to modify the folder permissions.

The folder the error mentions is:

~/Library/Application Support/Adobe/Flash Catalyst Panini Preview/workspace/.metadata/.plugins/org.eclipse.core.resources/filen ame_tmp

I can confirm that all of those parent directories are ones that my user account has write privileges.

Is there a way of getting more detailed error messages during export?

Has anyone found the solution to this error???  If so, will you please post the link to the fix, or

describe the fix here?  Thanks.

I think this issue is related to an os x update as I can export my catalyst project as .fxpl using a macbook running os x 10.7.7, I just opened up the same Catalyst project on a iMac running os x 10.6.8 and this 'Parent of resource...' dialogue pops up. The version of Catalyst I have is 1.0.0.273393.

apple and adobe should just learn to get along...

I'm still getting this issue (in OSX Lion and FC 5.5). This problem has existed for 2 years and there still isn't a fix? What's the point of having an export button if it doesn't work?

I have admin rights and none of the suggested workarounds work. Problem exists on any variety of projects (brand-new, created in FB, exisiting older FC, etc).

My error message is slightly different from original post:

"org.eclipse.core.runtime.CoreException: Parent of resource: /(filename)_tmp is marked as read-only."

I had high hopes you were posting a solution

This is really getting frustrating. I have to constantly recreate components because I can't export the library for reuse.

Adobe, are you reading these posts?

It sure does look like a permissions problem.

On Windows XP Catalyst is trying to write to a file called '<something>_tmp' in the root directory of the C drive. I don't have permission to write to that directory and never will at work.

But on the mac it's the same location, but since that is my personal machine, I do have write access to the root level of the system disk.(yet I have errors thee as well - but only on one of my 2 Macs)

If this is an eclipse issue, I would assume it doesn't have a path set for a temp directory. I've looked through a large number of the Catalyst config XML files and have not seen where one might set this. Where are the eclipse config files stored? I assume it's different than the standalone eclipse app, since I have that at work as well and don't have any issues this it.

So, I've just tested a workaround with one of our developers. It's a little annoying but so far so good. If you have Flex Builder installed you can import your Catalyst File and then export it as a Flash Catalyst library. I was able to export a custom library button from Builder (that was part of the catalyst file) and reimport into a new Catalyst file and it works. There are some issues that you'll have to resolve with dependencies (mainly when you have components embedded inside of components) but for me, I would most like just be picking and choosing which components I want instead of the whole thing (this requires creating a new library in Builder and then copying/pasting from the Catalyst file into it). This might prove more flexible in the short term, but at least I have something that works.

Let's see (I'm not a Builder expert by any stretch), here's what I did:

1. Open Catalyst file in Flash Builder

2. New Flex Builder Library. Give it a name. Make sure "Make project Flash Catalyst compatible" is checked.

3. Expand Components in your Catalyst file, find what you want to export.

4. Select and Copy them (I just did a ctrl-C)

5. Paste into the Components Library (in the src library) in your new Flex Builder Library project

6. Under Projects menu, select Flash Catalyst>Export Flash Catalyst Project and I checked both Validation options. Click Finish. *Cross fingers*

7. In Catalyst, assuming you got this far, use the Import>Library Package

This looked to work pretty accuratly for me. However, I have not tested the button or anything nor am I aware yet of the shortcomings of this method. One thing to help troubleshooting on the Builder side, when you nest components (especially the generic ones) it creates dependencies so you have to copy and paste all those other components to get it to export correctly. If you're looking to do as simple 1:1 export of Catalyst>Builder>Catalyst it should work just fine with very little tweaking. The one thing I do like about this is that in theory I should be able to filter out which components I don't want for a new project. I would love to do all this within Catalyst, but if this works as I hope, this will ok for now (which is far better than the NOTHING I had before ).

Hope this helps!

That helped! And yes, this is an actual bug. Adobe should know.

Thanks!

Well if you haven't heard, Adobe is discontinuing Catalyst so I'm confident in saying they'll never fix it.

http://www.itwriting.com/blog/5240-adobe-discontinues-flash-catalyst-c larifies-flex-and-flash-builder-futures.html

There are a couple of solutions above that are workarounds; I preferred the Flash Builder route myself (because of the extra flexibility).

Good Luck.