Affinity Publisher Customer Beta - 1.8.0.535 Crashing

[Johann Seidel]

Download and installation worked correctly, but when I launch version 1.8.0.535 the load screen appears awhile and then just close down. I have the same problem with Affinity Photo as well as Affinity Designer. See the info from the Event Viewer Console:

Quote

 

Application: Publisher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.Runtime.InteropServices.SEHException
   at <Module>.Affinity.TextBaseTarget.GetFontStyles(Kernel.Font*, Story.FontResolution, std.vector<Kernel::Font,std::allocator<Kernel::Font> >*, UInt64*)
   at Serif.Interop.Persona.UserInterface.FontFamilyComboBoxContextBarItem.BuildFontsList()
   at Serif.Interop.Persona.UserInterface.FontFamilyComboBoxContextBarItem..ctor()
   at Serif.Interop.Persona.Data.CharacterDataSource..ctor(Serif.Interop.Persona.Services.IServiceProvider)
   at Serif.Affinity.UI.Studio.CharacterPage..ctor()

Exception Info: System.Reflection.TargetInvocationException
   at System.RuntimeTypeHandle.CreateInstance(System.RuntimeType, Boolean, Boolean, Boolean ByRef, System.RuntimeMethodHandleInternal ByRef, Boolean ByRef)
   at System.RuntimeType.CreateInstanceSlow(Boolean, Boolean, Boolean, System.Threading.StackCrawlMark ByRef)
   at System.Activator.CreateInstance(System.Type, Boolean)
   at System.Activator.CreateInstance(System.Type)
   at Serif.Affinity.Services.PageService.EnsurePage(System.Type)
   at Serif.Affinity.UI.AffinityWindow.AttachPages(Serif.Interop.Persona.Workspaces.IWorkspace, Boolean)
   at Serif.Affinity.UI.AffinityWindow.set_CurrentWorkspace(Serif.Interop.Persona.Workspaces.IWorkspace)
   at Serif.Affinity.Services.WindowService.ShowMainWindow()
   at Serif.Affinity.Application+<>c__DisplayClass53_0.<OnServicesInitialised>b__2()
   at System.Windows.Threading.DispatcherOperation.InvokeDelegateCore()
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task)
   at System.Windows.Threading.DispatcherOperation.Wait(System.TimeSpan)
   at System.Windows.Threading.Dispatcher.InvokeImpl(System.Windows.Threading.DispatcherOperation, System.Threading.CancellationToken, System.TimeSpan)
   at System.Windows.Threading.Dispatcher.Invoke(System.Action, System.Windows.Threading.DispatcherPriority, System.Threading.CancellationToken, System.TimeSpan)
   at System.Windows.Threading.Dispatcher.Invoke(System.Action)
   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 System.Threading.ThreadHelper.ThreadStart()

 

 

[Patrick Connor]

Sorry.

Thank you for reporting a problem using the pre 1.8.0 beta builds. It appears that a member of the Affinity QA team didn't get round to fully investigating this specific report posted in the bugs forums. We are very sorry for this oversight. Yours is one of a number of reports that I am posting this apology to, using an automated script. 

Now we have released 1.8.3 on all platforms containing many hundreds of bug fixes, and we hope your problem has already been fully addressed. If you still have this problem in the 1.8.3 release build, then the QA team would really appreciate you reporting again it in the relevant Bugs forum.

• Report a Bug in Affinity Designer
• Report a Bug in Affinity Photo
• Report a Bug in Affinity Publisher

Each of those links above contains instructions how best to report a bug to us. If that is what you already did in this thread just copy paste your original report into a new thread. We appreciate all the information that you have including sample files and screen shots to help us replicate your problem.

This thread has now been locked as the QA team are not following the threads to which this automatic reply is made, which is why we would appreciate a new bug report if you are still have this problem in the release build.