-
Notifications
You must be signed in to change notification settings - Fork 373
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
v2.12.3: "Share into" launcher shortcut crashing #2371
Comments
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Yes, editor and viewer screens works fine in Markor itself (for both todo and markdown files). Attached video with issue. Screen_Recording_20240730_102444_One.UI.Home.mp4 |
This comment was marked as duplicate.
This comment was marked as duplicate.
Thank you for the video. This is why describing issues best you can is important. It helps a lot if you add picture or video, makes it more likely to understand what you mean. I thought you generally speak about ShareInto (when you share....something from browser to Markor) i.e. I see that it's crashing here too. Probably related to @harshad1 recent changes to the activity launchers |
I experienced this issue too in my Z fold 5, One UI |
Description
After update from v2.12.2 to v2.12.3 "Share into" launcher become broken. I click on it, quick animation of its trying to open screen appears, and then nothing happens.
Reproduced in both Fdroid version and nightly build.
Screen_Recording_20240730_102444_One.UI.Home.mp4
Steps to reproduce
AR: quick animation appears, but window not opened.
ER: open share into screen.
Information
Android version: 14
Device: Samsung Galaxy A55
App Version: 2.12.3
Nightly App Version: net.gsantner.markor-v153-2.12.4-flavorAtest-debug.apk
Source
F-Droid
Format / File type
Not specific
Additional info / Log
And each time I try to open share into after that:
The text was updated successfully, but these errors were encountered: