" That flexibility makes type checking difficult." if type checking is so difficult, they should have a compiler flag you can add that requires you to declare all variable types like in C++ or ObjC, and checks if you have not done this. an error with no specific line number seems prehistoric in the compiler era. Or at least make a "recommended practice" to declare the types of all variables. You may save 15 minutes by not doing so, then next week you might spend 2 hours trying to find the source of an error like this.

the thing you find out over time is that sometimes the compiler will say it is this "reasonable time" thing, but really it could be some other error. a truly maddening error message. in the old days when compilers couldn't figure out your code they would sometimes output PANIC! and stop haha. which gives you about as much information as this reasonable time error.

apple seems to have fixed this issue

fyi apple posted a response to another thread on this issue (see page 12 of this thread), they are working on it: https://developer.apple.com/forums/thread/701330?page=12

yes same here, tried a bunch of stuff like that. it looks like it installs but then says Install again, and the app on the home screen of the phone has a little cloud icon w/ a download arrow on it. we found this other commentary on this problem. no solution for us yet but there are some ideas there: https://developer.apple.com/forums/thread/720033 i put in a call to support, they had not heard about this issue yet. weird thing, installed ok on ios15.6.1 but not ios15.4 ok it just worked (good test flight install) on my ios16.1.1 phone... weird. maybe it is fixed now? update: it only ran once after install. then when i tried to relauch the app, it showed the beta expired alert again.

if anyone is running into this, it seems that if you get an out of memory crash, you get no stack trace.

no havent found an answer yet

FYI we got a half hour "office hours" appointment and after some chatter and trial and error, this method seemed to do the trick at extracting images from HDR / Dolby vids with better color. We don't know if it is the full answer yet, but it is definitely better. // prior to here, set up the AVAsset * asset // code is a bit of archaic ObjC syntax but it works NSArray* video_tracks = [asset tracksWithMediaType:AVMediaTypeVideo]; AVAssetTrack* video_track = [video_tracks firstObject]; NSMutableDictionary* dictionary = [[NSMutableDictionary alloc] init]; // kCVPixelFormatType_32BGRA (pixel format we originally used) // 420YpCbCr8BiPlanarFullRange (new pixel format that seems to work) // need to change the pixel format to this new one here, and also set the video color prop key below (which is 3 items in a dictionary) [dictionary setObject:[NSNumber numberWithInt:kCVPixelFormatType_420YpCbCr8BiPlanarFullRange ] forKey:(NSString*)kCVPixelBufferPixelFormatTypeKey]; 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]; // then proceed to normally walk thru frames of the video

fyi if anyone having this problem, i shut off the new managed versioning switch in the uploader and it worked. whether this was co-incidental to the problem i dont know, but our upload works now.

if anyone has this problem, we found the solution, you have to clear prior uses of this sign in w/ apple feature on a given app e.g. each user has to do it not so easy to explain this to the users https://github.com/invertase/react-native-apple-authentication/issues/144