Hello All,
I have a question about releasing a major update and new version of an app
that's already on the Mac App Store (MAS). The new version is to be a paid
upgrade, which I know the MAS doesn't really support.
Other developers use the strategy of releasing a separate app with a new name,
> On Aug 13, 2018, at 10:17 AM, Martin Wierschin wrote:
>
> The new version is to be a paid upgrade, which I know the MAS doesn't really
> support.
It has been reported that Microsoft Office 365 and Adobe Lightroom are coming
to the new Mac App Store. Those apps surely are not single time pa
> So does this mean that the new Mac App Store will allow for upgrade payments
> or recurring payments?
You never know. It’s always possible there are MAS enhancements coming to help
facilitate paid updates. Or maybe more permissible guidelines from Apple
regarding subscriptions. But I won’t be
> On 14 Aug 2018, at 04:08, Richard Charles wrote:
>
>
>
> It has been reported that Microsoft Office 365 and Adobe Lightroom are coming
> to the new Mac App Store. Those apps surely are not single time payment apps.
> So does this mean that the new Mac App Store will allow for upgrade paym
Saagar Jha
> On Aug 13, 2018, at 13:40, Martin Wierschin wrote:
>
>> So does this mean that the new Mac App Store will allow for upgrade payments
>> or recurring payments?
>
> You never know. It’s always possible there are MAS enhancements coming to
> help facilitate paid updates. Or maybe m
> Perhaps you could put both apps in an app group, so they get access to the
> same sandbox container?
Ah yes, I had forgotten about app groups. Thanks Saagar! That’s probably the
very best solution. In fact, my app already belongs to a group via the
entitlements key "com.apple.security.applica
