Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The settings app crashes when navigating back from a license page (iOS13.2.2, LicencePlist v2.9) #123

Closed
BastiaanAndriessen opened this issue Nov 29, 2019 · 5 comments

Comments

@BastiaanAndriessen
Copy link

BastiaanAndriessen commented Nov 29, 2019

In iOS 13.2.2, the Setting app crashes when navigating back from a license page.
The generated plist
Crash video
I am using LicencePlist v2.9.

As reported in the other issue, the Settings app also crashes on iOS 13.0, and does so immediately after selecting "Acknowledgements" (not after navigating back from a license). Remarkably, I don't have any issues on iOS 13.1 (also no popping and pushing when selecting a single library).

After playing around with the plist properties I found out that removing the Title property of the PSGroupSpecifier in the generated plist fixes the crash, but produces
this behavior.
I've seen this behavior within the acknowledgement section of other apps (p.e. Github and Asana).

My guess is this is caused by iOS, but it would be nice to avoid generating the title until Apple releases a fix.

@BastiaanAndriessen BastiaanAndriessen changed the title The settings app crashes when navigating back from a license page (iOS13.2.2) The settings app crashes when navigating back from a license page (iOS13.2.2, LicencePlist v2.9) Nov 29, 2019
@griffin-stewie
Copy link
Contributor

Same here.

As a workaround, It won't be crashed and won't produce weird behavior if you have 2 levels navigations stacks.

@mono0926
We don't have to worry about these kind of Settings.app's bugs if we have #120 gets merged.

@mono0926
Copy link
Owner

mono0926 commented Dec 3, 2019

Released 2.10.0, which supports --single-page option.

You can use this option to avoid this kind of bugs for now 🐶

@BastiaanAndriessen
Copy link
Author

Thank you so much!

@griffin-stewie
Copy link
Contributor

@mono0926 @BastiaanAndriessen @NewFieldForMe
Thank you guys!

@MohdElBasyouni
Copy link

Solved with 13.3 update today.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants