-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
Kiwix MacOS always crash by trying to open an non-existing article #157
Comments
(This is a copy of openzim/mwoffliner#852 (comment) ) This issue probably is related to the fact that the hyperlinks on the landing page of
(note the forward slash). However, hyperlinks on the page are:
That's clearly incorrect, as the href should be |
Is this issue current? Do I need a paid Apple Developer license to build this app via Xcode? My first attempt failed because of a missing provisioning profile for WikiMed. |
@jhbiggs I would say this issue is still current until openzim/mwoffliner#726 is fully resolved. I don't know about your other questions. |
@jhbiggs Yes, I confirm. |
This issue has been automatically marked as stale because it has not had recent activity. It will be now be reviewed manually. Thank you for your contributions. |
@kelson42 Do you happen to have a zim file available to test this issue? If not, I am gonna close this as unable to reproduce |
@automactic It seems to not crash anymore indeed. That said, no info/erro is printed either. |
You mean when click on an article that does not exist? Do you have an example zim file that could be used as test? I have recently added a alert for this scenario on iOS could certainly do the same for macOS |
@automactic the current edutech fr has a lot of them. |
added alert in #308 |
Steps:
1 - Download http://tmp.kiwix.org/wikivoyage_en_all_novid_2019-06.zim
2 - Open main page
3 - Click on "Europe"
You get:
1 - Application quits
You should get:
1 - An empty page or an error
Remark
Link "Europe" points to an non-existing article, this is the root of the bug probably...
The text was updated successfully, but these errors were encountered: