Does the user see those files?
Il giorno mercoledì 6 gennaio 2021 alle 04:16:04 UTC+1 Shai Almog ha
scritto:
> Storage uses the documents folder on our iOS port. Not sure we have that
> path you're talking about. Most of that code is ~9 years old so I don't
> recall.
>
> On Tuesday, January 5, 2021 at 10:59:09 AM UTC+2 P5music wrote:
>
>> I am talking about Storage, not FileSystemStorage.
>> That is the app private folder, not the user data folder.
>> I think the iOS Library folder should be inside it.
>> Regards
>> Il giorno martedì 5 gennaio 2021 alle 04:18:47 UTC+1 Shai Almog ha
>> scritto:
>>
>>> The first FileSystemStorage root maps to the "Documents" folder. The
>>> second maps to caches and the third root maps to the resources dir.
>>>
>>> On Monday, January 4, 2021 at 9:07:48 PM UTC+2 P5music wrote:
>>>
>>>> My CodenameOne app is intended for iOS, but I also created a native app
>>>> with XCode.
>>>> The two apps should be compatible, in regard to data files in the app
>>>> private folder.
>>>>
>>>> At present stage the CodenameOne app writes data to the main private
>>>> folder /
>>>> while the Swift app uses the following instructions, as suggested in
>>>> the official guidelines, if I am not wrong:
>>>>
>>>>
>>>> let dir = try! FileManager.default.url(for: .libraryDirectory, in:
>>>> .userDomainMask, appropriateFor: nil, create: true);
>>>>
>>>> let fileUrl =
>>>> dir.appendingPathComponent(fileName).appendingPathExtension("json");
>>>>
>>>> I do not think that the "Library" is the main private folder, so I need
>>>> to understand if it is necessary for the CodenameOne app to create a
>>>> subfolder. And what should be the path.
>>>>
>>>> Thanks in advance
>>>>
>>>
--
You received this message because you are subscribed to the Google Groups
"CodenameOne Discussions" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/codenameone-discussions/b831485c-022d-455b-ad4d-81d79c93422en%40googlegroups.com.
