Daniel Jalkut
Erik Schwiebert
@danielpunkass sorry, no ideas. we didn’t change IDs. Apple’s migration is really for non-sandboxed -> sandboxed, not cross-container.
Once again I seek wisdom of Mac developers who have done battle with sandbox issues. "Sandbox Container Ownership." http://indiestack.com/2016/07/sandbox-container-ownership/ …
-
-
- View other replies
-
.
@Schwieb The only reason I'm contemplating a change in bundle ID is you can't charge for a new SKU on the App Store without changing. - View other replies
-
@danielpunkass not my area of expertise, but, App Groups maybe? - View other replies
-
@jnadeau Thanks, I'm using App Groups and will probably move app preferences to them as well, but in the meantime afraid of breaking access…
-
-
-
@danielpunkass Don't know if it's the same problem, but I've seen preferences updates fail after an update. Reboot has always fixed it. -
@BFormations Thanks! Sigh, these edge case behaviors are not nice to support with users. -
@danielpunkass Got that right. The bulk of our support cases are sandbox related. It's taken much joy out of using & developing for the Mac.
-
-
-
@danielpunkass Have you tried multiple entries in the com.apple.developer.icloud-container-identifiers array? -
@macgreg I have not! Thanks for the tip. I don't think I have even one. It will be interesting if that plays a part in sharing ownership. -
@danielpunkass Probably not. I think I've misread sandbox container for iCloud container. Sorry. -
@macgreg Oh, no problem. I'm curious enough to try anything :)
-
-
-
@danielpunkass Could you make code changes to app v1 to give an "export" option for the sandbox data, and write some code for v2 to import? -
@danielpunkass Obviously not the best solution, but might help head off data migration issues. -
@nptacek Yep. Trying to avoid forcing users into manual export/import workflows as much as possible. - View other replies
- Show more
-
-
-
@danielpunkass Answer from a very tired sandbox wrangler: Don't do it. Don't waste your time on custom settings, etc. Instead, import once… -
@danielpunkass …via open dialog automatically, then make additional imports (for whatever reason) available via menu or preferences. -
@danielpunkass You _can_ check if the other container exists without reading permission, so you can trigger the import only when needed.
-
-
@danielpunkass correct me if I'm wrong, but I thought the standard way to handle this was to move data to a shared app group?
Jeff Nadeau 
Binary Formations
Greg Scown
Nicholas Ptacek
Peter Maurer
Ben Lings
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.