Hangman Posted March 16, 2023 Posted March 16, 2023 I'm getting a Cannot open package filename.afpackage. Access to packaged resources was denied message when attempting to open a Publisher .afpackage file in 2.1.0.1713. The file opens without issue in 2.0.4. Do we know what might cause this issue? Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
walt.farrell Posted March 16, 2023 Posted March 16, 2023 Where is the .afpackage file located? Have you checked Publisher Beta's Permissions for that location (and for the Images file)? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Hangman Posted March 16, 2023 Author Posted March 16, 2023 Hi Walt, The .afpackage is simply sitting in a folder on my HD, in the folder there is the .afpackage file itself plus two folders, one containing fonts the other containing images/graphics... In Publisher 2.0.4 I simply use File > Open and select the .afpackage file and it opens as expected, in 2.1.0.713 I do the same and get the error message... Would the Beta require any special permissions for the location, it happily opens every other file I've thrown at it... Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
walt.farrell Posted March 16, 2023 Posted March 16, 2023 I don't think it should need anything special with that scenario. Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Hangman Posted March 16, 2023 Author Posted March 16, 2023 That's what I figured... I've just created an .afpackage file in 2.0.4 and it likewise won't open in 2.1.0.1713. I'll log it as a bug... Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
walt.farrell Posted March 16, 2023 Posted March 16, 2023 Can you create a Package in the Beta and open it successfully in the Beta? Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Hangman Posted March 16, 2023 Author Posted March 16, 2023 I can indeed, though interestingly when intitially opening the Publisher file in the Beta, the majority of linked images displayed with a Sandbox status and had to be re-linked... My assumption is once 2.1 is released that there will be users wanting to open .afpackage files created in V2.0.4 in V2.1... Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
walt.farrell Posted March 16, 2023 Posted March 16, 2023 I wonder if it could be related to something like this: But I'll also remind you of an earlier post you made: Quote -- Walt Designer, Photo, and Publisher V1 and V2 at latest retail and beta releases PC: Desktop: Windows 11 Pro 23H2, 64GB memory, AMD Ryzen 9 5900 12-Core @ 3.00 GHz, NVIDIA GeForce RTX 3090 Laptop: Windows 11 Pro 23H2, 32GB memory, Intel Core i7-10750H @ 2.60GHz, Intel UHD Graphics Comet Lake GT2 and NVIDIA GeForce RTX 3070 Laptop GPU. Laptop 2: Windows 11 Pro 24H2, 16GB memory, Snapdragon(R) X Elite - X1E80100 - Qualcomm(R) Oryon(TM) 12 Core CPU 4.01 GHz, Qualcomm(R) Adreno(TM) X1-85 GPU iPad: iPad Pro M1, 12.9": iPadOS 18.3.1, Apple Pencil 2, Magic Keyboard Mac: 2023 M2 MacBook Air 15", 16GB memory, macOS Sequoia 15.0.1
Hangman Posted March 16, 2023 Author Posted March 16, 2023 34 minutes ago, walt.farrell said: I wonder if it could be related to something like this: Well the symptoms are certainly similar but doesn't sandboxing only apply to app store versions of the apps or have I misunderstood how it applies here... There are also no sandboxing references in the Console... Deleting the original .afpackage file created in the beta and remaking it seemed to work as expected as in all linked files were correctly recognised... 46 minutes ago, walt.farrell said: But I'll also remind you of an earlier post you made: I think that post was more to do with Publisher only opening every other file though the reference to the sandbox error did replicate what I intitally saw when opening the .afpackage created in the beta for the first time which I can no longer replicate... the first file in the resource manager list is shown as ok, the rest with the sandbox error despite all being located in the same folder so I'm unsure what that means in practice... I'm wondering if this is in any way related to the mru.dat corruption issue on mac as I'm seeing a lot of Publisher crashes which are simply resolved by deleting the mru.dat file. Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
MikeTO Posted March 16, 2023 Posted March 16, 2023 The mru.dat problems on macOS are fixed in 1730. I saved one of my bad ones for testing with this version and all is well now. Quote Download a free PDF manual for Affinity Publisher 2.6 Download a quick reference chart for Affinity's Special Characters Affinity 2.6 for macOS Sequoia 15.3, MacBook Pro (M4 Pro) and iPad Air (M2)
Hangman Posted March 16, 2023 Author Posted March 16, 2023 Here is a short screen recording showing a new 2.0.4 Publisher file simply created by opening a PDF. I've then saved the Publisher document as an .afpackage file, closed it and then attempted to open the .afpackage file using the 2.1.0.1730 beta... This happens for me with any document created in 2.0.4 when attempting to open the .afpackage file in the current beta's... could it be OS version specific perhaps? Relevant files are attached... Package.mp4 Package.zip Zwartboek Downsyndroom.pdf Quote Affinity Designer 2.6.0 | Affinity Photo 2.6.0 | Affinity Publisher 2.6.0 MacBook Pro M3 Max, 36 GB Unified Memory, macOS Sonoma 14.6.1, Magic Mouse HP ENVY x360, 8 GB RAM, AMD Ryzen 5 2500U, Windows 10 Home, Logitech Mouse
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.