It does not, I just tried again. The code above (D232600479) was the only code it gave me. Here's how I got it:

- Enabled Logging in the settings
- (here Zotero expectedly crashed the first time after a few seconds)
- Started the app, started logging by hitting the blue record button
- (here Zotero had its second crash, the one I hoped to record)
- upon starting the app again, it showed a notification that the debug logs had been sent and gave me that code to copy.

D862535330

Hey @Pomulum, can you try on your device that the crashes occur, going to Settings > Privacy & Security > Analytics & Improvements > Analytics Data, search for "Zotero", and export and mails us the files to support@zotero.org, mentioning this thread?
You can reproduce the crash and send the file that corresponds only to the last one, by checking the date in the name.

Thanks so much for taking a look @mvasilak !

The iPad has 21.7 GB of free storage available at the moment, which would seem sufficient, and the crash occurs also after a fresh install (not just of the app, but also on a freshly set up iPad with no other 3rd party apps installed).

Please note that I can use the app flawlessly to sync and (if I manage to download them in time before a crash) read PDFs as long as I prevent the app to connect to the internet and thus prevent a sync (read: put the iPad in Airplane mode). So it seems to me that the deadlock has something to do with finishing up on a sync.

Additionally, I'm having that problem on two different devices. So far I just blamed my formerly dated iOS version, but the iPad is up to date with 17.4, that's why I decided to reach out.

Thanks again!

Hello again @Pomulum, can you please install the iOS beta (https://www.zotero.org/support/beta_builds#zotero_for_ios_beta)?
We have added a new debug feature that might help us pinpoint the cause of the issue.
Go to:
- Settings
- Debug Output Logging
- Full Sync Debugging
- and tap Start Full Sync Debugging

Thank you in advance.

It took a workaround, but here is, I believe, the right Debug ID for Full Sync Debugging: D1152163725.

(By "workaround" I mean: I started the app up with the iPad in Airplane Mode, initiated the Full Sync Debugging Feature, let the iPad connect to the Internet again, waited for it to sync and crash, started it up again normally, and then stopped the debug logging. I hope that way it collected the information you needed. Thanks again!)

Thanks for looking into this so diligently! I'm confirming that there never, alas, is a Report ID popup after these crashes, and that I just sent the analytics file and the screen recording.

Just to give you all the information I have that might be useful for that:

1. This is for 1.0.32 (251), so, the beta version from TestFlight, and that was the only Zotero analytics file available at the moment from Analytics Data.

2. In an act of desparation for which dstillman might rightly chide me, I emptied my Zotero library a week ago and just finished reuploading my data. However, I now know that the crash also occurs when there is no data at all in my account, so that the desktop library is empty, the web library is empty, and the storage information shows 0 MB synced file data---even then the iOS apps on both my devices go dark after 10-15 seconds (you'll see what I mean in the screen recording).

I got a hunch though that it has something to do with my account. I haven't seen any problems in the web library, and given that the crash happens even with a completely empty library it probably has nothing to do with any one particular file, .prop or .pdf or otherwise, but still it does not look at all like this was a common issue. Would it be okay if I created a dummy account to test that, so, to check whether the app crashes also on the same device, but with a different account?

That's the exact summary, @michalrentka. Regarding syncing the empty account, I synced that with a fresh install of the app and logged in with the empty account (after uninstalling the previous Zotero download and shutting the iPad down and leaving it off for a while, I wanted to try it out with a fresh local database).

And I just sent you the temporary password. The account is empty again (and I just checked for the crash, it still occurs at my end); not because I didn't trust you, but because there's quite a lot of items in the library and that way you don't have to wait forever for the syncs to finish while you troubleshoot (for which I'm very grateful). I'll restore from an up-to-date backup later.

Fantastic, thank you so much!

It works perfectly, thanks!

I have to admit I followed along on GitHub while you were fixing it yesterday and today, and I never would have guessed that item deletion limits could cause that kind of problem. You guys obviously are awesome. And I'm really enjoying reading with the app now.