Sunday, May 26, 2024
HomeiOS Developmentios - App group (containerURL) as main (or solely) file storage?

ios – App group (containerURL) as main (or solely) file storage?


I’ve an app that began by storing a small quantity of information in UserDefaults, and developed to utilizing a small variety of recordsdata (to keep away from the “photos in .plists” issues.

The app has continued add extensions, and the extensions would use an app group by way of containerURL to see the information. At first it was abstract information, however now the extensions are absolutely featured, and the containerURL accommodates a replica of what’s in “main” storage.

My query:

Since all targets want full entry to the information, is there any motive to not merely have the app and the extensions completely save within the app group’s container?

NOTE: The quantity (and dimension) of the recordsdata may have a small footprint.

Earlier than asking, I did:

  • Learn all the first documentation from Apple
  • Google round and verify stack overflow
  • Affirm that I have not inadvertently forked code between goal that handles file administration, proper now, the app and the goal habits is an identical, besides the app is utilizing the app’s default container, and the extensions are utilizing the app group’s shared container.

What I am hoping for:

I anticipate that somebody will say “sure I did this”, even whether it is by way of feedback.

My pondering is that there is perhaps some facet of provisioning, set up or meta-level considerations that I did not consider, that somebody can alert me to.

[Pls keep in mind, I’ve already jumped thru all hoops to make a Widget and an iMessage app for this project (including the Provisioning, Capability and Entitlement stuff). This isn’t a fishing expedition about Xcode’s bundle architecture.]



Supply hyperlink

RELATED ARTICLES

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisment -
Google search engine

Most Popular

Recent Comments