Publisher crashes…

[Inlancewetrust]

Publisher iOS is now crashing so frequently it is unusable. Whether it’s a new doc, an old one, nothing else running, whatever. Again, brand new iPad Air M3 with 512g and everything installed fresh. Ideas? This is making it impossible to get work done. Attached new crash report. Is anyone seeing this? Thank you…Publisher iPad-2025-04-25-010846.ipsPublisher iPad-2025-04-25-010846.ips

[Joe Gavilan]

I suffer the same situation but do not know, how to generate a crash report.

The list on actions which seem to cause the crash is long an therefore seems irrelevant.

I use V 2.6.2 on an iPad Pro 1 TB, two days old (which i did buy, because I hoped to end this problem.)

[Alfred]

10 minutes ago, Joe Gavilan said:

I suffer the same situation but do not know, how to generate a crash report.

You don’t generate the report, the app does: you merely have to find it.

Go to ‘Settings > Privacy & Security > Analytics & Improvements > Analytics Data’. If you see a *.ips file whose name is something like

Publisher iPad-2025-05-01-214036.ips

(i.e. ‘Publisher iPad’ followed by a timestamp), tap on the ‘Share’ button and choose ‘Save to Files’ to save it to local or Cloud storage, and then attach it here.

[Joe Gavilan]

Thanks @Alfred, now I know how to share crash reports. Sadly this does not help in this case, because there are no reports since April 29th, although Publisher crashed at least ten times yesterday and today.

[Lee D]

@Inlancewetrust & @Joe Gavilan Due to certain restrictions within iPadOS, our ability to suggest in-depth troubleshooting steps for iPad devices is somewhat limited.

However, if you’re able to reproduce the crash consistently by following specific steps, please confirm the steps so we can try replicating the issue on our test iPads. We can then create a report for the development team to investigate it further. The same applies to document-related crashes—any reproducible examples are extremely helpful for testing and resolving the issue.

@Inlancewetrust The crash report you provided points towards a memory access violation. Have you tried doing a restart of your iPad so it clears its cache/memory?

[Joe Gavilan]

Thanks a lot for your inquiry, @Lee D You might help to meet an important deadline. (Is there another kind?)

My crashes are indeed document related. I attach the file here. It was created with Publisher 2 – before the last Update, I believe.

As I said, there are numerous ways to provoke the crash. This is the thing I tried the most desperate:
- when opening, ignore all missing resources
- select a random (missing) picture, e. g. at the bottom of page 8
- jump to the resource manager
- replace the (missing) picture by any other picture from your hard drive
- leave the document towards the main menu of Publisher

Some background information which may or may not be important:
I do not send the linked pictures because the links are broken on my side anyway. This is due to the fact, that I hosted all pictures on iCloud. When the trouble started, I supposed that less than 9 GB free space on my old iPad would be the reason for all those crashes. I bought a new iPad. The iCloud-links stopped working there. I learned that hosting resources in a cloud is not recommended anyway. I copied all resources to the new iPad, since this one has 1 TB. I started to replace the iCloud links with the local pictures, but the crashes from the old iPad continued immediately. To me, the switch to the new iPad seems not to be the reason for the current crashes.

JB-WS_2025_beta.afpub

[Joe Gavilan]

… I can now add a crash report.

Dear @Alfred, I just was not attentive enough to understand, that those reports are *not* arranged by date 😑

Publisher iPad-2025-05-02-162031.ips

[Alfred]

3 hours ago, Joe Gavilan said:

I just was not attentive enough to understand, that those reports are *not* arranged by date

They’re arranged in alphabetical order, so that any ‘Photo iPad’ reports will precede ‘Publisher iPad’ reports. The year-first date format ensures that the reports within each such group will be in chronological order.

[Joe Gavilan]

Here is the workaround: Do not open the faulty document, but import it. I am designing for hours now without any crash.

Regarding those 108 corrupted links: I learned to save a Publisher project as a package on my old iPad. When I did open that on the new iPad, everything was tidy and working. This procedure prevented the constant crashes also.

Working with links to cloud resources seems to have caused all the trouble — in my case.

[Joe Gavilan]

The optimism is gone again. There are still no crashes, but when I continued this morning, all links were corrupted again. What is new: I get no warning about the corruption upon opening the document, unless I try my workaround to close and import the document. This does not work anymore.

Every picture which is linked has now a sandbox error again. Like before, I can not reconnect any of them. Before, I was able to replace them (apparently with the same picture — and then got the crash), but this time this attempt leads to no change. Neither do I get a message with the reason for the missing change. Only the resource manager shows a check now, where there was a dash before.

I can confirm that all resources are where they belong. I can not check if this affects further documents as I do not have an older one with linked resources.

I appreciate your ideas, as I have to rescue this elaborate document. I can not afford to start from scratch (and would have too less confidence to do so).

[Joe Gavilan]

… Replacing now works again 😐 Just have to do this 108 times. What will be next morning is still frightening me, though.

[Inlancewetrust]

Coming back to my original post and crash report, publisher continues to crash constantly, creating a brand new file doesn’t make any difference. Restarting doesn’t make any difference, having other programs open, on the web, WiFi turned off, nothing helps.