Languages

Menu
Sites
Language
Unable to see files which was created using GetAppDataPath
Straight and simple  : I am not able to see data folder inside opt/apps/(MyAppID) directory. I have expanded the emulator and I looked into my app data path. I am not able to see neither data folder and the file which I saved. The following is the code which I used to create a file and saved inside the data folder,
 
String fileName(L"log.txt");

   File file;

   char buffer[10];

   char buffer2[5];

   int i;

   int readCnt;

   result r = E_SUCCESS;

   // Creates file

   String filePath = App::GetInstance()->GetAppDataPath() + fileName;

   r = file.Construct(filePath, "w+");

   if (IsFailed(r))

   {

       AppLog("Failed");

   }

   for (i = 0; i < 10; i++)

   {

       buffer[i] = (char) i;

   }

   // Writes to the file

   r = file.Write(buffer, 10);

   if (IsFailed(r))

   {

    AppLog("Failed");

   }

   // Repositions the file pointer

   r = file.Seek(FILESEEKPOSITION_CURRENT, -5);

   if (IsFailed(r))

   {

    AppLog("Failed");

   }
 
The above code is taken from the Tizen website and no error is being thrown.
NOTE : After this problem , I tried to create data folder inside the opt/apps/(MyAppID) on my own too, but it is displaying error as data folder already exists.
Why I am not able to see data folder ?
 
Edited by: Leo Joseph on 16 Aug, 2013

Responses

3 Replies
wil smith
Looks, from 2.2 onwards Tizen has added an extra security measure. Emulator can be run in user mode or root mode. When it is in user mode, you won't able to access/see application private files/folders, only shared folder will be visible. If you switch to "root" mode, you can access all you application files. For swithing to root mode follow the steps below: 1. run the command prompt/terminal. 2. Change working directory to \tizen-sdk\tools 3. Execute "sdb -e root on"
Leo Joseph
will smith. That was perfect. Now I am able to see the folder as well as my File. Thank you. I am facing strange problems in this 2.2 beta version, where my log stops working. Planning to post that question as a separate one.
Byron Gavras
Great! I had the same issue but nobody answered so clear. Now it is fixed. In case someone has the same issue but in a physical device the command is sdb -d root on