Seeking for the same infos, and one more :My two apps use one freemium IAP to unlock full features and renewable subscriptions for some contents.Merging subscriptions IAPsThe two freemium IAP are different, and the Mac version cost more. They will stay distincts in a possible merge scenario.But the subscriptions are the same and shared between Mac and iOS. At the time being, I had to have two products for each subscription, one for each Store with different product ID. Its currently up to our licence server processing to do the merging and allow content access for both versions whenever one environment does a purchase.It's completely unclear to me how and when to merge the two subscription products. If the Mac version vanishes by using the iOS bundle, what will happen to current purchases, both one time freemium and subscription. How will the users get the licences they paid for in the former (current) Mac version ? Specifically, will a merged app doing a "restore purchase" get all the purchases from both sides in the receipt ?We definitely need a more complete description of the Universal Purchases AND possible switch scenario.
Post
Replies
Boosts
Views
Activity
Same problem with XC12 GM.
I tried to suppress DVTSourceControlAccountDefaultsKey from defaults with no success.
Then I commented the [credentials] section in /Applications/Xcode.app/Contents/Developer/usr/share/git-core/gitconfig
restarted Xcode
and was able to access ONE repository, which recreated an entry in DVTSourceControlAccountDefaultsKey
This repository is now operational. But any other is not, even if it use the same credential. It looks like Xcode 12 has a bug in managing MULTIPLE entries in that key.
Now that the Family Sharing is up and running for renewable subscriptions, can someone confirm here what are the values received for the original_transaction_id field in receipt.
Our assumption from the doc is that all customers should get the same original_transaction_id value as the original purchaser, while each transaction_id is unique.
Others here are expecting different original_transaction_id for each customers.
And the accepted answer is ?
OK. I've been able to get an opaque background by setting navigationBar.scrollEdgeAppearance to standardAppearance. Nevertheless I still can't understand why some navigation items default to opaque and other transparent.