Sorry to say, this did not fix the problem.
I turned on Factory Reset. Rebooted the iPad. Checked that Factory Reset was still on. And then started Panels.
I still only get a black screen.
I understand that further investigation may take time. I’m looking forward to seeing if you are able to come up with a solution.
Could you join our discord.panels.app so we can discuss this in real-time? We got another report of this problem from another user.
If you join, ping me on DM, and I’ll create a channel to shorten the feedback loop and fix this as soon as possible.
Currently, we don’t have any leads
Found the update in the App Store.
Rebooted my iPad.
Sorry to say, it did not fix the problem.
I do very much appreciate your attention to this issue. Thanks.
(Factory Reset is still set to on/green)
The App store showed an update.
I watched the little blue circle go around as it downloaded and installed.
(I had looked there in the previous few days for an update without finding one until today.)
Should I watch there for the Beta you discussed?
So this time I got TestFlight and then downloaded Panels 3.0.7.
(Your instructions on how to do this were super clear. My bad.)
The new Panels beta still does not get past the black welcome screen, but there are two differences.
The iPad now gives me a notice that Panels has crashed, which was not appearing previously. Afterwards, there is a little orange dot by the panels icon.
I sent you a crash report.
Thank you again.
Not trying to hijack, but just realized I had this same problem during setup of a new device from a backup restore. Signed up for the beta and installed what TestFlight gave me. It launches Panels without the almost immediate crash. Now I need to test it with my actual data.
Perfect. The crash was caused by a missing attribute of one of the database models. So yeah, regardless of the data on the device or whether it was a backup restore or a new install… it could crash in some circumstances.
It affected users who skipped the penultimate version (went from 3.0.4 to 3.0.6 without installing 3.0.5), and/or sorted the library by file size or length.
That’s why it only affected a group of users.