[TIMOB-2613] framework accessing /mnt/sdcard and fails on devices without sd card.
GitHub Issue | n/a |
---|---|
Type | Bug |
Priority | High |
Status | Closed |
Resolution | Fixed |
Resolution Date | 2012-03-11T22:24:52.000+0000 |
Affected Version/s | Release 1.5.0, Release 1.8.0.1 |
Fix Version/s | Sprint 2012-01, Release 2.0.0, Release 1.8.1 |
Components | Android |
Labels | module_filesystem, qe-testadded |
Reporter | Matt Schmulen |
Assignee | Allen Yeung |
Created | 2011-04-15T03:24:47.000+0000 |
Updated | 2012-03-11T22:24:52.000+0000 |
Description
When accessing the remote portrait url, the low level framework is not using /data on the local disk but rather always using /mnt/sdcard (even though there is no SD card mounted) when caching the image data.
http://developer.appcelerator.com/helpdesk/view/59711">http://developer.appcelerator.com/helpdesk/view/59711
Sample Code
Steps to Reproduce with Sample
Log
No exceptions were shown in the trace level log.
Tested On
Titanium Mobile 1.6.0 (02/01/11 17:45 a632082...)
BROKEN on Android Simulator 2.2
Is there any update on a fix for this? This is pretty major and I can't release!
I'm suffering hard from exactly this problem, this is pretty huge, please fix this!
There are three scenarios that need to be tested for Timob-2613 With SD card mounted 1. Verify that sd card is mounted 2. Launch app and verify the icon appears 3. Confirm that the images are stored in the correct location: /mnt/sdcard/Android/data/
When testing this with 1.8.0.1RC1 I am not getting the remote-image-cache directory.
@Michael can you provide more details? Which test specifically did the remote-image-cache directory fail to show in? Can you test this again against the GA? I'm targetting this as tbs-1.8.1 until we can verify if this was fixed or not.
updating sprint till issue can be confirmed or not.
Just tested this in the master branch, and confirmed that it is working. Note that I had to test the "without sd card" and "remove sd card while app is running" scenarios with an emulator since I didn't have read permissions for the data directory on my test phone.
This was confirmed again by Allen, resolving
Tested with 1.9.0.v20120119110134 with Droid 3 (2.3.4) for Step 2 from Allen, need to ran on Emulator to confirm the files in /data/data/...