mirror of
https://github.com/pd4d10/git-touch.git
synced 2026-03-11 00:02:51 -05:00
markdown rendering causes reboot #84
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @ghost on GitHub (Nov 2, 2020).
Samsung Galaxy S8, Android 9, One UI
Opening this repo by going through settings crashes Android and causes a soft reboot. Issue was not present in previous play release
@ghost commented on GitHub (Nov 2, 2020):
This also seems to happen with my own repos, although testing is a bit of a pain. Gitlab is also effected, I suspect the markdown renderer may have something to do with this since repositories without a readme seem to be fine
@pd4d10 commented on GitHub (Nov 2, 2020):
The latest version uses webview_flutter to display readmes. Probably related to this change.
@pd4d10 commented on GitHub (Nov 8, 2020):
Hi, @kakolisgay , you could select Markdown render engine in the latest version v1.9.0, which has been published and in review.
@ghost commented on GitHub (Nov 8, 2020):
Updated to 1.9.0* and strangely enough, it no longer crashes. Even in flutter rendering mode. Webview rendering mode doesn't seem to work though. Was the crash fixed upstream?
@pd4d10 commented on GitHub (Nov 8, 2020):
Markdown render engine history:
@ghost commented on GitHub (Nov 26, 2020):
Still not entire sure what was causing the crashes but I assume it was likely fixed upstream. Closing for now
@pd4d10 commented on GitHub (Dec 13, 2020):
@pd4d10 commented on GitHub (Dec 13, 2020):
It seems happen again at v1.10.0
@pd4d10 commented on GitHub (Dec 13, 2020):
It is probably caused by the webview component. Selecting 'Flutter' markdown render engine would solve this temporarily.
@ThisNekoGuy commented on GitHub (Feb 27, 2021):
Still happens for me with webview*
@Lehmaning commented on GitHub (Jan 22, 2022):
The problem still exists. Maybe we should open this issue again...