We are in an app review loop trying to get an in-app purchase approved with this message (below)However, we did what they said and resubmitted a binary (essentially the same binary we submitted before but witha new build number), but then the in-app purchase is rejected for the same reason, with no additional explanation.Is there a way to escalate this and talk to someone to figure what is going on? This is for a pre-existing app in the app store, not a new app.In-App Purchase - New Business ModelWe have begun the review of your in-app purchase but aren't able to continue because your submitted in-app purchases indicates a change of business model for your app. Therefore, we need to verify the implementation of your submitted in-app purchases in the app to ensure your app, and its in-app purchases, are in compliance with the App Store Review Guidelines.Next StepsPlease upload a new binary for review and resubmit your in-app purchase(s) with the binary so that we can continue the review.

hello I am confused about mac app store search rules i released a new mac app last week and it still does not show up when i type the exact app name as a search. does the mac app store not use the app name automatically as a keyword? app name = SimplML if anyone at apple wants to analyze why it is not showing up since it is a non standard spelling, one would think it would pop up at the top note: mac app store, not iOS store

hi all, is it possible to control the orientation of the UIMenuController popup menu or does it always follow the status bar orientation like so many other things do? see attached. main app is in portrait but some uses are in a landscape mode. but the status bar is still portrait in this case. so we would like to force rotate the popup menu to be in landscape mode.

anyone else notice this greek letter misspelled in the keycaps app? i thought i was spelling it wrong but maybe not?

my understanding is that header file search paths (-I options) go directly to the compiler command lines. so: why when i switch to the new build system am i suddenly getting header file path errors (cant find various header files)? does any one have any documentation on how the new build system affects the header file search paths?

has anyone else noticed much slower GCD runs in newer MacOS / Catalyst this seems like it used to be blazing fast: dispatch_async(dispatch_get_global_queue(QOS_CLASS_USER_INTERACTIVE, 0), ^{ // code to run }); now if I run a block on this type of queue versus the main thread, the dispatched code runs much slower vs main thread. not 10%, like multiple slower. i am not sure yet if it is the code run time or time for dispatch to trigger. trying to focus in on what is the problem on our side and get some metrics, but if anyone has seen this issue, it might be useful to compare notes.

hi all, i have made mac catalyst apps before and they were fine. now i try to make a new one (converting an iOS app over to catalyst) in xcode14.2 and i get the above error msg when trying to run on mac intel locally. however, i seem to have the mac os deployment targets set to a slightly older version of macos than i have installed on the run target mac. what is new in catalyst setup that i am missing? the setup seems a little different in the xcode UI than before so maybe there are some new hidden tricks to get this to work?

Hey guys, tried to follow the super confusing doc on this, but no luck yet. https://developer.apple.com/av-foundation/Incorporating-HDR-video-with-Dolby-Vision-into-your-apps.pdf I have code that uses AVAssetReader and AVAssetReaderTrackOutput to directly pull frames from a video, but the colors are wrong for HDR dolby videos. Basically what I want is to extract frames from an HDR Dolby video as images and have those images not be the wrong color. Don't care if they are only 8 bit per color instead of 10 and all the all new stuff, just the closest that old fashioned 8 bit per color supports. I added the statement marked // added for dolby hdr per the above doc, (spread across several lines), no luck, still bad colors. Any hints of what I am missing? NSMutableDictionary* dictionary = [[NSMutableDictionary alloc] init];                                [dictionary setObject:[NSNumber numberWithInt:kCVPixelFormatType_32BGRA] forKey:(NSString*)kCVPixelBufferPixelFormatTypeKey];                // added for dolby hdr                dictionary[AVVideoColorPropertiesKey] = @{                 AVVideoColorPrimariesKey: AVVideoColorPrimaries_ITU_R_709_2,                 AVVideoTransferFunctionKey: AVVideoTransferFunction_ITU_R_709_2,                 AVVideoYCbCrMatrixKey: AVVideoYCbCrMatrix_ITU_R_709_2                 };                                AVAssetReaderTrackOutput* asset_reader_output = [[AVAssetReaderTrackOutput alloc] initWithTrack:video_track outputSettings:dictionary];                                  [asset_reader addOutput:asset_reader_output]; // from here we get sample buffers like this CMSampleBufferRef buffer2 = [asset_reader_output copyNextSampleBuffer]; // then pixel buffer  CVPixelBufferRef inputPixelBuffer = CMSampleBufferGetImageBuffer(buffer2); // then a CIImage   CIImage* ciImage = [CIImage imageWithCVPixelBuffer:inputPixelBuffer]; // one vid frame then we use standard stuff to convert that to a CGImage/UIImage

we are doing something like this to get photo data from photo kit (see code) however, when the media is on iCloud, it seems like it is trying to pull the highest res possible (e.g. for RAW photos or ProRes vid maybe). which can take a lonnnng time if you are on a cellular net. this completely bogs down the app. is there a recommended way to get a normal res media item from this (e.g. not pull the highest res from icloud?); either a standard jpeg or a lower res movie? [phasset requestContentEditingInputWithOptions:options                                          completionHandler:^(PHContentEditingInput *contentEditingInput, NSDictionary *infoin) {

hello apple guys, why do live photos lose their live-ness even when going thru proprietary iMessage? what is the best way transfer these live photos between users even for testing? i see the little icon indicating it is a live photo on the "sent" side of the message, but on the rec'vd side it shows as a regular photo.

Is there a simple way in the newer iOS versions to make all black pixels transparent for an image? I see a whole bunch of super complicated stuff online on how to do this for colors other than black involving color cube mapping etc, but it seems like it should be a 1 line filter operation. Any ideas from the Apple experts?

hi all, getting an error reading ProRes vid on a non ProRes phone (12 mini) video was sync'd via icloud to the 12mini video plays ok in the apple photos app, but our asset reader is puking on it the same code works ok on the phone where the pro res video was made AVAssetReader * asset_reader = [[AVAssetReader alloc] initWithAsset:asset error:&error]; NSMutableDictionary* dictionary = [[NSMutableDictionary alloc] init]; [dictionary setObject:[NSNumber numberWithInt:/*kCVPixelFormatType_420YpCbCr8BiPlanarFullRange*/ kCVPixelFormatType_32BGRA] forKey:(NSString*)kCVPixelBufferPixelFormatTypeKey]; AVAssetReaderTrackOutput* asset_reader_output = [[AVAssetReaderTrackOutput alloc] initWithTrack:video_track outputSettings:dictionary]; [asset_reader addOutput:asset_reader_output]; [asset_reader startReading]; asset reader error code is: (NSInteger) $1 = -11833 localized msg = "Cannot Decode" note that i had tried a different recommended pixel format instead of the older BGRA we wer using (commented out). didn't work either. this is older code. anyone see this, know of workarounds?

has anyone noticed this query being a lot slower in newer iOS versions? we try to get counts of all assets in all asset collections (folders) to display in a selector table for the user to select an album to work with, and it seems to be lagging recently when there are a lot of assets involved maybe some of the assets are on iCloud? not sure. getting user reports of speed issues. we are trying to set .fetchLimit in fetch options to a number like 1000 or so to keep it from scanning all assets as a test to see if we get fewer complaints, but will have to wait for user feedback and our tracking metrics to see if it speeds up or not on real user devices with lots of photos. regarding counts, we are seeing users with 100k+ assets on a device (photos & videos).

anybody else noticing : unable to pair iphone ios16.x to mac via bluetooth?

i upload a binary from xcode, it shows as "uploaded," but on appstoreconnect, it does not appear. it doesnt even say "processing" or something like that. why?