Hi,I have been running an app campain with search ads for 2 weeks now. Now things turned to be interesting. However today I realized that apple made my app "... not eligible for Search Ads". What the **** is this ? Does anybody here have experience with that ? How cope with it and what to do to get back into business ?Any comments are highly appreciated.ThanksChrisp.s. Yes, I have read the compliance rules for search ads and I do not violate them !

Hi,I am trying to port audio input to Mac Catalyst. As of now I am using xcode11.1GMseed, macOS 10.15 Beta 10 and (ios13 release).The following code does not return any input ports under catalyst, it works however on iOS deivces. I have granted the "Hardend Runtime - Audio Input" entitlement and also the catalyst app asks for microphone permission which is granted then of course. So it is not a permission problem.let audioSession = AVAudioSession.sharedInstance() try audioSession.setActive(true, options: .notifyOthersOnDeactivation) var mic : AVAudioSessionPortDescription? = nil for input in audioSession.availableInputs! { if input.portType == AVAudioSession.Port.builtInMic { mic = input } else { print("Not internal mic") } // ERROR !!! here: 'mic' is nil, but it should at least find builtInMicWhen accessing audioSession.availableInputs the following error show up in the console:2019-10-02 08:20:18.005998+0200 [3340:162455] [avas] AVAudioSession_MacOS.mm:258:-[AVAudioSession getChannelsFromAU:PortName:PortID:]: ERROR in getting channel layout for auScope 1768845428 element 12019-10-02 08:20:18.006890+0200 [3340:162455] [avas] AVAudioSession_MacOS.mm:351:-[AVAudioSession createPortsfromAggregateDevice:]: No Ports available returning emptyIs this a bug due to beta status of the whole stuff or am I missing something ? We are now in 10.15. beta 10 which is probably near release ...ThanksChris

Hi,I have submitted a new macOS app which was rejected due to:Guideline 3.1.2 - Business - Payments - SubscriptionsYour app still uses auto-renewing subscriptions, but it is not an appropriate use of the service.Next StepsTo resolve this issue, please change your in-app purchase product to a non-renewing subscription.Background:The app offers a "recording" service that is restricted to 90 sec. in the free version of the app. After 90 sec. the recording is stopped and a requester pops up informing the user about the limitation and offering to cancel or purchase. Our (re-newing) subscriptions offer an unlock feature that removes the recording time limit.The reviewer states that this is not an appropriate use of re-newing subscriptions and recommends we should proceed with non-renewing IAPs. I have read the new review guidelines and could not find something that forbids this kind of business model for re-newing IAPs.Did anybody else experience similar rejections or can someone explain what the exact reason for these rejections is ?(The reviewer just states this to be not an appropriate use w/o furhter explaining where it really conflicts with the review 3.1.2 guidelines, which unfortunately is a very long clause.)Any information is highly appreciated. Thanks.

When I upload a preview video to ASC (which conforms to preview specifications), the uploaded video it uploaded correctly in the first place. During upload to ASC it shows a blurred image of the first video frame. So far so good. But, once upload is finished the video turns into a "cloud" image and says it is currently processed. The problem is that it gets stuck in the status „currently processed“ forever. I waited a few days but processing did never end. To make it worse the landscape "cloud" image turns into a portrait when I come back to the ASC media center. The problem : is reproducible occurs on different video files occurs on different appIDs occurs on all iPhone resolutions This is a serious bug. I can’t finalise my app submission. Any ideas ?

Hi, we have an app which used DeviceID to track users. We had implemented ATT and setup our privacy declaration in ASC accordingly. Now in our new version we decided to not track users anymore. We removed NSUserTrackingUsageDescription, removed ATT permission code and submitted the new version. Now, reviewer has complained that our privacy declaration in ASC still says we are tracking users and refused app acceptance. They told us to update the privacy declaration in ASC. We tried to do so, but ASC does not allow us to remove device ID tracking. It is showing a warning that our app still uses NSUserTrackingUsageDescription and in fact that is true for the production version. We are now in a chicken egg problem. We can't change our privacy declaration in ASC because the production version still uses the feature AND we do not get the new version accepted as long as our privacy declaration is not changed. How can we fix that ? Pls advise !

Hi, Firstly: The whole question is about MacCatalyst (in IOS it works as intended) In my Maccatalyst app I want to share Userdefaults between app and widget. I have added an app group to the widget and the app and have set up Userdefauls accordingly. Here is the problem: Xcode claims that the app group should start with "group.***" because Catalyst is based on iOS. If I do so, my Catalyst app rises the "App wants to access data from other apps" requester on EVERY launch. So, I can't use it in production. Even if I would accept the requester, the widget isn't able to access the defaults at all because it does not rise that requester, but silently ignores the access. In contrast, if I setup the app group name with our TeamID (instead of group.*) then the requester vanishes, but Xcode does not accept it, issuing a warning and displaying the app group in red. I don't think this is advisable 'state' for production code. Even then widget can't see the data either. What is the recommended way of sharing Userdefaults between Catalyst app and Catalyst Widget (not the iOS widget which displays the "open on iPhone warning" when clicked) on macOS ? Thanks