MantisCore

Yes! The recovered file opens without issue. Thanks for the help!

A document I have been working on on and off for a while is suddenly causing Publisher to crash as soon as it is loaded. Just before crashing I can briefly see a notice about a missing font. I did indeed just uninstall a font that was used in that document, but surely that should not be causing the application to crash? I am not sure what I can do to recover this document. I tried installing an earlier version of Publisher to see if that would help, but no luck. Grateful for any help. I attached the document below. This is the error from the Windows event log if it is of any help: Faulting application name: Publisher.exe, version: 2.3.1.2217, time stamp: 0x65981eb2 Faulting module name: ntdll.dll, version: 10.0.22621.2506, time stamp: 0xbced4b82 Exception code: 0xc0000374 Fault offset: 0x000000000010c7a9 Faulting process id: 0x0x4EC4 Faulting application start time: 0x0x1DA57CCAC6E214B Faulting application path: C:\Program Files\WindowsApps\SerifEuropeLtd.AffinityPublisher2_2.3.1.2217_x64__3cqzy0nppv2rt\App\Publisher.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 24ae31c4-c276-4b19-badb-c21563be1414 Faulting package full name: SerifEuropeLtd.AffinityPublisher2_2.3.1.2217_x64__3cqzy0nppv2rt Faulting package-relative application ID: SerifEuropeLtd.AffinityPublisher2 mecha_clash_rulebook_4.0.afpub

Thanks for the reply @Dan C These particular pages were synced from a different file belonging to the same book (using the Books pane). I tested the other file and that one seems to work fine. If I recall correctly multiple syncs caused duplicates of the master pages pages to appear in this file so I removed the extra ones manually. Could that be the cause of the problem?

Publisher (version 2.1.1) is consistently crashing whenever I try to apply a master to another master page in my document. It works fine in a brand new document and used to work in this one as well so I assume it is something that happened over time. According to the Event Viewer the crash is caused by an AccessViolationException (see below) so I assume there is some memory handling issue at fault here. Document displaying the issue is attached below. Application: Publisher.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.AccessViolationException at <Module>.ApplyMasterPageCommand.CanPlaceMaster(Kernel.Counted<DocumentController const >*, Int32, Int32) at Serif.Interop.Persona.Data.PagesPageDataSource.CouldApplyMaster(Int32, Int32) at Serif.Interop.Persona.Data.ApplyMasterToMasterDataSource.UpdateEnabled() at Serif.Affinity.UI.Studio.Pages.PagesPageViewModel.<PrepareCommands>b__102_16(System.Object) at MS.Internal.Commands.CommandHelpers.CriticalExecuteCommandSource(System.Windows.Input.ICommandSource, Boolean) at System.Windows.Controls.MenuItem.InvokeClickAfterRender(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.DispatcherOperation.InvokeImpl() at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object) at MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, System.Threading.ContextCallback, System.Object) at System.Windows.Threading.DispatcherOperation.Invoke() at System.Windows.Threading.Dispatcher.ProcessQueue() at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef) at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object) at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32) at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate) at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32) at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr) at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef) at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame) at System.Windows.Application.RunDispatcher(System.Object) at System.Windows.Application.RunInternal(System.Windows.Window) at Publisher.Application.Main(System.String[]) test.afpub

Trying to copy any table cells or their contents causes an immediate crash to desktop. Publisher version is 1.7.0.376 (beta).

Thank you No idea why I didn't find that setting on my own.

I just bought both Designer and Photo for iPad and I cannot get pressure with the Apple Pencil to work with either of them. It is constantly on full pressure no matter what i try. Pressure works fine in other apps such as Procreate so I know it is not a hardware issue. I am using an iPad Pro 2017. Is there something I might have missed here? The apps are kind of useless to me unless I can get this sorted.