By now all Mac App Store developers know that all apps must have the new OSX Lion Sandboxing enabled going forward. For existing apps, we must enable it in XCode 4.2 and set in place the data migration plist.
So my existing Mac App Store app has a build target of OSX 10.6.8 Snow Leopard. Not only that, but it does access the webcam and also synchronizes stuff to iCal via CalendarStore API and AppleScript. I'm expecting most of my app to break when I enable the Sandbox, but when I get that working in the Sandbox I'm wondering if a Sandboxed app can run in Snow Leopard.
Does anybody have experience in migrating to the Mac App Sandbox? I would like to know if enabling this would break Snow Leopard compatibility, and what I am up against given the entitlements my app will require.
Snow Leopard is an awesome OS and I'd like to support it as long as reasonably possible, for those users who have a Mac not quite new enough to run Lion.
After enabling entitlements and sandbox while still keeping the build target as 10.6, I was able to get my app up to speed so it operates within the sandbox in Lion. E.g. file access, calendar access, webcam access.
Once I had that taken care of, I built a .pkg file and installed it on my old Mac Mini running Snow Leopard. It seems to run in Snow Leopard just as it did before. Unlike Lion, it won't migrate your config and plist-defined folders as it seems the sandbox stuff that is compiled in is completely ignored when run under Snow Leopard (which makes sense since the Lion kernel is probably doing all the work).
So there you have it, the short answer for backwards compatibility is "Yes". Although who is to say Apple won't restrict 10.6 targeted builds from being uploaded to the Mac App Store once March 1st hits? Probably not, but it will happen eventually. I'm not trying to start a rumor or anything, it's just a thought.
Anyways, I hope Apple continues to let us support Snow Leopard users, as I imagine they are still the majority of the Mac users out there. Take this article with a grain of salt, but still...
http://www.theverge.com/2011/11/11/2554009/mac-os-x-lion-adoption-slowing
Related
Since Mac OS 11 Big Sur release Apple allows installation of kext drivers in the Recovery mode only.
It also prohibits installation of kext drivers from Apple store. Which I guess is the end of macFuse, at least for virtual/cloud file systems.
What would be the migration path and how to build virtual file systems for Mac OS 11+, in particular for document management and cloud storage, similar to OneDrive, DropBox, etc.
I can also guess that a similar issue may appear on Windows too. I can imagine that Microsoft will follow Apple's path and will prohibit file system drivers and filters on Windows for these purposes in future releases.
Any hint for future migration if such a situation happens would be appreciated.
Since macOS 11, Apple has updated documentation of the File Provider API which can be used to sync files between client and server and may serve as a replacement for file system drivers. Until this day Apple has not officially announced that functionality on macOS.
The API is similar to the File Provider API that Apple has provided for iOS 11 some time ago but still it has some differences in mostly how main FileProvider class extension works and which abilities it has. There is no examples at this moment that I’ve seen but it looks like this functionality works at least on basic level. Based on what people say on the forums.
On Windows, Microsoft has introduced the Cloud Storage Provider (Cloud Sync Engine) API for Windows 10 in the year 2018 (Windows Creators update). It is used in One Drive for Windows. Here are some examples on GitHub in C++ and in C#.
The repository 'https://packagecloud.io/realm/realm/linuxmint serena Release' does not have a Release file.
N: Data from such a repository can't be authenticated and is therefore potentially dangerous to use.
N: See apt-secure(8) manpage for repository creation and user configuration details.
We don't support Linux Mint at this time.
Edit regarding the comment:
We support Linux. It's the only platform we support in production.
We support Ubuntu 16.04, CentOS 6 & 7 (as indicated on the website). You can trivially create a docker container or VM using one of these base images on Linux Mint. We have a number of issues requesting Debian support, Fedora support, native Docker image, but none formally requesting Linux Mint support.
We obviously want to make the experience as painless as possible for everyone, but we also have to be very strategic when deciding to add a new platform as officially supported. Our CI has to build and test every single change on this new platform. We have to be able to support our users, etc. For example, we already have some bugs that only appear on CentOS 6, but not on 7 nor Ubuntu, so we want to make sure we stabilise things before moving ahead.
Feel free to submit a feature request to support Linux Mint. That way you will have a place where you can ask us directly about progress.
I'm developing an app on a 64-bit machine with Lion and Xcode 4.2. I'm not doing anything special with the 64bit environment or lion specifically and would like this app to run on 32bit Snow Leopard machines. Can I do this? If so, what specifically do I set in the build settings?
I've looked all over the internet and cannot find a simple "yes, here's how..." or a "no, it isn't possible"
Thanks
The simple answer to the situation above: NO
Because the program was using ARC and that is limited to 64 bit releases only.
My client wants an application, that uses 10.7 specific features (eg. it's compiled with 10.7 SDK to support resume, no specific code changes are needed for this), but it's needed, that the same application runs on 10.5 and 10.6. This application shall get into App Store.
Any ideas?
Also you could set Deployment target to 10.5 and all will be fine. But in this case specific Lion features will be not working in the lowest versions of osx. Also you should not call selectors thats not exist in lowest versions. In this case you should wrap osx 10.7 selectors into responsToSelector: statement.
I'm about to write an app that should work under OS X and Windows XP/Vista/7. The app will require a database engine. Can someone suggest one that can do the following:
Be compatible with Windows
Be compatible with OS X (and preferably with iOS)
Preferably be available by default in those operating systems, or require minimum installation.
I understand that all three items may be hard to come by. So just curious, whatever is available?
My favorite is Sql Lite: http://sqlite.org/
It requires no installation, and is a small binary.