Post not yet marked as solved
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.
Post not yet marked as solved
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 ?
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.
Post not yet marked as solved
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 not yet marked as solved
From what I've gathered from the net, looks like we cant use it a the moment. I was considering using WKExtendedRuntimeSession to keep the app on and refresh the display (not tested, maybe worth the try ?), but if it is blurred anyway, there is no point.
BEWARE anyway :I recently added this attribute to hide some items from my iOS application when the iCloud keychain is active and can be seen on a Mac, also because the MacOS version of our app is now almost ready.And we faced critical situation where iOS users where unable to store their purchases in the Keychain because of this obscure and undocumented behaviour :If you setup a dictionary to delete and rewrite an item in the KC, adding the kSecAttrIsInvisible attribute, then the delete will FAIL if the previous write was done without the invisible attribute. The error is errSecItemNotFound. Because the item is not deleted, it can't be stored again.On the contrary, an item stored with the invisible attribute can be deleted with a query dictionary including or not including the attribute.So to correctly migrate to using this attribute one should :Delete an item with a query without the kSecAttrIsInvisible attribute.If the delete fails, redo the delete with the attribute. We did not see that situation but it should be planned in the code.Then write the item with the attribute.Future delete can succeed with the attribute, but the previous steps work with only one attempt to delete in any case we tested.
