feat: Add share button for patched apk#3350
Conversation
|
Share button is fine, I'm surprised we didn't have one infact But if your purpose is what's implied within that wink wink, then an option in settings to use intent-based installation instead of session would be better UX |
|
As for the output name, you could use the same name used by exporting the patch log file |
I guess? Although if the
|
|
Sure looks perfect |
|
Share should replace save, because sharing to files is the standardized way making save redundant |
|
Material Icons moment |
There was a problem hiding this comment.
Everything looks fine to me (aside from one general comment), although it would be good if the APK name is the same as APK content but if that's too much work we could add a TODO comment or file a feature request for it.
If resolved, I'll go ahead, and approve it, then merge it after 24 hours has passed. (Assuming there are no more review/requested changes after this from other designated reviewers; of course.)
Also the `version` type is `String?` so might as well add a failsafe for that if its somehow missing (???)
validcube
left a comment
There was a problem hiding this comment.
🥞 LGTM, merge on queue when 24hrs passed.
|
Can we put the share button next to the save button |
|
The share won't work after the file is deleted, but I guess that won't be a problem as long as the target app consumes the file promptly. |
yes we can 4266d04 |
# app [2.7.0-dev.1](v2.6.1-dev.3...v2.7.0-dev.1) (2026-05-17) ### Features * Add share button for patched apk ([#3350](#3350)) ([51c8d1f](51c8d1f))






Just adds a share button on the patcher screen.
Pretty useful for installing with another app (wink wink)
It's using the default
output.apkfilename because:Export/Savebutton anyways