From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH pve_flutter_frontend] fix: android: unable to open spice file with aSpice client
Date: Tue, 11 Nov 2025 19:03:45 +0100 [thread overview]
Message-ID: <20251111180345.2397-1-s.shaji@proxmox.com> (raw)
Users were unable to open the SPICE file with their aSpice client on
Android [0]. The issue occurred because, in a previous commit (826474c),
the path where the .vv file was saved was changed from the external
cache directory to the temporary internal cache path.
However, the sharable directory [1] was not updated in that commit.
To fix the issue, update the sharable directory to point to the
internal cache path.
- [0] https://forum.proxmox.com/threads/new-mobile-app-for-proxmox-ve.76327/post-815473
- [1] https://developer.android.com/training/secure-file-sharing/setup-sharing#DefineMetaData
Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
---
android/app/src/main/res/xml/provider_paths.xml | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/android/app/src/main/res/xml/provider_paths.xml b/android/app/src/main/res/xml/provider_paths.xml
index 8248868..3708e27 100644
--- a/android/app/src/main/res/xml/provider_paths.xml
+++ b/android/app/src/main/res/xml/provider_paths.xml
@@ -1,4 +1,4 @@
<?xml version="1.0" encoding="utf-8"?>
<paths>
- <external-path name="external_files" path="." />
+ <cache-path path="." name="cache_file" />
</paths>
\ No newline at end of file
--
2.50.1
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next reply other threads:[~2025-11-11 18:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-11 18:03 Shan Shaji [this message]
2025-11-12 8:06 ` Thomas Lamprecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251111180345.2397-1-s.shaji@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.