Assigned
Status Update
No update yet.
Comments
uc...@google.com
not me
On Friday, September 9, 2022 at 07:45:40 PM PDT, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the team that works on this product.
https://issuetracker.google.com/issues/192000016
Changed
priority: P3 → P2
status: Assigned → New
assignee: an...@google.com → <none>
_______________________________
Reference Info: 192000016 Deleting a database in "Device File Explorer" deletes all database and removes the sd directory "databases".
component: Android Public Tracker > App Development > Android Studio > Tool Windows > Device File Explorer
status: New
reporter: rr7051349@gmail.com
cc: rr7051349@gmail.com
type: Bug
priority: P2
severity: S3
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.
On Friday, September 9, 2022 at 07:45:40 PM PDT, <buganizer-system@google.com> wrote:
Replying to this email means your email address will be shared with the team that works on this product.
Changed
priority: P3 → P2
status: Assigned → New
assignee: an...@google.com → <none>
_______________________________
Reference Info: 192000016 Deleting a database in "Device File Explorer" deletes all database and removes the sd directory "databases".
component: Android Public Tracker > App Development > Android Studio > Tool Windows > Device File Explorer
status: New
reporter: rr7051349@gmail.com
cc: rr7051349@gmail.com
type: Bug
priority: P2
severity: S3
retention: Component default
Generated by Google IssueTracker notification system
You're receiving this email because you are subscribed to updates on Google IssueTracker
Unsubscribe from this issue.
je...@gmail.com
I'm unsure what the exact issue is. Is it that if you delete one database it will delete all the databases along with its root directory?
uc...@google.com
Thank you for your feedback. Team may reach out for more feedback in reproducing or triaging this issue.
je...@gmail.com
Just an little info more :
I think the problem does not come from the structure of the sqlite .db pointed by the "Save as", because :
- All the table are used by the application, without any probleme,
- In the application it is possible to make a backup of the .db (to download directory).
So when I open the backup .db anything are OK with my DB Browser for SQLite.
- "Save As" with this same file .db to Desktop was OK with Android Studio 3.1
John :)
I think the problem does not come from the structure of the sqlite .db pointed by the "Save as", because :
- All the table are used by the application, without any probleme,
- In the application it is possible to make a backup of the .db (to download directory).
So when I open the backup .db anything are OK with my DB Browser for SQLite.
- "Save As" with this same file .db to Desktop was OK with Android Studio 3.1
John :)
Description
To open a sqlite database from /data/data/com.mypackage/databases/pcav.db I use "Save As" to my desktop directory.
With the studio 3.3 I get a bug. le process is stop before its end and the interface said
"errors downloading files and/or directories: Writing local file failed!"
grrrrr... I’m very surprised because the 3.3 is a stable release
jeanmarccrespin@gmail.com
Build: 3.3, AI-182.5107.16.33.5199772, 201812250239,
AI-182.5107.16.33.5199772, JRE 1.8.0_152-release-1248-b01x64 JetBrains s.r.o, OS Windows 7(amd64) v6.1 Service Pack 1, screens 1920x1080
Android Gradle Plugin: 3.3.0
Gradle: 4.10.1
NDK: from local.properties: (not specified); latest from SDK: (not found);
LLDB: pinned revision 3.1 not found; latest from SDK: (package not found);
CMake: from local.properties: (not specified); latest from SDK: (not found); from PATH: (not found);
Source: user_sentiment_feedback
IMPORTANT: Please read