mirror of
https://github.com/LiveContainer/LiveContainer.git
synced 2026-04-25 17:15:50 +03:00
[GH-ISSUE #290] Enmity v2.2.6 #264
Labels
No labels
bug
compatibility
enhancement
multitasking
pull-request
safe area
status: broken
status: usable
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/LiveContainer#264
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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 @Impure2411 on GitHub (Jan 1, 2025).
Original GitHub issue: https://github.com/LiveContainer/LiveContainer/issues/290
Describe the issue
Importing plugin urls still does not work even though we use the shortcut as instructed in this thread. Nothing happens (share link -> open in LiveContainer -> Current App).
Is there a workaround like importing files to folder manually or is this a limitation? Importing source url works for aidoku so I'm wondering if it does not work in the same way.
Instructions to reproduce
What version of LiveContainer are you using?
3.1.0 (
fb0c16f)Other
No response
@Impure2411 commented on GitHub (Jan 1, 2025):
OK, I figured out the way.
@Impure2411 commented on GitHub (Jan 1, 2025):
To install theme,
Install should succeed although it can't be enabled for some reason (it prompts me to restart the app, but it's not enabled after that)
@Impure2411 commented on GitHub (Jan 1, 2025):
Updating to the latest LiveContainer build (
d23ae3a) fixed the issue above. Now we can install/uninstall plugins and theme, and enable/disable them properly.This issue could be closed with the label "status:usable" added.
@hugeBlack commented on GitHub (Jan 2, 2025):
Duplicate of #44, already fixed in 3.1.52
@Impure2411 commented on GitHub (Jan 2, 2025):
Did you read the entire issue? It works without issues now so that bug issue can be also closed. What I recommend you to do is add the label "status:usable" so that users can search the label to see if it's compatible or not easily (see readme about a compatibility list).
BTW, it should be completed instead of not planned.