Before I found this thread I issued an SO question here on similar topics.https://stackoverflow.com/questions/60587223/how-to-setup-universal-purchasesAs of today there are no answers to it, but this may change (hopefully soon !!!) in the future and to have all information in one place I am adding the link here.@Apple guys: We really need answers to these SOON !RegardsChris

same here on Catalina 10.15.3Any solutions ?

Thank you for explaining the historic evolvement of renewing subscriptions. Intererstingly my iOS counterpart of the app, which uses a very similar business model, did go through a few weeks ago w/o problems. SInce this was already a "re-submission" this is not an option anymore and I already have appealed the review decission. Let's see what they say. BTW: Does anybody know how fast they respond on appeals ?Could you please explain how you use iCloud to manage non-renewing subscriptions. For my re-newing subscriptions under iOS I do not use iCloud for restoring. I store the current expiration date insde the app (encrypted and persitently stored in keychain). When I encounter expiration I am analysing the receipt to either prolong the expiration date or disable functionality. All happens on device. The only drawback I am aware of is man-in-the-middle attack, but considering my numbers I just don't care about this.How do you manage these things using iCloud ?

How did you solve the problem ? Exactly the same problem here !!

Hi,during researching a similar problem a few days ago I came over a new build settings flag:"Derive Mac Catalyst Product Bundle Identifier"Maybe you can research in that direction. Don't know if this helps, but give it a shot.RegardsChris

I have exactly the same problem (also IOS 14 only and working in iOS 13). I found that NSMetadataQuery is broken. If you set up a NSMetadataQuery for a file in an ubiquitous container on iCloud, iOS14 will not receive the NSMetadataQueryDidUpdate notification, when you e.g. delete or modify the file with Finder. Even changes made from the iOS app that is running the query are NOT notified. Again : IOS 14 only. I think this is a VERY SERIOUS problem which should be solved asap. It renders iCloud sync across devices completely useless ! Furthermore the NSFilePresenter protocol is also broken. If you set up a FilePresenter to monitor an iCloud ubiquitous file, the presentedItemDidChange() never gets called under iOS14. In iOS 13 it works as intended. Please note that file changes using a file NSFileCoordinator initiated by iOS 14 are propagated to iOS 13 devices that are registered as presenters, but not vice versa. I think both problems are highly related. I have already submitted a TSI and reported a bug in feedback assistant, but nobody cares ! @Others: Please submit these bugs as well so that we receive awarenesses for this serious problem ! @Apple: Please help ASAP Finally here my posts for both problems on SO: https://stackoverflow.com/questions/64444494/ios-14-nsmetadataquery-not-updating-no-notifications-are-sent-works-on-ios13 https://stackoverflow.com/questions/64446024/ios-14-nsfilepresenter-not-getting-callbacks-notifications-works-on-ios13

Please do use one of your TSIs, since this would produce more credibility that this problem really exists !!! I also did submit one of my TSIs.... Meanwhile I am in communication with an Apple engineer, but the problem is, he is claiming the problem does not occur on his side. I am still insisting and providing a test project that clarifies the problem and I have also made a video that they can see what is happening live. Tho whole thing did cost me way too much time and still the bug is not at all confirmed by Apple. So please support my request by creating a bug report and submitting an TSI. Maybe you could change the title of this thread to "NSMetadataQueryDidUpdate", which is the official name of the notification. It might increase the probability that people find this thread. Thanks

Any news on this ?

Did anybody find workarounds for this ? I have the same problem !

@Maven: Yes of course @ivancnatorino: No, apple engineers were committed but didn't offer a solution As of 2021-03 the bug seems to be fixed in macOS 11+. but still exists in macOS 10.15+ In essence that means that no Catalyst app using audio will exist for macOS Catalina ! That's a pitty Regards Chris

I have the same issue. Did you investigate this further ? Is only sandbox affected by this ?

I can confirm this behaviour. We need urgent fix for this, because as of now programmers don't know when the recogniser has finished previous segment and is starting a new segment. Thus a continuous transcription is impossible !!! Furthermore on some older Macs the recogniser is NOT setting the segment confidences to greater than 0 when a segment is finished. So this is also NOT a solution for knowing when a segment is finished. This is a severe problem ! Pls fix asap !

Same here ! Did you find a solution ?

[quote='813262022, DTS Engineer, /thread/768254?answerId=813262022#813262022'] Using a group. prefix is fine in a Mac Catalyst app. [/quote] Thanks for your feedback. I tried this, but there are 2 issues. If I use group.* I get this annoying requester at every launch of the catalyst app (I am running macOS 15.1), and the widget isn't able to access Userdefaults. The widget comes up always with default settings despite what is set in Userdefaults. I don't know why ... (in iOS it works).

I found the issue. For some reason the provisioning file for Catalyst was not correctly updated when adding the app group. After deleting the Xcode managed profiles and rebuilding them the app group entitlement also appeared for the Catalyst app and the requester is gone. Thanks for your response anyway !